Philip Blundell writes:
> >However, when you start to think about loadable modules, this argument does
> >not count (loaders are required to get at the IP addresses for some netcards,
> >since they're stored in the description string,
>
> It's scarcely hard to teach the driver how to write to a paging register.
So rather than have a generic expansion card handler, you'd rather duplicate
code left right and centre to be able to read the cards IDs, the chunk
directories and so forth.
I don't think so. If you don't like it, complain to what's left of Acorn for
creating such a brain dead spec, and the third party companies for implementing
it. This is what we've got to work with, and it's worked satisfactorily for
the last 5 years.
The kcardd idea is quite clean, and doesn't cost us a lot. It also allows these
cards which have wrong IDs on them to work (eg, the PowerROMs). If you're worried
about the code supplied on expansion cards having trojans in them, I don't think
so. You've got to trust some non-free software at some point.
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King [EMAIL PROTECTED] --- ---
| | | | http://www.arm.linux.org.uk/~rmk/armlinux.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
