[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Device detection?



On Fri, Mar 05, 1999 at 01:23:25AM -0500, Steve Dunham wrote:
> Stephen Crowley <crow@debian.org> writes:
> 
> > On Thu, Mar 04, 1999 at 10:58:13PM -0500, Randolph Chung wrote:
> 
> > > In that case.... how do you propose gathering this list? The
> > > ultimate goal of course is better and more automated hardware
> > > detection; it matters much less how we do it than that we *can* do
> > > it. It just seems that if someone has already done the detection
> > > for us, we should use the info. Of course, if we can develop a
> > > better strategy, that'd be nice too......
> 
> > Well, looking at the source for the modules can provide a good start? maybe
> > those silly .inf files on windows driver disks could provide some help too.
> 
> Well, for PCI stuff, Red Hat's install has a nice list, which IIRC is
> generated from headers in the kernel source.
> 
> > > does Windows also detect hardware by identifying PCI/PnP ids? can
> > > we get our hands on a list of ids somewhere?
> 
> PCI/PnP ids is the easy part - the hard part is detecting the other
> types of hardware.
>

Yes, I was wondering if it would be possible to do a brute force scan for
some older legacy hardware. Just cycle through the i/o and irq ports for
some commonly used hardware. Some devices might lock up on this though, so
they would have to be installed manually.

> To map PCI ids to drivers, look at "misc/src/install/pci-probing" in any
> RedHat archive. 
> 
> 
> Steve
> dunham@cse.msu.edu
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 
> 

-- 
/-----------------------------------------------------------\
|Stephen Crowley      stephenc@wf.net, crow@debian.org      |
|Debian GNU/Linux     http://www.debian.org                 |
|GPG Key              http://va.debian.org/~crow/public.key |
\--- 8A8B 3B82 6EA7 CF4E 01A5  5B21 B378 981D D2E1 0D85 ----/
     


Reply to: