Marshall Henderson
2013-Apr-02 20:27 UTC
[asterisk-users] TigerJet 320G Chip / TDM400 Chipset / DAHDI Support
Hi, I'm curious what chip Digium is using in the latest TDM400 cards. Specifically, to my recollection, they used to use the TigerJet 320G, however somewhat recently, Tigerjet was bought out, and now the 320G is no longer produced. Maybe a better question is: is there a way I can take the latest DAHDI source and get a list of supported chipsets from it? Thanks. MCH -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20130402/26191e95/attachment.htm>
Tzafrir Cohen
2013-Apr-03 09:52 UTC
[asterisk-users] TigerJet 320G Chip / TDM400 Chipset / DAHDI Support
On Tue, Apr 02, 2013 at 03:27:55PM -0500, Marshall Henderson wrote:> Hi, I'm curious what chip Digium is using in the latest TDM400 cards. > Specifically, to my recollection, they used to use the TigerJet 320G, > however somewhat recently, Tigerjet was bought out, and now the 320G is no > longer produced. > > Maybe a better question is: is there a way I can take the latest DAHDI > source and get a list of supported chipsets from it?Latest tarballs: http://downloads.asterisk.org/pub/telephony/dahdi-linux/ But the latest source is in the git repository: git clone git://git.asterisk.org/dahdi/linux.git It lacks the full history of DAHDI and Zaptel. You can find those in the Subversion repositories in svn.asterisk.org or . -- Tzafrir Cohen icq#16849755 jabber:tzafrir.cohen at xorcom.com +972-50-7952406 mailto:tzafrir.cohen at xorcom.com http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir
Marshall Henderson
2013-Apr-03 18:34 UTC
[asterisk-users] TigerJet 320G Chip / TDM400 Chipset / DAHDI Support
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?
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?
MCH
On Wed, Apr 3, 2013 at 8:58 AM, Patrick Lists <
asterisk-list at puzzled.xs4all.nl> wrote:
> On 04/03/2013 02:48 PM, Marshall Henderson wrote:
>
>> Hi Tzafrir-
>>
>> I know where to find the DAHDI source, but I was more asking where to
>> actually find which chipsets are supported within the source. Any
>> thoughts?
>>
>
> Have you checked the PCI IDs in the source?
>
> Regards,
> Patrick
>
>
>
> --
> ______________________________**______________________________**_________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
> http://www.asterisk.org/hello
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>
http://lists.digium.com/**mailman/listinfo/asterisk-**users<http://lists.digium.com/mailman/listinfo/asterisk-users>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20130403/8593a3fe/attachment.htm>
Patrick Lists
2013-Apr-03 18:55 UTC
[asterisk-users] TigerJet 320G Chip / TDM400 Chipset / DAHDI Support
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