Talk:TechniSat AirStar-HD5000-USB: Difference between revisions
(Add chips) |
No edit summary |
||
Line 181: | Line 181: | ||
* C77331 65T C12E (U13) |
* C77331 65T C12E (U13) |
||
--[[User:Grythumn|Grythumn]] 03:37, 3 October 2007 (CEST) |
--[[User:Grythumn|Grythumn]] 03:37, 3 October 2007 (CEST) |
||
==Support== |
|||
<blockquote>With the exception of the additional PLX USB bridge, the device's components are otherwise near identical, if not the same, to its [[TechniSat AirStar-HD5000-PCI|AirStar-HD5000-PCI]] counterpart. Given that driver support for the PLX USB bridge does exist [http://www.mail-archive.com/linux-usb-devel@lists.sourceforge.net/msg42872.html], adding support for this device ''should probably not be too difficult''' (famous last words), and is likely just a matter of adding the glue code that ties all the components together.</blockquote> |
|||
I don't think this is true... the net2282 is a dual mode device; it can be used either as a PCI host, or a PCI device. It is being used in a 'Remote PCI' configuration (PCI host, USB device) on this device. The net2280.c driver looks to me to be designed for use in the PCI device configuration (PCI device, USB host). |
|||
--[[User:Grythumn|Grythumn]] 08:52, 8 March 2009 (CET) |
Latest revision as of 07:52, 8 March 2009
Any progress on updating this driver to support the newer hardware rev?
My output of lsusb -v shows the following, but the b2c2-flexcop-usb driver fails to connect to the device.
Bus 005 Device 002: ID 13d0:2282
Device Descriptor:
bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x13d0 idProduct 0x2282 bcdDevice 1.01 iManufacturer 0 iProduct 0 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 81 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 222mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 9 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x8d EP 13 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x0d EP 13 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x8e EP 14 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x0e EP 14 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x8f EP 15 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 1
dmesg output shows,
DVB: registering new adapter (FlexCop Digital TV device). b2c2-flexcop: reading of MAC address failed. b2c2-flexcop: i2c master_xfer failed b2c2-flexcop: i2c master_xfer failed b2c2-flexcop: i2c master_xfer failed mt352_read_register: readreg error (reg=127, ret==-121) b2c2-flexcop: i2c master_xfer failed nxt200x: nxt200x_readbytes: i2c read error (addr 0x0a, err == -121) Unknown/Unsupported NXT chip: 00 00 00 00 00 b2c2-flexcop: i2c master_xfer failed lgdt330x: i2c_read_demod_bytes: addr 0x59 select 0x02 error (ret == -121) b2c2-flexcop: i2c master_xfer failed b2c2-flexcop: i2c master_xfer failed stv0297_readreg: readreg error (reg == 0x80, ret == -121) b2c2-flexcop: i2c master_xfer failed mt312_read: ret == -121 b2c2-flexcop: no frontend driver found for this B2C2/FlexCop adapter usbcore: registered new interface driver b2c2_flexcop_usb usb 5-1: USB disconnect, address 2
- That your attempt failed is explained simply by the fact that there have been no steps taken towards providing a driver -- which itself is explained simply by the fact that no developer has such device and no end user (whom would be able to provide testing and feedback about any extensions to existing code) has yet to request support. That said, from brief discussion about the device, it is likely that it would be fairly simple to add support. As per the instructions on the article page, please inquire about this on the mail list.--CityK 21:22, 30 September 2007 (CEST)
Components
Top side:
- LG TDVS-H064F demodulator (P1 or U2)
- Atmel PLD: ATF750C (U8)
- clock: CTS09-CB3 45M00000 (U23)
- Flexcop-IIB MM5HG-000 (U1)
- MKAL 5298 (U22)
- 62AE N12A (U7) (looks like regulator)
- ?? (U21)
- ?? (U20)
There's an unpopulated jumper that appears to lead to U11; not checked.
Bottom:
- ISSI IS61LV256-15TL (U3)
- ATMEL616 24C08AN (U4)
- PLX NET2282-A833PC (U9)
- ATMEL 542 25640AN (U11)
- C77331 65T C12E (U13)
--Grythumn 03:37, 3 October 2007 (CEST)
Support
With the exception of the additional PLX USB bridge, the device's components are otherwise near identical, if not the same, to its AirStar-HD5000-PCI counterpart. Given that driver support for the PLX USB bridge does exist [1], adding support for this device should probably not be too difficult' (famous last words), and is likely just a matter of adding the glue code that ties all the components together.
I don't think this is true... the net2282 is a dual mode device; it can be used either as a PCI host, or a PCI device. It is being used in a 'Remote PCI' configuration (PCI host, USB device) on this device. The net2280.c driver looks to me to be designed for use in the PCI device configuration (PCI device, USB host).
--Grythumn 08:52, 8 March 2009 (CET)