Lines Matching refs:address

11 controller the physical address of the buffers, which is correct on x86
16 so-called "bus address". 
21  - CPU untranslated.  This is the "physical" address.  Physical address 
24  - CPU translated address. This is the "virtual" address, and is 
28  - bus address. This is the address of memory as seen by OTHER devices, 
35 Now, on normal PCs the bus address is exactly the same as the physical
36 address, and things are very simple indeed. However, they are that simple
37 because the memory and the devices share the same address space, and that is
49 address 0 actually shows up as address 2 GB for any IO master.
52 has to give the master address 0x80000000 as the memory address.
57  physical address:	0
58  virtual address:	0xC0000000
59  bus address:		0x80000000
66  physical address:	0
67  virtual address:	0xfffffc0000000000
68  bus address:		0x40000000
70 (but there are also Alphas where the physical address and the bus address
84 You want the _virtual_ address when you are actually going to access that 
100 		/* get the address from the controller */
106 on the other hand, you want the bus address when you have a buffer that 
115 And you generally _never_ want to use the physical address, because you can't
119 So why do we care about the physical address at all? We do need the physical
120 address in some cases, it's just not very often in normal code.  The physical
121 address is needed if you use memory mappings, for example, because the
122 "remap_pfn_range()" mm function wants the physical address of the memory to
137 related functions. You should never take the address of such memory, because
138 there is really nothing you can do with such an address: it's not
169 	/* get the 6-byte Ethernet address at ISA address E000:0040 */