public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Giacomo Catenazzi <cate@debian.org>
Cc: Russell King <rmk@arm.linux.org.uk>,
	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:34:32 -0800	[thread overview]
Message-ID: <20020115183432.GC27059@kroah.com> (raw)
In-Reply-To: <3C4401CD.3040408@debian.org> <20020115105733.B994@flint.arm.linux.org.uk> <3C442395.8010500@debian.org>
In-Reply-To: <3C442395.8010500@debian.org>

On Tue, Jan 15, 2002 at 01:41:57PM +0100, Giacomo Catenazzi wrote:
> 
> 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.

The hisax driver already has a MODULE_DEVICE_TABLE entry for it's pci
devices, and this data shows up in the modules.pcimap table in the
modules directory.

Russell, when /sbin/hotplug is part of the initramfs in 2.5, the driver
will automatically be loaded for your new card, IF you have all the
different modules already built.  You will not need autoconfigure, just
a good vendor kernel :)

Giacomo, please, please, please, just use the info in the
MODULE_DEVICE_TABLE entries for your autoconfigure program.  Don't try
to keep all of this data up to date by hand, just use the info that is
already in the kernel.  It is a battle you will always loose.  Automate
this process (David Brownell has made a proposal that will work for
you), and you will never have to generate those PCI and USB tables by
hand again.

One other autoconfigure problem that I don't think anyone has mentioned,
USB devices that only show up when they want to transfer data to/from
the host.  Like all of the Palm based devices.  They don't stay
connected long enough for a "probe all the busses" tool like
you are currently developing to detect.

thanks,

greg k-h

  reply	other threads:[~2002-01-15 18:38 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
2002-01-15 12:41   ` Giacomo Catenazzi
2002-01-15 18:34     ` Greg KH [this message]
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=20020115183432.GC27059@kroah.com \
    --to=greg@kroah.com \
    --cc=cate@debian.org \
    --cc=esr@thyrsus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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