Date: Wed, 29 Sep 2004 18:00:58 +0100 From: "Steven Hartland" <killing@multiplay.co.uk> To: "Brenden Grace" <bcg@intelli7.com>, <freebsd-hackers@freebsd.org> Subject: Re: Device probe issue with an em(4) compatible device Message-ID: <010a01c4a645$e6356630$b3db87d4@multiplay.co.uk> References: <1096476707.2670.1088.camel@localhost.localdomain>
next in thread | previous in thread | raw e-mail | index | archive | help
If its compatible with em why not just alter the em to support
the additional id's?
Steve
----- Original Message -----
From: "Brenden Grace" <bcg@intelli7.com>
> I am writing a network driver for a em(4) compatible chip. I know the
> specific subvendor id and subdevice id, but the em(4) driver seems to
> attach to the device before my driver can. Is this because the em_probe
> is occurring before my probe AND because the em_probe is allowing for
> PCI_ANY_ID for subvendor subdevice ids (the vendor and device ids of my
> card are identical to an actual Intel card)? If so the solution then
> would be to have the em driver return a number less than zero in
> em_probe and my driver's probe to return a number greater than the
> em_probes's return?
>
> On a side not, would it also not be more correct for FreeBSD drivers in
> the tree to return a negative number for _any_ device that accepts a
> PCI_ANY_ID value?
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137
or return the E.mail to postmaster@multiplay.co.uk.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?010a01c4a645$e6356630$b3db87d4>