Re: Device probe issue with an em(4) compatible device

From: M. Warner Losh (imp_at_bsdimp.com)
Date: 09/30/04

  • Next message: Ivan Voras: "GEOM (ggate) compression consumer +problem"
    Date: Wed, 29 Sep 2004 18:06:55 -0600 (MDT)
    To: bcg@intelli7.com
    
    

    In message: <1096487538.2670.1147.camel@localhost.localdomain>
                Brenden Grace <bcg@intelli7.com> writes:
    : On Wed, 2004-09-29 at 15:32, Peter Buckingham wrote:
    : > experience then just not compiling in the em driver or an ugly like i
    : > describe (or you suggest) should be fine.
    :
    : I wasn't trying to be rude, but DEVICE_PROBE(9) seems to describe how
    : conflicts like this should be handled. I was wondering if I am in fact
    : correct that devices that attempt to be generic enough for wide support
    : (accepting PCI_ANY_ID) should also properly pass the probing (by
    : returning some negative) so that a driver that may better fit the exact
    : device can attach.

    Well, it does match on the VENDOR ID and DEVICE, so it isn't that
    generic. The subvendor field is generally a don't care field for
    drivers in FreeBSD, so it is just following existing practices. Maybe
    that practice should be revisited, but that's why em_probe does things
    the way it does.

    If you need em to not attach, you'll have to hack em in your tree to
    return some small negative number.

    Chances are excellent that FreeBSD 6 will have facilities to address
    these issues (they are needed both for 'vendor supplied updated
    drivers' as well as 'please load me when you see this sort of card').

    Warner
    _______________________________________________
    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"


  • Next message: Ivan Voras: "GEOM (ggate) compression consumer +problem"

    Relevant Pages

    • Re: TRAP 0000 in OS2KRNL
      ... Because the driver writers used the available samples as best practices. ... One needs to keep in mind that most of the driver development we are ...
      (comp.os.os2.bugs)
    • Re: nvidia-driver rebooting machine on X startup
      ... Same driver different hw, same os version... ... FreeBSD is a registered trademark of The FreeBSD Foundation. ... acpi0: <Nvidia AWRDACPI> on motherboard ... Identifier "Microsoft_Natural" ...
      (freebsd-questions)
    • Re: Where to find good/cheap tech support
      ... If you have a bug in a driver, ... Fedora Core, openbsd, freebsd, and netbsd. ... I got a SCSI controller card and an ATA/IDE controller ...
      (freebsd-questions)
    • Re: Experiences with 7.0-CURRENT and vmware.
      ... difference to time keeping on FreeBSD 7 and nor does it seem to have any ... FreeBSD-7 uses the "em" driver. ... Has VMware changed what network hardware they emulate, ... I would advise instead setting up an SSH key ...
      (freebsd-current)
    • Re: Experiences with 7.0-CURRENT and vmware.
      ... difference to time keeping on FreeBSD 7 and nor does it seem to have any ... FreeBSD-7 uses the "em" driver. ... Has VMware changed what network hardware they emulate, ... I would advise instead setting up an SSH key ...
      (freebsd-hackers)