>> Are we stuck with Space.c forever? Anyone have any plans for
>> replacing it with something more driver-model friendly?
>
> Is it worth the effort. Why not just let the old ISA stuff live
> out its life in peace ? There is certainly no reason we couldn't
> make it more driver model like by splitting probe and activity
>
> i.e. ne2000 probing would do
>
> poke around for ISA device
> Found one ?
> Alloc ISA device
> Fill in ports/range/IRQ
> Fill in vendor/product with invented idents
> Announce it
>
> Then have ne2000 driver model code do the actual setup
Is the vendor ID 015A allocated to anything? If not, we could use
that to indicate ISA devices - it resembles ISA as a number, and
would thus be easier to identify. We could then use the product
number to identify the particular product. For example..
015A:2000 NE 2000 clone card.
015A:3509 3COM 3C509
...with other numbers allocated in a similar way. There may be some
duplication as the above allows 65,536 discrete ISA Bus products,
but that shouldn't matter providing we allocate unique product ID's
for each product actually installed on a particular system.
Alternatively, if it's free, we could use 15Ay:xxxx to allow for up
to 1,048,576 products, with ID's like the following...
15Ay:2000 NE 2000 clone card.
15Ay:3509 3COM 3C509
...with the 'y' digit used to allow up to 16 different products with
any given product ID, incremented by the kernel as required.
Best wishes from Riley.
--- * Nothing as pretty as a smile, nothing as ugly as a frown.
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.476 / Virus Database: 273 - Release Date: 24-Apr-2003- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/