Jeroen Ruigrok van der Werven writes:
> >    found-> vendor=0x8086, dev=0x2413, revid=0x02
> >         class=0c-05-00, hdrtype=0x00, mfdev=0
> >                  ^^^^^^^^
> >         subordinatebus=0        secondarybus=0
> >         intpin=b, irq=10
> >         map[20]: type 1, range 32, base 0000fe00, size  4
> pciconf -l will probably show the class as 0x0c0500 I guess?


> >The class/sub-class/programming interface (highlighted above)
> >indicates a SMBus device as specified by PCI 2.2.
> >
> >However, I'm not sure what that is. Adding the "smbus" device and
> >friends to the kernel config doesn't cause this device to be
> >detected.  You'd think all I needed to do then would be to add the
> >device ID to a list in the smbus driver somewhere, but I can't find
> >that list. Does "smbus_pci.c" not exist yet?
> Normally, that would be enough yes.  I think you want:
> src/sys/dev/iicbus and src/sys/dev/smbus

Those are in, but there is no driver that recognizes the
device and vendor ID above.  Guess I'll have to write one
as soon as I can get the PCI 2.2 spec.


Archie Cobbs   *   Whistle Communications, Inc.  *

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to