On Sat, 1 Jan 2000, James Simmons wrote: > On Fri, 31 Dec 1999 08:53:50 +0100 Christophe Kumsta <[EMAIL PROTECTED]> wrote: > >David Schleef wrote: > >> with kmalloc, hence the 128k limit. Yet another good reason not to use > >> global variables in modules, since this means that it is more difficult to > >> find their physical address. > >> > >Hi all, > > > > About the physical address , have someone any idea with getting the > >physical address > >of a kmalloc'ed structure ? ( virt_to_phys() does not work ...) > > I tried to do that for an EtherPowerII netcard which use a TX-ring and > >RX-ring with > >bus-master access but I had to change my solution with a high part of > >unused memory > >physicaly remapped to give the physical address to the PCI netcard... > > Read linux/Documentation/IO-mapping.txt It has excellent explaination of these functions. Kmalloc allocates continous physical memory. Doing a & on the address returned by kmalloc should give you the physical address. Virtual address doesn't mean much to the kernel. --- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED] ---- For more information on Real-Time Linux see: http://www.rtlinux.org/~rtlinux/
