search for: subvendor

On 2020/6/8 ??5:45, Michael S. Tsirkin wrote: > On Mon, Jun 08, 2020 at 05:43:58PM +0800, Jason Wang wrote: >>>> Looking at >>>> pci_match_one_device() it checks both subvendor and subdevice there. >>>> >>>> Thanks >>> But IIUC there is no guarantee that driver with a specific subvendor >>> matches in presence of a generic one. >>> So either IFC or virtio pci can win, whichever binds first. >> >> I'm not s...

On 2020/6/8 ??5:45, Michael S. Tsirkin wrote: > On Mon, Jun 08, 2020 at 05:43:58PM +0800, Jason Wang wrote: >>>> Looking at >>>> pci_match_one_device() it checks both subvendor and subdevice there. >>>> >>>> Thanks >>> But IIUC there is no guarantee that driver with a specific subvendor >>> matches in presence of a generic one. >>> So either IFC or virtio pci can win, whichever binds first. >> >> I'm not s...

...wrote: > On Mon, Jun 08, 2020 at 05:46:52PM +0800, Jason Wang wrote: >> On 2020/6/8 ??5:45, Michael S. Tsirkin wrote: >>> On Mon, Jun 08, 2020 at 05:43:58PM +0800, Jason Wang wrote: >>>>>> Looking at >>>>>> pci_match_one_device() it checks both subvendor and subdevice there. >>>>>> >>>>>> Thanks >>>>> But IIUC there is no guarantee that driver with a specific subvendor >>>>> matches in presence of a generic one. >>>>> So either IFC or virtio pci can win, whichever bind...

...wrote: > On Mon, Jun 08, 2020 at 05:46:52PM +0800, Jason Wang wrote: >> On 2020/6/8 ??5:45, Michael S. Tsirkin wrote: >>> On Mon, Jun 08, 2020 at 05:43:58PM +0800, Jason Wang wrote: >>>>>> Looking at >>>>>> pci_match_one_device() it checks both subvendor and subdevice there. >>>>>> >>>>>> Thanks >>>>> But IIUC there is no guarantee that driver with a specific subvendor >>>>> matches in presence of a generic one. >>>>> So either IFC or virtio pci can win, whichever bind...

...a virtio driver to it? It works. > I'm guessing no otherwise they wouldn't need IFC driver, right? > Looking at the driver, they used a dedicated bar for dealing with virtqueue state save/restore. It > > >> Looking at >> pci_match_one_device() it checks both subvendor and subdevice there. >> >> Thanks > > But IIUC there is no guarantee that driver with a specific subvendor > matches in presence of a generic one. > So either IFC or virtio pci can win, whichever binds first. I'm not sure I get there. But I try manually bind IFCVF to q...

...a virtio driver to it? It works. > I'm guessing no otherwise they wouldn't need IFC driver, right? > Looking at the driver, they used a dedicated bar for dealing with virtqueue state save/restore. It > > >> Looking at >> pci_match_one_device() it checks both subvendor and subdevice there. >> >> Thanks > > But IIUC there is no guarantee that driver with a specific subvendor > matches in presence of a generic one. > So either IFC or virtio pci can win, whichever binds first. I'm not sure I get there. But I try manually bind IFCVF to q...

Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: This is a digitally signed message part. Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20080617/73afe727/attachment.pgp

...nks >> > Then regular virtio will still bind to it. It has > > drivers/virtio/virtio_pci_common.c: { PCI_DEVICE(PCI_VENDOR_ID_REDHAT_QUMRANET, PCI_ANY_ID) }, > > IFCVF use this to avoid the binding to regular virtio device. Looking at pci_match_one_device() it checks both subvendor and subdevice there. Thanks

...nks >> > Then regular virtio will still bind to it. It has > > drivers/virtio/virtio_pci_common.c: { PCI_DEVICE(PCI_VENDOR_ID_REDHAT_QUMRANET, PCI_ANY_ID) }, > > IFCVF use this to avoid the binding to regular virtio device. Looking at pci_match_one_device() it checks both subvendor and subdevice there. Thanks

...ev.pcib.0.%location: handle=\_SB_.PCI0 dev.pcib.0.%pnpinfo: _HID=PNP0A03 _UID=0 dev.pcib.0.%parent: acpi0 dev.pcib.0.wake: 0 dev.pcib.1.%desc: ACPI PCI-PCI bridge dev.pcib.1.%driver: pcib dev.pcib.1.%location: slot=1 function=0 handle=\_SB_.PCI0.P0P1 dev.pcib.1.%pnpinfo: vendor=0x1106 device=0xb188 subvendor=0x0080 subdevice=0x0000 class=0x060400 dev.pcib.1.%parent: pci0 dev.pcib.2.%desc: ACPI PCI-PCI bridge dev.pcib.2.%driver: pcib dev.pcib.2.%location: slot=19 function=0 handle=\_SB_.PCI0.P0P7 dev.pcib.2.%pnpinfo: vendor=0x1106 device=0x287b subvendor=0x0000 subdevice=0x0000 class=0x060400 dev.pcib.2...

...=> _NXXXXXXX,1,Answer exten => _NXXXXXXX,2,Dial(Zap/g1/${EXTEN}) I can to see following in /var/log/messages when I make outgoing call. Jul 20 00:50:26 boldsoft kernel: Zapata Telephony Interface Registered on major 196 Jul 20 00:50:26 boldsoft kernel: ZapTel device: vendor=e159 device=1 subvendor=8085 Jul 20 00:50:26 boldsoft kernel: wcfxo0: <Wildcard X101P> port 0xe800-0xe8ff mem 0xfaffe000-0xfaffefff irq 18 at device 9.0 on pci2 Jul 20 00:50:26 boldsoft kernel: ZapTel Attach for wcfxo0: deviceID : 0xe159 Jul 20 00:50:26 boldsoft kernel: wcfxo: DAA mode is 'FCC' Jul 20 00:50:...

