Hi Jeff,
I agree that an isa interface with sysfs would be useful. This patch looks like
a great start. I'm considering the following aditional changes...
1.) Perhaps the contents of /drivers/eisa and /drivers/isa should be held in the
same directory. Comments?
2.) Some collaboration between isapnp, eisa, and isa would be nice. This is
because all three of these interfaces could potentially be detecting the same
devices, resulting in nasty conflicts.
3.) A sysfs interface that would export isa information would be useful.
4.) Perhaps the isa drivers could match against the name of the legacy probing
driver or maybe the system should be designed to not use device_ids at all.
Also a few things to consider...
Is isa limited to one dma, one irq, and one ioport? I haven't seen more then
this anywere but it would be nice to know for registration purposes.
What is the best action to take if a legacy probing technique detects an area
that conflicts with a previous legacy probe from another driver. At the very
least, it would be nice if isa was aware of such things.
Best Regards,
Adam
-
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/