From: "Eric S. Raymond" <esr@thyrsus.com>
To: Greg KH <greg@kroah.com>
Cc: Giacomo Catenazzi <cate@debian.org>,
Russell King <rmk@arm.linux.org.uk>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Autoconfiguration: Original design scenario
Date: Tue, 15 Jan 2002 13:31:30 -0500 [thread overview]
Message-ID: <20020115133130.A3197@thyrsus.com> (raw)
In-Reply-To: <3C4401CD.3040408@debian.org> <20020115105733.B994@flint.arm.linux.org.uk> <3C442395.8010500@debian.org> <20020115183432.GC27059@kroah.com>
In-Reply-To: <20020115183432.GC27059@kroah.com>; from greg@kroah.com on Tue, Jan 15, 2002 at 10:34:32AM -0800
Greg KH <greg@kroah.com>:
> Giacomo, please, please, please, just use the info in the
> MODULE_DEVICE_TABLE entries for your autoconfigure program.
Giacomo will probably answer definitively, but I believe he is already
generating all of the PCI, PNP, and module probes by script. We're planning
to ship the probe table generator with a future CML2 version.
> 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.
Which is why the "standalone" mode of the autoconfigurator turns all that
stuff modular. The autoprobe doesn't, it's intended to generate a facilities
report that can be used to tune by hand.
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
Never trust a man who praises compassion while pointing a gun at you.
next prev parent reply other threads:[~2002-01-15 18:49 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
2002-01-15 18:31 ` Eric S. Raymond [this message]
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=20020115133130.A3197@thyrsus.com \
--to=esr@thyrsus.com \
--cc=cate@debian.org \
--cc=greg@kroah.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.