...=> _NXXXXXXX,1,Answer exten => _NXXXXXXX,2,Dial(Zap/g1/${EXTEN}) I can to see following in /var/log/messages when I make outgoing call. Jul 20 00:50:26 boldsoft kernel: Zapata Telephony Interface Registered on major 196 Jul 20 00:50:26 boldsoft kernel: ZapTel device: vendor=e159 device=1 subvendor=8085 Jul 20 00:50:26 boldsoft kernel: wcfxo0: <Wildcard X101P> port 0xe800-0xe8ff mem 0xfaffe000-0xfaffefff irq 18 at device 9.0 on pci2 Jul 20 00:50:26 boldsoft kernel: ZapTel Attach for wcfxo0: deviceID : 0xe159 Jul 20 00:50:26 boldsoft kernel: wcfxo: DAA mode is 'FCC' Jul 20 00:50:...

...ied moving the modules to 3 and 4 (and changed everything accordingly). I even tried this: Comment out this line on zaptel/zconfig.h and recompile zaptel. /* * Uncomment if you happen have an early TDM400P Rev H which * sometimes forgets its PCI ID to have wcfxs match essentially all * subvendor ID's */ /* #define TDM_REVH_MATCHALL */ This is just a basic test setup for my home. I want to get an analog phone and 2 Cisco 7910 phones working. Any help would be appreciated. Jeff Borders

...0x1AF4 Which is of course not an IFCVF vendor id, it's the Red Hat vendor ID. I missed that. Does it actually work if you bind a virtio driver to it? I'm guessing no otherwise they wouldn't need IFC driver, right? > Looking at > pci_match_one_device() it checks both subvendor and subdevice there. > > Thanks But IIUC there is no guarantee that driver with a specific subvendor matches in presence of a generic one. So either IFC or virtio pci can win, whichever binds first. I guess we need to blacklist IFC in virtio pci probe code. Ugh. -- MST

On Mon, Jun 08, 2020 at 05:43:58PM +0800, Jason Wang wrote: > > > > > Looking at > > > pci_match_one_device() it checks both subvendor and subdevice there. > > > > > > Thanks > > > > But IIUC there is no guarantee that driver with a specific subvendor > > matches in presence of a generic one. > > So either IFC or virtio pci can win, whichever binds first. > > > I'm not sur...

On Mon, Jun 08, 2020 at 05:46:52PM +0800, Jason Wang wrote: > > On 2020/6/8 ??5:45, Michael S. Tsirkin wrote: > > On Mon, Jun 08, 2020 at 05:43:58PM +0800, Jason Wang wrote: > > > > > Looking at > > > > > pci_match_one_device() it checks both subvendor and subdevice there. > > > > > > > > > > Thanks > > > > But IIUC there is no guarantee that driver with a specific subvendor > > > > matches in presence of a generic one. > > > > So either IFC or virtio pci can win, whichever binds...

...at 05:46:52PM +0800, Jason Wang wrote: > > > On 2020/6/8 ??5:45, Michael S. Tsirkin wrote: > > > > On Mon, Jun 08, 2020 at 05:43:58PM +0800, Jason Wang wrote: > > > > > > > Looking at > > > > > > > pci_match_one_device() it checks both subvendor and subdevice there. > > > > > > > > > > > > > > Thanks > > > > > > But IIUC there is no guarantee that driver with a specific subvendor > > > > > > matches in presence of a generic one. > > > > > > So...

...uffer': 02: None 00.0: 11001 VESA Framebuffer [Created at bios.459] Unique ID: rdCR.fRULN9k9OD4 Hardware Class: framebuffer Model: "Intel(r)Cantiga Graphics Controller" Vendor: "Intel Corporation" Device: "Intel(r)Cantiga Graphics Controller" SubVendor: "Intel(r)Cantiga Graphics Chip Accelerated VGA BIOS" SubDevice: Revision: "Hardware Version 0.0" Memory Size: 31 MB + 960 kB Memory Range: 0xd0000000-0xd1feffff (rw) Mode 0x0305: 1024x768 (+1024), 8 bits Mode 0x0317: 1024x768 (+2048), 16 bits Mode 0x0318: 1...

...eue *vq) +{ + if (vq->vring.avail->flags & VRING_AVAIL_F_NO_INTERRUPT) + return; + + vdev->isr = 1; + virtio_update_irq(vdev); +} + +VirtIODevice *virtio_init_pci(PCIBus *bus, const char *name, + uint16_t vendor, uint16_t device, + uint16_t subvendor, uint16_t subdevice, + uint8_t class_code, uint8_t subclass_code, + uint8_t pif, size_t config_size, + size_t struct_size) +{ + VirtIODevice *vdev; + PCIDevice *pci_dev; + uint8_t *config; + + pci_dev = pci_register_device(bus, name, st...

...eue *vq) +{ + if (vq->vring.avail->flags & VRING_AVAIL_F_NO_INTERRUPT) + return; + + vdev->isr = 1; + virtio_update_irq(vdev); +} + +VirtIODevice *virtio_init_pci(PCIBus *bus, const char *name, + uint16_t vendor, uint16_t device, + uint16_t subvendor, uint16_t subdevice, + uint8_t class_code, uint8_t subclass_code, + uint8_t pif, size_t config_size, + size_t struct_size) +{ + VirtIODevice *vdev; + PCIDevice *pci_dev; + uint8_t *config; + + pci_dev = pci_register_device(bus, name, st...