Device probe issue with an em(4) compatible device
From: Brenden Grace (bcg_at_intelli7.com)
Date: 09/29/04
- Previous message: Igor Serikov: "FreeBSD 4.10 system stops responding"
- Next in thread: Steven Hartland: "Re: Device probe issue with an em(4) compatible device"
- Reply: Steven Hartland: "Re: Device probe issue with an em(4) compatible device"
- Maybe reply: Brenden Grace: "Re: Device probe issue with an em(4) compatible device"
- Maybe reply: Brenden Grace: "Re: Device probe issue with an em(4) compatible device"
- Reply: M. Warner Losh: "Re: Device probe issue with an em(4) compatible device"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: freebsd-hackers@freebsd.org Date: Wed, 29 Sep 2004 12:51:47 -0400
I have a somewhat limited knowledge of FreeBSD's device system, so
forgive (and correct) me if I get any of this wrong.
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?
Thanks in advance for the clarification/help.
-- Brenden C. Grace Intelli7 _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
- Previous message: Igor Serikov: "FreeBSD 4.10 system stops responding"
- Next in thread: Steven Hartland: "Re: Device probe issue with an em(4) compatible device"
- Reply: Steven Hartland: "Re: Device probe issue with an em(4) compatible device"
- Maybe reply: Brenden Grace: "Re: Device probe issue with an em(4) compatible device"
- Maybe reply: Brenden Grace: "Re: Device probe issue with an em(4) compatible device"
- Reply: M. Warner Losh: "Re: Device probe issue with an em(4) compatible device"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
- Re: Simple ADS5273 -> Xilinx Interconnect Model
... Is the ADS5273 a non-standard LVDS "style" of driver? ... If there are
excessive reflections from the ... reduced-amplitude probe point. ... (comp.arch.fpga) - Re: patch bus_add_device-losing-an-error-return-from-the-probe-metho
... How do you feel about the flag that I've been proposing that a driver that needs to
probe for its hardware could set and that says "if we return an error the hardware's reallyreally
not present and the device should not register"? ... adding a .discover method to struct
device_driver that noone other than drivers for this old non generically discoverable hardware would
set but which would make a registration fail if set and returning < 0? ... struct snd_card
*card; ... (Linux-Kernel) - Re: Ziatech 5503 watchdog driver
... :>> driver, I have no way to identify that the system has the driver, so ...
would simply probe various I/O ports. ... Assuming no useful information exists,
is it enough to let the ... Maxime suggested that I use device hints ... (freebsd-hackers) - Re: [ALSA STABLE 3/3] a few more -- unregister platform device again if probe was unsuccessf
... with nothing other than the driver available to probe ... bus",
where the _user_ would first need to setup the hardware from userspace by echoing values into sysfs.
... With an ISA bus type, ... (Linux-Kernel) - Re: [patch/RFC 2.6.18-rc] platform_device_probe(), to conserve memory
... sections for typical system configurations. ... that pointers to init
section code (like, ideally, probe support) must ... driver methods) when those
pointers would be invalid. ... (Linux-Kernel)