[lkml]   [2002]   [Jan]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Autoconfiguration: Original design scenario

Russell King wrote:

> I really don't see why hisax couldn't say "oh, you have an ISDN card with
> IDs xxxx:xxxx, that's hisax type nn" and be done with it, rather than
> needing to be told "pci id xxxx:xxxx type nn". Have a look at
> drivers/isdn/hisax/config.c and wonder how the hell you take some random
> vendors PCI ISDN card and work out how to drive it under Linux.
> (For the record, the card was:
> 1397:2bd0 - Cologne Chip Designs GmbH - HFC-PCI 2BD0 ISDN
> and the driver requirements were: hisax type 35 proto 2)
> Realistically, I don't think any autoconfigurator will solve such cases
> until these areas can be fixed up reasonably.

Autoconfigure cannnot solve this.
The card is not in my database.
To help user, you should tell the driver maintainer to add our card
in the know pci devices. In this manner autoconfigure, hotplug and
modutils can take easy use your card.

This is also a problem of PCI design.
ISAPNP have the function type, USB have also the
function class, so that there exists few interfaces, and kernel
can ask only to specific interface and not to the specific card.
PCI also have the interface field, but not very used, and the
interfaces are also not so standardized.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:22    [W:0.090 / U:4.056 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site