Lines Matching full:address

21 controller the physical address of the buffers, which is correct on x86
26 so-called "bus address". 
31  - CPU untranslated.  This is the "physical" address.  Physical address 
34  - CPU translated address. This is the "virtual" address, and is 
38  - bus address. This is the address of memory as seen by OTHER devices, 
45 Now, on normal PCs the bus address is exactly the same as the physical
46 address, and things are very simple indeed. However, they are that simple
47 because the memory and the devices share the same address space, and that is
59 address 0 actually shows up as address 2 GB for any IO master.
62 has to give the master address 0x80000000 as the memory address.
67  physical address:	0
68  virtual address:	0xC0000000
69  bus address:		0x80000000
76  physical address:	0
77  virtual address:	0xfffffc0000000000
78  bus address:		0x40000000
80 (but there are also Alphas where the physical address and the bus address
94 You want the **virtual** address when you are actually going to access that
110 		/* get the address from the controller */
116 on the other hand, you want the bus address when you have a buffer that 
125 And you generally **never** want to use the physical address, because you can't
129 So why do we care about the physical address at all? We do need the physical
130 address in some cases, it's just not very often in normal code.  The physical
131 address is needed if you use memory mappings, for example, because the
132 "remap_pfn_range()" mm function wants the physical address of the memory to
149 related functions. You should never take the address of such memory, because
150 there is really nothing you can do with such an address: it's not
184 	/* get the 6-byte Ethernet address at ISA address E000:0040 */