On Mon, 25 Oct 1999 14:15:22 -0300 
 David Maxwell <david@fundy.ca> wrote:

 > Further to my own question, in case I wasn't clear.. (also trying a different list :-)
 > 
 > In sys/dev/isapnp/isapnpdevs for example, a device line looks like this:
 > 
 > devlogic        com     OZO8039         0       Zoom 56k flex
                           ^^^^^^^
This is effectively "vendor/product" info ... encoded the same way EISA
vendor/product info is encoded.  ISA PnP devices have "decompat" strings
("this product is compatible with this standard interface") and "devlogic"
strings (which uniquely identify the product).

Because ISA PnP is PC crap, many device don't behave according to the
specs, so we match "devlogic" on some devices which are compatible but
don't explicitly say that they are.

 > In sys/dev/pci/pcidevs, you get vendors and products:
 > 
 > vendor 3COM             0x10B7  3Com
 > product 3COM 3C590      0x5900  3c590 Ethernet
 > 
 > Now, fair enough, networks cards are less standardized than com ports,
 > but can comeone point me to details on what's involved in trying to get
 > a pci internal modem working?

The only way you're going to get that device working is to get programming
docs from 3Com.  And then be prepared to write a lot of code.

I have never ever ever seen a PCI modem that wasn't a soft-modem, which
is why there isn't a PCI `com' attachment that's a modem (the current
com-on-PCI are all attached to known PCI boards with 16x50 UARTs on them,
and they're just serial boards, not modems).

        -- Jason R. Thorpe <thorpej@nas.nasa.gov>