Support or LME2510(C) DM04/QQBOX USB DVB-S BOXES.
Subsystems (3)
PATCH 1/1 Support or LME2510(C) DM04/QQBOX USB DVB-S BOXES.
DM04/QQBOX DVB-S USB BOX with LME2510C+SHARP:BS2F7HZ7395 or LME2510+LGTDQT-P001F tuner.
patch also requires patches.
140351 Support for Sharp IX2505V (marked B0017) DVB-S silicon tuner
140361 STV0288 Incorrect bit sample for Vitterbi status.
These patches should be applied to v4l-dvb-a4c762698bcb.
Patch 116279 also needs to be applied.
Documentation/dvb/get_dvb_firmware +44 -1
@@ -26,7 +26,8 @@ use IO::Handle; "dec3000s", "vp7041", "dibusb", "nxt2002", "nxt2004", "or51211", "or51132_qam", "or51132_vsb", "bluebird", "opera1", "cx231xx", "cx18", "cx23885", "pvrusb2", "mpc718", - "af9015", "ngene"); + "af9015", "ngene", "lme2510_lg", "lme2510c_s7395", + "lme2510c_s7395_old"); # Check args syntax() if (scalar(@ARGV) != 1);
@@ -567,6 +568,48 @@ sub ngene { "$file1, $file2"; } +sub lme2510_lg { + my $sourcefile = "LMEBDA_DVBS.sys"; + my $hash = "fc6017ad01e79890a97ec53bea157ed2"; + my $outfile = "dvb-usb-lme2510-lg.fw"; + my $hasho = "caa065d5fdbd2c09ad57b399bbf55cad"; + + checkstandard(); + + verify($sourcefile, $hash); + extract($sourcefile, 4168, 3841, $outfile); + verify($outfile, $hasho); + $outfile; +} + +sub lme2510c_s7395 { + my $sourcefile = "US2A0D.sys"; + my $hash = "b0155a8083fb822a3bd47bc360e74601"; + my $outfile = "dvb-usb-lme2510c-s7395.fw"; + my $hasho = "3a3cf1aeebd17b6ddc04cebe131e94cf"; + + checkstandard(); + + verify($sourcefile, $hash); + extract($sourcefile, 37248, 3720, $outfile); + verify($outfile, $hasho); + $outfile; +} + +sub lme2510c_s7395_old { + my $sourcefile = "LMEBDA_DVBS7395C.sys"; + my $hash = "7572ae0eb9cdf91baabd7c0ba9e09b31"; + my $outfile = "dvb-usb-lme2510c-s7395.fw"; + my $hasho = "90430c5b435eb5c6f88fd44a9d950674"; + + checkstandard(); + + verify($sourcefile, $hash); + extract($sourcefile, 4208, 3881, $outfile); + verify($outfile, $hasho); + $outfile; +} + # --------------------------------------------------------------- # Utilities
Documentation/dvb/lmedm04.txt new file +55 -0
55 lines not on this page · raw message
drivers/media/IR/keymaps/Makefile +1 -0
@@ -38,6 +38,7 @@ obj-$(CONFIG_RC_MAP) += rc-adstech-dvb-t-pci.o \ rc-kworld-315u.o \ rc-kworld-plus-tv-analog.o \ rc-lirc.o \ + rc-lme2510.o \ rc-manli.o \ rc-msi-tvanywhere.o \ rc-msi-tvanywhere-plus.o \
drivers/media/IR/keymaps/rc-lme2510.c new file +68 -0
68 lines not on this page · raw message
drivers/media/dvb/dvb-usb/Kconfig +11 -0
@@ -346,3 +346,14 @@ config DVB_USB_AZ6027 select DVB_STB6100 if !DVB_FE_CUSTOMISE help Say Y here to support the AZ6027 device + +config DVB_USB_LME2510 + tristate "LME DM04/QQBOX DVB-S USB2.0 support" + depends on DVB_USB + select DVB_TDA10086 if !DVB_FE_CUSTOMISE + select DVB_TDA826X if !DVB_FE_CUSTOMISE + select DVB_STV0288 if !DVB_FE_CUSTOMISE + select DVB_IX2505V if !DVB_FE_CUSTOMISE + select IR_CORE + help + Say Y here to support the LME DM04/QQBOX DVB-S USB2.0 .
drivers/media/dvb/dvb-usb/Makefile +3 -0
@@ -88,6 +88,9 @@ obj-$(CONFIG_DVB_USB_EC168) += dvb-usb-ec168.o dvb-usb-az6027-objs = az6027.o obj-$(CONFIG_DVB_USB_AZ6027) += dvb-usb-az6027.o +dvb-usb-lmedm04-objs = lmedm04.o +obj-$(CONFIG_DVB_USB_LME2510) += dvb-usb-lmedm04.o + EXTRA_CFLAGS += -Idrivers/media/dvb/dvb-core/ -Idrivers/media/dvb/frontends/ # due to tuner-xc3028 EXTRA_CFLAGS += -Idrivers/media/common/tuners
drivers/media/dvb/dvb-usb/lmedm04.c new file +937 -0
937 lines not on this page · raw message
drivers/media/dvb/dvb-usb/lmedm04.h new file +187 -0
187 lines not on this page · raw message
include/media/rc-map.h +1 -0
@@ -93,6 +93,7 @@ void rc_map_init(void);#define RC_MAP_KWORLD_315U "rc-kworld-315u"#define RC_MAP_KWORLD_PLUS_TV_ANALOG "rc-kworld-plus-tv-analog"#define RC_MAP_LIRC "rc-lirc" +#define RC_MAP_LME2510 "rc-lme2510"#define RC_MAP_MANLI "rc-manli"#define RC_MAP_MSI_TVANYWHERE_PLUS "rc-msi-tvanywhere-plus"#define RC_MAP_MSI_TVANYWHERE "rc-msi-tvanywhere"
drivers/media/dvb/dvb-usb/Kconfig config DVB_USB_AZ6027 · line 359
Quoted 12 lines · tvbox
DM04/QQBOX DVB-S USB BOX with LME2510C+SHARP:BS2F7HZ7395 or LME2510+LGTDQT-P001F tuner.
drivers/media/dvb/dvb-usb/Kconfig +10
-0+config DVB_USB_LME2510 + tristate "LME DM04/QQBOX DVB-S USB2.0 support" + depends on DVB_USB + select DVB_TDA10086 if !DVB_FE_CUSTOMISE + select DVB_TDA826X if !DVB_FE_CUSTOMISE + select DVB_STV0288 if !DVB_FE_CUSTOMISE + select DVB_IX2505V if !DVB_FE_CUSTOMISE + select IR_CORE + help + Say Y here to support the LME DM04/QQBOX DVB-S USB2.0 .
Just for curious, is IR_CORE and DVB_USB both needed? DVB_USB also depends on IR_CORE ? This was only DVB-USB driver which does that.
Antti
Signature · 1 line
http://palosaari.fi/
Em 13-10-2010 16:10, Antti Palosaari escreveu:
Quoted 14 lines · tvbox
drivers/media/dvb/dvb-usb/Kconfig config DVB_USB_AZ6027 · line 359
Quoted 12 lines
DM04/QQBOX DVB-S USB BOX with LME2510C+SHARP:BS2F7HZ7395 or LME2510+LGTDQT-P001F tuner.
drivers/media/dvb/dvb-usb/Kconfig +10
-0+config DVB_USB_LME2510 + tristate "LME DM04/QQBOX DVB-S USB2.0 support" + depends on DVB_USB + select DVB_TDA10086 if !DVB_FE_CUSTOMISE + select DVB_TDA826X if !DVB_FE_CUSTOMISE + select DVB_STV0288 if !DVB_FE_CUSTOMISE + select DVB_IX2505V if !DVB_FE_CUSTOMISE + select IR_CORE + help + Say Y here to support the LME DM04/QQBOX DVB-S USB2.0 .
Quoted 1 line
Just for curious, is
IR_COREandDVB_USBboth needed?DVB_USBalso depends onIR_CORE? This was only DVB-USB driver which does that.
First of all, you shouldn't never use select with IR_CORE. This won't work for menu items. It should use only depends on.
With respect to DVB_USB, as we have:
config DVB_USB
tristate "Support for various USB DVB devices" depends on DVB_CORE && USB && I2C && IR_CORE
The IR_CORE dependency is already there, so, DVB_USB_LME2510 shouldn't need do use dependency related to IR.
Cheers,
Mauro
Quoted 15 lines · Mauro Carvalho Chehab
Em 13-10-2010 16:10, Antti Palosaari escreveu:
Quoted 14 lines · tvbox
Quoted 12 lines
DM04/QQBOX DVB-S USB BOX with LME2510C+SHARP:BS2F7HZ7395 or LME2510+LGTDQT-P001F tuner.
drivers/media/dvb/dvb-usb/Kconfig +10
-0+config DVB_USB_LME2510 + tristate "LME DM04/QQBOX DVB-S USB2.0 support" + depends on DVB_USB + select DVB_TDA10086 if !DVB_FE_CUSTOMISE + select DVB_TDA826X if !DVB_FE_CUSTOMISE + select DVB_STV0288 if !DVB_FE_CUSTOMISE + select DVB_IX2505V if !DVB_FE_CUSTOMISE + select IR_CORE + help + Say Y here to support the LME DM04/QQBOX DVB-S USB2.0 .
Quoted 4 lines
Quoted 1 line
Just for curious, is
IR_COREandDVB_USBboth needed?DVB_USBalso depends onIR_CORE? This was only DVB-USB driver which does that.The
IR_COREdependency is already there, so,DVB_USB_LME2510shouldn't need do use dependency related to IR.
I have an update patch pending final test for this driver. I will remove it in the patch.
Malcolm
Skystar USB 2 Driver
Hi,
I have just participated in this mail group. I wonder if there is a driver for Technisat Skystar USB 2 . Thank you.
Re: Skystar USB 2 Driver
Quoted 4 lines · On Friday 15 October 2010 10:10:44 Ali Güller wrote:
Hi,
I have just participated in this mail group. I wonder if there is a driver for Technisat Skystar USB 2 . Thank you.
Do you have a link with a picture of this device or a more precise description?
There is effectively a driver waiting to be merged for a SkyStar USB DVB-S2, but to find out if it yours, I need more information.
regards,
Signature · 1 line
Patrick
RE: Skystar USB 2 Driver
Hi,
Thank you for your reply
Here is my device
http://www.linuxtv.org/wiki/index.php/TechniSat_SkyStar_USB_2
TechniSat SkyStar USB 2
Quoted 1 line
From LinuxTVWiki
Jump to: navigation, search
Overview
Output of lsusb -v:
Bus 002 Device 004: ID 13d0:2282 TechniSat DVB-S Skystar USB 2 Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x13d0 TechniSat
idProduct 0x2282 DVB-S Skystar USB 2
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
cannot read device status, Broken pipe (32)
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Patrick Boettcher
Sent: Friday, October 15, 2010 11:15 AM
To: Ali Güller
Cc: 'tvbox'; 'Mauro Carvalho Chehab'; 'Antti Palosaari'; [email protected]
Subject: Re: Skystar USB 2 Driver
Quoted 4 lines · On Friday 15 October 2010 10:10:44 Ali Güller wrote:
Hi,
I have just participated in this mail group. I wonder if there is a driver for Technisat Skystar USB 2 . Thank you.
Do you have a link with a picture of this device or a more precise description?
There is effectively a driver waiting to be merged for a SkyStar USB DVB-S2, but to find out if it yours, I need more information.
regards,
Signature · 5 lines
Patrick -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Skystar USB 2 Driver
In reply to Ali GüllerHei Ali,
Quoted 1 line · Ali Güller
I have just participated in this mail group. I wonder if there is a driver for Technisat Skystar USB 2 . Thank you.
There is also commonly available Cinergy S2 USB HD (USB DVB-S2). I tested it recently and it was rather working with s2-liplianin tree. Support is not added to the main Kernel for some reason, looks like Liplianin is delaying it for some reason. He didn't even answer mail when I asked reason for delay :-(
http://mercurial.intuxication.org/hg/s2-liplianin-351/rev/97ae743b2035
Antti
Signature · 1 line
http://palosaari.fi/