From: Russell King <rmk@arm.linux.org.uk>
To: Giacomo Catenazzi <cate@debian.org>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
"Eric S. Raymond" <esr@thyrsus.com>
Subject: Re: Autoconfiguration: Original design scenario
Date: Tue, 15 Jan 2002 10:57:33 +0000 [thread overview]
Message-ID: <20020115105733.B994@flint.arm.linux.org.uk> (raw)
In-Reply-To: <3C4401CD.3040408@debian.org>
In-Reply-To: <3C4401CD.3040408@debian.org>; from cate@debian.org on Tue, Jan 15, 2002 at 11:17:49AM +0100
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 (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-01-15 10:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 10:17 Autoconfiguration: Original design scenario Giacomo Catenazzi
2002-01-15 10:57 ` Russell King [this message]
2002-01-15 12:41 ` Giacomo Catenazzi
2002-01-15 18:34 ` Greg KH
2002-01-15 18:31 ` Eric S. Raymond
2002-01-15 23:07 ` Greg KH
2002-01-15 23:02 ` Eric S. Raymond
2002-01-15 19:16 ` Russell King
2002-01-16 8:12 ` Giacomo Catenazzi
2002-01-16 15:51 ` Kai Germaschewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020115105733.B994@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=cate@debian.org \
--cc=esr@thyrsus.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox