Mauro, Please pull from http://jusst.de/hg/v4l-dvb for the following changes for the AZ6027 DVB USB DVB-S2 CI device There has been a shortage of supported CI devices. The driver provides support for the following: - Azurewave VP-6027 or AD-SB301 or some other name by which it is called. Additionally, it supports 2 other re branded USB devices as well, viz, - Technisat DVB-S2 HD CI - Terratec DVB-S2 CI If any other STB0899/STB6100 based similar devices are known, hopefully we can add in support in to the same driver. changeset: 14169:fcd125343873 http://jusst.de/hg/v4l-dvb/rev/fcd125343873 AZ6027: Fix build warnings changeset: 14168:f0304f694aca http://jusst.de/hg/v4l-dvb/rev/f0304f694aca AZ6027: Fix checkpatch violations changeset: 14167:1af35f1537e7 http://jusst.de/hg/v4l-dvb/rev/1af35f1537e7 AZ6027: Add driver supported ID's changeset: 14166:d40a2eb97f77 http://jusst.de/hg/v4l-dvb/re/d40a2eb97f77 AZ6027: Update Build changeset: 14165:eefc5eae5449 http://jusst.de/hg/v4l-dvb/rev/eefc5eae5449 AZ6027: Add driver supported ID's changeset: 14164:e961a33a85ac http://jusst.de/hg/v4l-dvb/rev/e961a33a85ac AZ6027: Initial import of the driver It appears to function prima facie; [ 499.201809] TUPLE type:0x1b length:37 [ 499.202184] 0x00: 0xcf . [ 499.202561] 0x01: 0x04 . [ 499.202934] 0x02: 0x09 . [ 499.203308] 0x03: 0x37 7 [ 499.203682] 0x04: 0x55 U [ 499.204057] 0x05: 0x4d M [ 499.204432] 0x06: 0x5d ] [ 499.204807] 0x07: 0x1d . [ 499.205182] 0x08: 0x56 V [ 499.205557] 0x09: 0x22 " [ 499.205931] 0x0a: 0xc0 . [ 499.206396] 0x0b: 0x09 . [ 499.206807] 0x0c: 0x44 D [ 499.207181] 0x0d: 0x56 V [ 499.207555] 0x0e: 0x42 B [ 499.207930] 0x0f: 0x5f _ [ 499.208305] 0x10: 0x48 H [ 499.208679] 0x11: 0x4f O [ 499.209054] 0x12: 0x53 S [ 499.209428] 0x13: 0x54 T [ 499.209803] 0x14: 0x00 . [ 499.210178] 0x15: 0xc1 . [ 499.210552] 0x16: 0x0e . [ 499.210928] 0x17: 0x44 D [ 499.211303] 0x18: 0x56 V [ 499.211677] 0x19: 0x42 B [ 499.212052] 0x1a: 0x5f _ [ 499.212427] 0x1b: 0x43 C [ 499.212801] 0x1c: 0x49 I [ 499.213176] 0x1d: 0x5f _ [ 499.213551] 0x1e: 0x4d M [ 499.213926] 0x1f: 0x4f O [ 499.214388] 0x20: 0x44 D [ 499.214802] 0x21: 0x55 U [ 499.215175] 0x22: 0x4c L [ 499.215549] 0x23: 0x45 E [ 499.215924] 0x24: 0x00 . [ 499.216673] TUPLE type:0x14 length:0 [ 499.217048] END OF CHAIN TUPLE type:0xff [ 499.217050] Valid DVB CAM detected MANID:ffff DEVID:1 CONFIGBASE:0x1fe CONFIGOPTION:0xf [ 499.217053] dvb_ca_en50221_set_configoption [ 499.217672] Set configoption 0xf, read configoption 0xf [ 499.217922] DVB CAM validated successfully [ 499.518210] dvb_ca_en50221_link_init [ 499.518458] dvb_ca_en50221_wait_if_status [ 499.518709] dvb_ca_en50221_wait_if_status succeeded timeout:0 [ 499.518711] dvb_ca_en50221_read_data [ 499.520206] Received CA packet for slot 0 connection id 0x0 last_frag:0 size:0x2 [ 499.520455] Chosen link buffer size of 128 [ 499.520706] dvb_ca_en50221_wait_if_status [ 499.520957] dvb_ca_en50221_wait_if_status succeeded timeout:0 [ 499.520959] dvb_ca_en50221_write_data [ 499.523082] Wrote CA packet for slot 0, connection id 0x0 last_frag:0 size:0x2 [ 499.523830] dvb_ca adapter 0: DVB CAM detected and initialised successfully Regards, Manu -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
