[lkml]   [2002]   [Jan]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Autoconfiguration: Original design scenario
On Tue, Jan 15, 2002 at 11:17:49AM +0100, Giacomo Catenazzi wrote:
> [ In Alan diary, I found that he tried some drivers
> before to find the driver for Telsa new tape.
> Autoconfigure will help also hackers.
> Hmm. Was the card ISA? so forget the above example
> ]

Not particularly wanting to add to the rediculously high level of noise
on this list, but yes, that's happened to be once before, but for a PCI
ISDN card.

There weren't many clues on the card packaging what it was, and couldn't
find anything on the net about the card, so resourted to the "insmod this
module, does it do anything" approach. After many hours of prodding
around and reading source, turns out that it needed the hisax driver with
various random parameters.

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.

Russell King ( The developer of ARM Linux

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.114 / U:6.104 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site