On Fri, Oct 29, 2004 at 09:18:18PM +0200, Krzysztof Halasa wrote:

"Pekka J Enberg" [off-list ref] writes:

quoted

Yup, I thought about that after I sent the patch. However, as it
stands now, many network drivers use netdev->base_addr for just that.
Perhaps it should be nuked completely instead?

I thinks so. With ifmap, SIOCSIFMAP, ifr_map, mem_end etc.,
irq, if_port, dma.

SIOCSIFMAP is unfortunate, but legitimate - it passes more or less
opaque structure to driver and lets driver interpret it.

SIOCGIFMAP, OTOH, is really bad - among other things, for many drivers
it leaks ioremapped addresses to userland.  And *that* is a LARTable
offense - it's an information that makes no sense whatsoever for userland
code and should never be exposed, just as with any kernel pointers.

What uses ->base_addr from the data returned by SIOCGIFMAP?