[asterisk-users] TigerJet 320G Chip / TDM400 Chipset / DAHDI Support

[Patrick Lists]

On 04/03/2013 08:34 PM, Marshall Henderson wrote:
> Hi Patrick- Yes, I did find the list of PCI IDs (I think). Do these look
> right (from wctdm.c):
>
> static DEFINE_PCI_DEVICE_TABLE(wctdm_pci_tbl) = {
>          { 0xe159, 0x0001, 0xa159, PCI_ANY_ID, 0, 0, (unsigned long)
> &wctdm },
>          { 0xe159, 0x0001, 0xe159, PCI_ANY_ID, 0, 0, (unsigned long)
> &wctdm },
>          { 0xe159, 0x0001, 0xb100, PCI_ANY_ID, 0, 0, (unsigned long)
> &wctdme },
>          { 0xe159, 0x0001, 0xb1d9, PCI_ANY_ID, 0, 0, (unsigned long)
> &wctdmi },
>          { 0xe159, 0x0001, 0xb118, PCI_ANY_ID, 0, 0, (unsigned long)
> &wctdmi },
>          { 0xe159, 0x0001, 0xb119, PCI_ANY_ID, 0, 0, (unsigned long)
> &wctdmi },
>          { 0xe159, 0x0001, 0xa9fd, PCI_ANY_ID, 0, 0, (unsigned long)
> &wctdmh },
>          { 0xe159, 0x0001, 0xa8fd, PCI_ANY_ID, 0, 0, (unsigned long)
> &wctdmh },
>          { 0xe159, 0x0001, 0xa800, PCI_ANY_ID, 0, 0, (unsigned long)
> &wctdmh },
>          { 0xe159, 0x0001, 0xa801, PCI_ANY_ID, 0, 0, (unsigned long)
> &wctdmh },
>          { 0xe159, 0x0001, 0xa908, PCI_ANY_ID, 0, 0, (unsigned long)
> &wctdmh },
>          { 0xe159, 0x0001, 0xa901, PCI_ANY_ID, 0, 0, (unsigned long)
> &wctdmh },
> #ifdef TDM_REVH_MATCHALL
>          { 0xe159, 0x0001, PCI_ANY_ID, PCI_ANY_ID, 0, 0, (unsigned long)
> &wctdmh },
> #endif
>          { 0 }
> };
>
> So, next question, how do I take those device IDs and find the
> associated chip?

Look up the PCI ID at for example:

http://pciids.sourceforge.net/
http://www.pcidatabase.com/

The 0x159 is the TigerJet chip. The third column is the vendor. So if 
you lookup 0xb100 you will find that it is OpenVox.

> Going a step further, after a bit of research it appears some
> manufacturers have gone away from dedicated hardware chips like the
> TigerJet 320G to FPGA general purpose chips with firmware to control
> operation. Is this correct? Any thoughts?

No idea so no thoughts :-)

Regards,
Patrick