[PATCH 1/1] [media] s5p-tv: Use module_i2c_driver in sii9234_drv.c file
module_i2c_driver makes the code simpler by eliminating module_init
and module_exit calls.
Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
---
drivers/media/video/s5p-tv/sii9234_drv.c | 12 +---
1 files changed, 1 insertions(+), 11 deletions(-)
diff --git a/drivers/media/video/s5p-tv/sii9234_drv.c
b/drivers/media/video/s5p-tv/sii9234_drv.c
index 0f31ecc..6d348f9 100644
--- a/drivers/media/video/s5p-tv/sii9234_drv.c
+++ b/drivers/media/video/s5p-tv/sii9234_drv.c
@@ -419,14 +419,4 @@ static struct i2c_driver sii9234_driver = {
.id_table = sii9234_id,
};
-static int __init sii9234_init(void)
-{
- return i2c_add_driver(sii9234_driver);
-}
-module_init(sii9234_init);
-
-static void __exit sii9234_exit(void)
-{
- i2c_del_driver(sii9234_driver);
-}
-module_exit(sii9234_exit);
+module_i2c_driver(sii9234_driver);
--
1.7.4.1
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH 1/1] media: rc: ati_remote.c: code style and compile warning fixing
Since this mail message had been unexpectedly wrapped by my mail client, I
will resend a new one.
changes:
1. break some lines that are longer than 80 characters.
2. remove local function prototype declarations which do not
need.
3. replace TAB character with a space character in function
comments.
4. change the types of array init1[] and init2[] to
unsigned char to avoid compile warning.
Signed-off-by: Du, Changbin changbin...@gmail.com
---
drivers/media/rc/ati_remote.c | 139
+
1 file changed, 84 insertions(+), 55 deletions(-)
diff --git a/drivers/media/rc/ati_remote.c b/drivers/media/rc/ati_remote.c
index 7be377f..0df66ac 100644
--- a/drivers/media/rc/ati_remote.c
+++ b/drivers/media/rc/ati_remote.c
@@ -23,6 +23,8 @@
*Vincent Vanackere vanack...@lif.univ-mrs.fr
*Added support for the Lola remote contributed by:
*Seth Cohn sethc...@yahoo.com
+ * Jul 2012: Du, Changbin changbin...@gmail.com
+ *Code style and compile warning fixing
*
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*
*
*
@@ -147,7 +149,8 @@ static bool mouse = true;
module_param(mouse, bool, 0444);
MODULE_PARM_DESC(mouse, Enable mouse device, default = yes);
-#define dbginfo(dev, format, arg...) do { if (debug) dev_info(dev ,
format
, ## arg); } while (0)
+#define dbginfo(dev, format, arg...) \
+ do { if (debug) dev_info(dev , format , ## arg); } while (0)
#undef err
#define err(format, arg...) printk(KERN_ERR format , ## arg)
@@ -191,17 +194,41 @@ static const char *get_medion_keymap(struct
usb_interface *interface)
return RC_MAP_MEDION_X10;
}
-static const struct ati_receiver_type type_ati = {
.default_keymap
= RC_MAP_ATI_X10 };
-static const struct ati_receiver_type type_medion= {
.get_default_keymap = get_medion_keymap };
-static const struct ati_receiver_type type_firefly = { .default_keymap
= RC_MAP_SNAPSTREAM_FIREFLY };
+static const struct ati_receiver_type type_ati = {
+ .default_keymap = RC_MAP_ATI_X10
+};
+static const struct ati_receiver_type type_medion= {
+ .get_default_keymap = get_medion_keymap
+};
+static const struct ati_receiver_type type_firefly = {
+ .default_keymap = RC_MAP_SNAPSTREAM_FIREFLY
+};
static struct usb_device_id ati_remote_table[] = {
- { USB_DEVICE(ATI_REMOTE_VENDOR_ID, LOLA_REMOTE_PRODUCT_ID),
.driver_info = (unsigned long)type_ati },
- { USB_DEVICE(ATI_REMOTE_VENDOR_ID,
LOLA2_REMOTE_PRODUCT_ID),
.driver_info = (unsigned long)type_ati },
- { USB_DEVICE(ATI_REMOTE_VENDOR_ID, ATI_REMOTE_PRODUCT_ID),
.driver_info = (unsigned long)type_ati },
- { USB_DEVICE(ATI_REMOTE_VENDOR_ID,
NVIDIA_REMOTE_PRODUCT_ID),
.driver_info = (unsigned long)type_ati },
- { USB_DEVICE(ATI_REMOTE_VENDOR_ID,
MEDION_REMOTE_PRODUCT_ID),
.driver_info = (unsigned long)type_medion },
- { USB_DEVICE(ATI_REMOTE_VENDOR_ID,
FIREFLY_REMOTE_PRODUCT_ID),
.driver_info = (unsigned long)type_firefly },
+ {
+ USB_DEVICE(ATI_REMOTE_VENDOR_ID,
LOLA_REMOTE_PRODUCT_ID),
+ .driver_info = (unsigned long)type_ati
+ },
+ {
+ USB_DEVICE(ATI_REMOTE_VENDOR_ID,
LOLA2_REMOTE_PRODUCT_ID),
+ .driver_info = (unsigned long)type_ati
+ },
+ {
+ USB_DEVICE(ATI_REMOTE_VENDOR_ID,
ATI_REMOTE_PRODUCT_ID),
+ .driver_info = (unsigned long)type_ati
+ },
+ {
+ USB_DEVICE(ATI_REMOTE_VENDOR_ID,
NVIDIA_REMOTE_PRODUCT_ID),
+ .driver_info = (unsigned long)type_ati
+ },
+ {
+ USB_DEVICE(ATI_REMOTE_VENDOR_ID,
MEDION_REMOTE_PRODUCT_ID),
+ .driver_info = (unsigned long)type_medion
+ },
+ {
+ USB_DEVICE(ATI_REMOTE_VENDOR_ID,
FIREFLY_REMOTE_PRODUCT_ID),
+ .driver_info = (unsigned long)type_firefly
+ },
{} /* Terminating entry */
};
@@ -215,8 +242,8 @@ MODULE_DEVICE_TABLE(usb, ati_remote_table);
#define SEND_FLAG_COMPLETE 2
/* Device initialization strings */
-static char init1[] = { 0x01, 0x00, 0x20, 0x14 };
-static char init2[] = { 0x01, 0x00, 0x20, 0x14, 0x20, 0x20, 0x20 };
+static unsigned char init1[] = { 0x01, 0x00, 0x20, 0x14 };
+static unsigned char init2[] = { 0x01, 0x00, 0x20, 0x14, 0x20, 0x20, 0x20
};
struct ati_remote {
struct input_dev *idev;
@@ -296,25 +323,8 @@ static const struct {
{KIND_END, 0x00, EV_MAX + 1, 0, 0}
};
-/* Local function prototypes */
-static int ati_remote_sendpacket (struct ati_remote *ati_remote, u16
cmd, unsigned char *data);
-static void ati_remote_irq_out (struct urb *urb);
-static void ati_remote_irq_in(struct urb *urb);
-static void ati_remote_input_report (struct urb *urb);
Re: pctv452e
On 04.07.2012 01:04, Antti Palosaari wrote: Your claims about my DVB-USB-framework work is quite bullshit. I am not going to convert all drivers to the new framework just doing compile tests. I'm not bashing you, I see you are doing very good job, and not only you but many people here. I don't like mess and refactoring is good thing. The problem is that often makers of hardware doesn't support their linux drivers and changes in DVB core doesn't help it. Like with pctv452e - device was working, i've bought it as supported and now it works only partially. I don't think there is easy solution to that problem. Card maker should support drivers but in reality we should be happy if he do any working driver for linux. And thank you for modified driver, I will try it at home and of course will write how it is working. Marx -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Resend PATCH] media: rc: ati_remote.c: code style and compile warning fixing
changes:
1. break some lines that are longer than 80 characters.
2. remove local function prototype declarations which do not
need.
3. replace TAB character with a space character in function
comments.
4. change the types of array init1[] and init2[] to
unsigned char to avoid compile warning.
Signed-off-by: Du, Changbin changbin...@gmail.com
---
drivers/media/rc/ati_remote.c | 139
+
1 file changed, 84 insertions(+), 55 deletions(-)
diff --git a/drivers/media/rc/ati_remote.c b/drivers/media/rc/ati_remote.c
index 7be377f..0df66ac 100644
--- a/drivers/media/rc/ati_remote.c
+++ b/drivers/media/rc/ati_remote.c
@@ -23,6 +23,8 @@
*Vincent Vanackere vanack...@lif.univ-mrs.fr
*Added support for the Lola remote contributed by:
*Seth Cohn sethc...@yahoo.com
+ * Jul 2012: Du, Changbin changbin...@gmail.com
+ *Code style and compile warning fixing
*
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*
*
@@ -147,7 +149,8 @@ static bool mouse = true;
module_param(mouse, bool, 0444);
MODULE_PARM_DESC(mouse, Enable mouse device, default = yes);
-#define dbginfo(dev, format, arg...) do { if (debug) dev_info(dev , format
, ## arg); } while (0)
+#define dbginfo(dev, format, arg...) \
+ do { if (debug) dev_info(dev , format , ## arg); } while (0)
#undef err
#define err(format, arg...) printk(KERN_ERR format , ## arg)
@@ -191,17 +194,41 @@ static const char *get_medion_keymap(struct
usb_interface *interface)
return RC_MAP_MEDION_X10;
}
-static const struct ati_receiver_type type_ati = { .default_keymap
= RC_MAP_ATI_X10 };
-static const struct ati_receiver_type type_medion = {
.get_default_keymap = get_medion_keymap };
-static const struct ati_receiver_type type_firefly = { .default_keymap
= RC_MAP_SNAPSTREAM_FIREFLY };
+static const struct ati_receiver_type type_ati = {
+ .default_keymap = RC_MAP_ATI_X10
+};
+static const struct ati_receiver_type type_medion = {
+ .get_default_keymap = get_medion_keymap
+};
+static const struct ati_receiver_type type_firefly = {
+ .default_keymap = RC_MAP_SNAPSTREAM_FIREFLY
+};
static struct usb_device_id ati_remote_table[] = {
- { USB_DEVICE(ATI_REMOTE_VENDOR_ID, LOLA_REMOTE_PRODUCT_ID),
.driver_info = (unsigned long)type_ati },
- { USB_DEVICE(ATI_REMOTE_VENDOR_ID, LOLA2_REMOTE_PRODUCT_ID),
.driver_info = (unsigned long)type_ati },
- { USB_DEVICE(ATI_REMOTE_VENDOR_ID, ATI_REMOTE_PRODUCT_ID),
.driver_info = (unsigned long)type_ati },
- { USB_DEVICE(ATI_REMOTE_VENDOR_ID, NVIDIA_REMOTE_PRODUCT_ID),
.driver_info = (unsigned long)type_ati },
- { USB_DEVICE(ATI_REMOTE_VENDOR_ID, MEDION_REMOTE_PRODUCT_ID),
.driver_info = (unsigned long)type_medion },
- { USB_DEVICE(ATI_REMOTE_VENDOR_ID, FIREFLY_REMOTE_PRODUCT_ID),
.driver_info = (unsigned long)type_firefly },
+ {
+ USB_DEVICE(ATI_REMOTE_VENDOR_ID, LOLA_REMOTE_PRODUCT_ID),
+ .driver_info = (unsigned long)type_ati
+ },
+ {
+ USB_DEVICE(ATI_REMOTE_VENDOR_ID, LOLA2_REMOTE_PRODUCT_ID),
+ .driver_info = (unsigned long)type_ati
+ },
+ {
+ USB_DEVICE(ATI_REMOTE_VENDOR_ID, ATI_REMOTE_PRODUCT_ID),
+ .driver_info = (unsigned long)type_ati
+ },
+ {
+ USB_DEVICE(ATI_REMOTE_VENDOR_ID, NVIDIA_REMOTE_PRODUCT_ID),
+ .driver_info = (unsigned long)type_ati
+ },
+ {
+ USB_DEVICE(ATI_REMOTE_VENDOR_ID, MEDION_REMOTE_PRODUCT_ID),
+ .driver_info = (unsigned long)type_medion
+ },
+ {
+ USB_DEVICE(ATI_REMOTE_VENDOR_ID, FIREFLY_REMOTE_PRODUCT_ID),
+ .driver_info = (unsigned long)type_firefly
+ },
{} /* Terminating entry */
};
@@ -215,8 +242,8 @@ MODULE_DEVICE_TABLE(usb, ati_remote_table);
#define SEND_FLAG_COMPLETE 2
/* Device initialization strings */
-static char init1[] = { 0x01, 0x00, 0x20, 0x14 };
-static char init2[] = { 0x01, 0x00, 0x20, 0x14, 0x20, 0x20, 0x20 };
+static unsigned char init1[] = { 0x01, 0x00, 0x20, 0x14 };
+static unsigned char init2[] = { 0x01, 0x00, 0x20, 0x14, 0x20, 0x20, 0x20
};
struct ati_remote {
struct input_dev *idev;
@@ -296,25 +323,8 @@ static const struct {
{KIND_END, 0x00, EV_MAX + 1, 0, 0}
};
-/* Local function prototypes */
-static int ati_remote_sendpacket (struct ati_remote *ati_remote, u16
cmd, unsigned char *data);
-static void ati_remote_irq_out (struct urb *urb);
-static void ati_remote_irq_in (struct urb *urb);
-static void ati_remote_input_report(struct urb *urb);
-static int ati_remote_initialize (struct ati_remote *ati_remote);
-static int ati_remote_probe(struct usb_interface *interface,
Re: [RFC PATCH 1/6] videodev2.h: add VIDIOC_ENUM_FREQ_BANDS.
Hi, On 07/04/2012 10:35 AM, Hans Verkuil wrote: snip snip Can we have a (hopefully short) irc discussion today? I'd really like to get this API finalized. +1, I'm available the entire day (CET office hours + evening if needed that is) snip snip So my current proposal is: use a bitfield in v4l2_frequency_band to describe possible (de)modulators and add compat code to the v4l2-ioctl.c to automatically create a vidioc_enum_freq_bands op if no such op was supplied, using the data from g_tuner or g_modulator and which device node was used to fill in the fields. +1 Regards, The other Hans :) -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Easycap
Hi Robert, I've added linux-media on Cc since someone might find your question on interest. On Wed, Jul 4, 2012 at 3:16 AM, Robert Walter rolin...@gmail.com wrote: I wonder if you could point me in the right direction? I bought an easy-cap video capture device but it doesn't look like anything I've seen before. The USB ID is 1b71:3002 and lsusb -v tells me the USB bridge is made by Fuchsia and the device name is usbtv007. I would like to know if this device is supported in Linux and if not, what is the preferred way to get a device supported. There is currently no driver supporting 0x1b71 vendor id. It seems Chinese manufacturers like to make usb capture devices and use the name Easycap for every one of them :-) However, since usb bridge chip is different, a completely new driver should be written; and unless you can get a datasheet the only way I know to (blindly) write such driver is with a lot of reverse engineering. Good luck, Ezequiel. -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH v1] s5p-mfc: update MFC v4l2 driver to support MFC6.x
This patch is re-worked version of the original patch posted by Jeongtae Park for support of MFCv6.x The comment given by Kamil Debski can be found here: http://comments.gmane.org/gmane.linux.drivers.video-input-infrastructure/45189 The crash issue reported on MFC 5.1 on applying this patch has been fixed. This is tested for decoding functionality on MFC 5.1 and MFC 6.5. Encoder functionality is not tested on Exynos5 yet. Jeongtae Park (1): [media] s5p-mfc: update MFC v4l2 driver to support MFC6.x drivers/media/video/Kconfig | 16 +- drivers/media/video/s5p-mfc/Makefile |7 +- drivers/media/video/s5p-mfc/regs-mfc-v6.h| 676 ++ drivers/media/video/s5p-mfc/regs-mfc.h | 29 + drivers/media/video/s5p-mfc/s5p_mfc.c| 163 ++- drivers/media/video/s5p-mfc/s5p_mfc_cmd.c|6 +- drivers/media/video/s5p-mfc/s5p_mfc_cmd.h|3 + drivers/media/video/s5p-mfc/s5p_mfc_cmd_v6.c | 96 ++ drivers/media/video/s5p-mfc/s5p_mfc_common.h | 123 ++- drivers/media/video/s5p-mfc/s5p_mfc_ctrl.c | 160 ++- drivers/media/video/s5p-mfc/s5p_mfc_ctrl.h |1 + drivers/media/video/s5p-mfc/s5p_mfc_dec.c| 210 +++- drivers/media/video/s5p-mfc/s5p_mfc_dec.h|1 + drivers/media/video/s5p-mfc/s5p_mfc_enc.c| 377 +-- drivers/media/video/s5p-mfc/s5p_mfc_enc.h|1 + drivers/media/video/s5p-mfc/s5p_mfc_intr.c |1 - drivers/media/video/s5p-mfc/s5p_mfc_opr.c| 282 +++-- drivers/media/video/s5p-mfc/s5p_mfc_opr.h| 25 +- drivers/media/video/s5p-mfc/s5p_mfc_opr_v6.c | 1697 ++ drivers/media/video/s5p-mfc/s5p_mfc_opr_v6.h | 140 +++ drivers/media/video/s5p-mfc/s5p_mfc_pm.c |6 +- drivers/media/video/s5p-mfc/s5p_mfc_shm.c| 28 +- drivers/media/video/s5p-mfc/s5p_mfc_shm.h| 13 +- 23 files changed, 3661 insertions(+), 400 deletions(-) create mode 100644 drivers/media/video/s5p-mfc/regs-mfc-v6.h create mode 100644 drivers/media/video/s5p-mfc/s5p_mfc_cmd_v6.c create mode 100644 drivers/media/video/s5p-mfc/s5p_mfc_opr_v6.c create mode 100644 drivers/media/video/s5p-mfc/s5p_mfc_opr_v6.h -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
ATI theatre 750 HD tuner USB stick
Hi all, My name is Fisher Grubb, I have an ATI (now AMD) theatre 750 HD based TV tuner USB stick. I don't think this ATI chipset is supported by linuxTV and have had no joy search google as others also hit a dead end. I have put USB bus dump for that device and the chip part numbers at the bottom. Please may I have a quick reply if someone looks at this, thanks. Model number is U5071, manufacturer site: http://www.geniatech.com/pa/u5071.asp I think this is a very impressive piece of hardware as it can do: Analogue TV, DVB, AV capture and S video capture. There is an IR receiver on board and came with IR remote control. I'm happy to provide any info on it that you may want such as picture of board chips. I'm almost finished my electronics degree and so can do hardware probing if someone may give me something specific to look for. I'm also happy to run software or commands to dump stuff or even help with dumping things from the windows drivers if I've given directions etc. Thank you, Fisher lsusb: Bus 002 Device 021: ID 0438:ac14 Advanced Micro Devices, Inc. sudo lsusb -vd 0438:ac14 Bus 002 Device 021: ID 0438:ac14 Advanced Micro Devices, Inc. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x0438 Advanced Micro Devices, Inc. idProduct 0xac14 bcdDevice1.00 iManufacturer 1 AMD iProduct2 Cali TV Card iSerial 3 1234-5678 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 97 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 5 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 3 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x85 EP 5 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 1 bNumEndpoints 5 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes1 Transfer TypeIsochronous Synch Type None Usage Type Data wMaxPacketSize 0x1400 3x 1024 bytes bInterval 1
Re: ATI theatre 750 HD tuner USB stick
Hi all, I was in contact with AMD today regarding this tuner haveing no support on Linux and I was given a link for a feedback form and told to get specific needs from www.linuxtv.org to help the cause and if there were enough people, then the AMD developers may help. Of course I wouldn't be surprised if people will have to reverse engineer it from the windows drivers but I thought I would mention it. I could not find any info on this 750 HD on www.linuxtv.org regarding where it stands. What help is needed for it? Fisher On Wed, Jul 4, 2012 at 11:21 PM, Fisher Grubb fisher.gr...@gmail.com wrote: Hi all, My name is Fisher Grubb, I have an ATI (now AMD) theatre 750 HD based TV tuner USB stick. I don't think this ATI chipset is supported by linuxTV and have had no joy search google as others also hit a dead end. I have put USB bus dump for that device and the chip part numbers at the bottom. Please may I have a quick reply if someone looks at this, thanks. Model number is U5071, manufacturer site: http://www.geniatech.com/pa/u5071.asp I think this is a very impressive piece of hardware as it can do: Analogue TV, DVB, AV capture and S video capture. There is an IR receiver on board and came with IR remote control. I'm happy to provide any info on it that you may want such as picture of board chips. I'm almost finished my electronics degree and so can do hardware probing if someone may give me something specific to look for. I'm also happy to run software or commands to dump stuff or even help with dumping things from the windows drivers if I've given directions etc. Thank you, Fisher lsusb: Bus 002 Device 021: ID 0438:ac14 Advanced Micro Devices, Inc. sudo lsusb -vd 0438:ac14 Bus 002 Device 021: ID 0438:ac14 Advanced Micro Devices, Inc. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x0438 Advanced Micro Devices, Inc. idProduct 0xac14 bcdDevice1.00 iManufacturer 1 AMD iProduct2 Cali TV Card iSerial 3 1234-5678 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 97 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 5 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 3 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x85 EP 5 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9
Re: ATI theatre 750 HD tuner USB stick
On Wed, Jul 4, 2012 at 9:27 AM, Fisher Grubb fisher.gr...@gmail.com wrote: I was in contact with AMD today regarding this tuner haveing no support on Linux and I was given a link for a feedback form and told to get specific needs from www.linuxtv.org to help the cause and if there were enough people, then the AMD developers may help. I'm not sure why they would direct you to linuxtv.org. *They* are the ones with all the information that the linuxtv community would need. Of course I wouldn't be surprised if people will have to reverse engineer it from the windows drivers but I thought I would mention it. I could not find any info on this 750 HD on www.linuxtv.org regarding where it stands. What help is needed for it? 1. Datasheets for the 750 (under NDA is fine), but they need to agree to allow them to be used to author a GPL driver. 2. Reference driver sources which can be legally incorporated into a GPL driver. 3. Firmware with a license that permits free redistribution. I attempted to work with them back in 2009 on the T316 chip (an ATSC/ClearQAM demodulator), and they couldn't provide all of the above. Perhaps things have changed since then but I doubt it (in particular, the sale of their TV chip unit to Broadcom left all sorts of unknowns regarding who owns the relevant intellectual property). Finally, even if you get the above, there still needs to be some developer who has the time/interest to do the work. While three years ago the big challenge was getting access to the datasheets, nowadays a much bigger problem is there are no developers who are both qualified and not already too busy with other work. Bootstrapping a new chip like that is probably a 50-100 hour investment for somebody who is experienced in this area, which is a fairly big chunk of time if the developer doesn't have any vested interest. Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: ATI theatre 750 HD tuner USB stick
On Wed, Jul 4, 2012 at 9:27 AM, Fisher Grubb fisher.gr...@gmail.com wrote: Hi all, I was in contact with AMD today regarding this tuner haveing no support on Linux and I was given a link for a feedback form and told to get specific needs from www.linuxtv.org to help the cause and if there were enough people, then the AMD developers may help. Of course I wouldn't be surprised if people will have to reverse engineer it from the windows drivers but I thought I would mention it. I could not find any info on this 750 HD on www.linuxtv.org regarding where it stands. What help is needed for it? Unfortunately, I don't think there is much AMD can do. We sold our multimedia DTV division to Broadcom several years ago. IANAL, so I don't know exactly what rights we retained for the IP. You may need to talk to Broadcom now. Alex Fisher On Wed, Jul 4, 2012 at 11:21 PM, Fisher Grubb fisher.gr...@gmail.com wrote: Hi all, My name is Fisher Grubb, I have an ATI (now AMD) theatre 750 HD based TV tuner USB stick. I don't think this ATI chipset is supported by linuxTV and have had no joy search google as others also hit a dead end. I have put USB bus dump for that device and the chip part numbers at the bottom. Please may I have a quick reply if someone looks at this, thanks. Model number is U5071, manufacturer site: http://www.geniatech.com/pa/u5071.asp I think this is a very impressive piece of hardware as it can do: Analogue TV, DVB, AV capture and S video capture. There is an IR receiver on board and came with IR remote control. I'm happy to provide any info on it that you may want such as picture of board chips. I'm almost finished my electronics degree and so can do hardware probing if someone may give me something specific to look for. I'm also happy to run software or commands to dump stuff or even help with dumping things from the windows drivers if I've given directions etc. Thank you, Fisher lsusb: Bus 002 Device 021: ID 0438:ac14 Advanced Micro Devices, Inc. sudo lsusb -vd 0438:ac14 Bus 002 Device 021: ID 0438:ac14 Advanced Micro Devices, Inc. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x0438 Advanced Micro Devices, Inc. idProduct 0xac14 bcdDevice1.00 iManufacturer 1 AMD iProduct2 Cali TV Card iSerial 3 1234-5678 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 97 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 5 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 3 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5
Re: ATI theatre 750 HD tuner USB stick
On 07/04/2012 04:27 PM, Fisher Grubb wrote: Of course I wouldn't be surprised if people will have to reverse engineer it from the windows drivers but I thought I would mention it. I could not find any info on this 750 HD on www.linuxtv.org regarding where it stands. What help is needed for it? Chips: ATI: T507 0930 MADE IN TAIWAN P0U493.00 215-0692014 T507 driver is the missing piece. I suspect that SoC integrates many chips, USB-bridge (with IR etc.), DVB-T demodulator and analog decoder. Getting it work as DVB-T device is not mission impossible even without a specs. Reverse-engineering is fun ;-) Generally speaking DVB-bridge is very simple, no problems at all to reverse. DVB demodulator is little bit harder but still possible without loosing even sensitivity. What you lose is configuration options like how IF frequency, SNR, BER is calculated. Tuners are most tricky as there is all kind of calibration routines etc. but in that case tuner driver exists. NXP: TDA18271HDC2 P3KN4 02 PG09361 That TDA18271 driver already exists - even two different drivers. regards Antti -- http://palosaari.fi/ -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 4/4] radio-si470x: Lower firmware version requirements
On 06/14/2012 04:43 PM, Hans de Goede wrote:
With the changes from the previous patches device firmware version 14 +
usb microcontroller software version 1 works fine too.
Signed-off-by: Hans de Goede hdego...@redhat.com
---
drivers/media/radio/si470x/radio-si470x-usb.c |2 +-
drivers/media/radio/si470x/radio-si470x.h |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/media/radio/si470x/radio-si470x-usb.c
b/drivers/media/radio/si470x/radio-si470x-usb.c
index 66b1ba8..40b963c 100644
--- a/drivers/media/radio/si470x/radio-si470x-usb.c
+++ b/drivers/media/radio/si470x/radio-si470x-usb.c
@@ -143,7 +143,7 @@ MODULE_PARM_DESC(max_rds_errors, RDS maximum block errors:
*1*);
* Software/Hardware Versions from Scratch Page
**/
#define RADIO_SW_VERSION_NOT_BOOTLOADABLE 6
-#define RADIO_SW_VERSION 7
+#define RADIO_SW_VERSION 1
#define RADIO_HW_VERSION 1
diff --git a/drivers/media/radio/si470x/radio-si470x.h
b/drivers/media/radio/si470x/radio-si470x.h
index fbf713d..b3b612f 100644
--- a/drivers/media/radio/si470x/radio-si470x.h
+++ b/drivers/media/radio/si470x/radio-si470x.h
@@ -189,7 +189,7 @@ struct si470x_device {
* Firmware Versions
**/
-#define RADIO_FW_VERSION 15
+#define RADIO_FW_VERSION 14
I just found out this patch serie and tested it - but no luck. Could you
say if I do something wrong or is it due to my device firmware version?
I compiled radio from http://git.linuxtv.org/xawtv3.git to tune and
arecord -r96000 -c2 -f S16_LE | aplay - to play sound. Just silent
white noise is heard.
Jul 4 18:04:33 localhost kernel: [ 78.006361] usb 5-2: new full-speed
USB device number 2 using ohci_hcd
Jul 4 18:04:34 localhost kernel: [ 78.165127] usb 5-2: New USB device
found, idVendor=10c5, idProduct=819a
Jul 4 18:04:34 localhost kernel: [ 78.165131] usb 5-2: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Jul 4 18:04:34 localhost kernel: [ 78.165133] usb 5-2: Manufacturer:
www.rding.cn
Jul 4 18:04:34 localhost udevd[412]: specified group 'plugdev' unknown
Jul 4 18:04:34 localhost mtp-probe: checking bus 5, device 2:
/sys/devices/pci:00/:00:13.0/usb5/5-2
Jul 4 18:04:34 localhost mtp-probe: bus: 5, device: 2 was not an MTP device
Jul 4 18:04:34 localhost kernel: [ 78.189884] Linux media interface:
v0.10
Jul 4 18:04:34 localhost kernel: [ 78.191940] Linux video capture
interface: v2.00
Jul 4 18:04:34 localhost kernel: [ 78.194058] radio-si470x 5-2:1.2:
DeviceID=0x1242 ChipID=0x060c
Jul 4 18:04:34 localhost kernel: [ 78.194061] radio-si470x 5-2:1.2:
This driver is known to work with firmware version 14,
Jul 4 18:04:34 localhost kernel: [ 78.194062] radio-si470x 5-2:1.2:
but the device has firmware version 12.
Jul 4 18:04:34 localhost kernel: [ 78.196041] radio-si470x 5-2:1.2:
software version 1, hardware version 7
Jul 4 18:04:34 localhost kernel: [ 78.196043] radio-si470x 5-2:1.2:
If you have some trouble using this driver,
Jul 4 18:04:34 localhost kernel: [ 78.196045] radio-si470x 5-2:1.2:
please report to V4L ML at linux-media@vger.kernel.org
Jul 4 18:04:34 localhost kernel: [ 78.339041] usbcore: registered new
interface driver radio-si470x
Jul 4 18:04:34 localhost kernel: [ 78.357056] usbcore: registered new
interface driver snd-usb-audio
And is there any cheap USB FM-radio device that is known to work on
Linux ? I would like to order one...
regards
Antti
--
http://palosaari.fi/
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
re: pctv452e
Ps. Steve, could you please give me full version of kernel which works with pctv452e? I think it was 2.6.37-1-kirkwood from Debian which I was using (this is an ARM system). As the new DVB-USB fixes many bugs I ask you to test it. I converted pctv452e driver for you: http://git.linuxtv.org/anttip/media_tree.git/shortlog/refs/heads/pctv452e Only PCTV device supported currently, not TechnoTrend at that time. Can I ask why it only works on the PCTV devices? I was under the impression that the TechnoTrend hardware was identical? If you are able to provide any pointers as to where the TechnoTrend support is broken (or what debugging I should be turning on to figure out where it is broken) then that would be helpful. Thanks. -- - Steve -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: pctv452e
On 07/04/2012 07:04 PM, Steve Hill wrote: Ps. Steve, could you please give me full version of kernel which works with pctv452e? I think it was 2.6.37-1-kirkwood from Debian which I was using (this is an ARM system). As the new DVB-USB fixes many bugs I ask you to test it. I converted pctv452e driver for you: http://git.linuxtv.org/anttip/media_tree.git/shortlog/refs/heads/pctv452e Only PCTV device supported currently, not TechnoTrend at that time. Can I ask why it only works on the PCTV devices? I was under the impression that the TechnoTrend hardware was identical? If you are able to provide any pointers as to where the TechnoTrend support is broken (or what debugging I should be turning on to figure out where it is broken) then that would be helpful. I don't have hardware, no PCTV neither TechnoTrend. I just converted PCTV as Marx seems to have such device and he was blaming. Code wasn't 100% similar, for example TechnoTrend has CI PCTV doesn't. It should not fix problems but it could since I fixed some nasty bugs. Lets wait test report first and make decision what to do after that. regards Antti -- http://palosaari.fi/ -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[GIT PULL FOR v3.6] mostly remove V4L2_FL_LOCK_ALL_FOPS
Hi Mauro, This pull request builds on (and includes) this core patch series: http://patchwork.linuxtv.org/patch/13180/ It is identical to the RFC patch series I posted before: http://www.mail-archive.com/linux-media@vger.kernel.org/msg48184.html ...except that I dropped the patches touching s5p-fimc and fimc-lite and the final patch removing the flag altogether. Sylwester posted patches for those two drivers, but they won't apply. Sylwester, can you rebase those patches? Once I have those, then I can make another pull request that fixes those two drivers and removes the flag completely. Regards, Hans The following changes since commit 704a28e88ab6c9cfe393ae626b612cab8b46028e: [media] drxk: prevent doing something wrong when init is not ok (2012-06-29 19:04:32 -0300) are available in the git repository at: git://linuxtv.org/hverkuil/media_tree.git removeflag3 for you to fetch changes up to 3456068130243f2391ad3c763a28a7137efcf0a2: s5p-mfc: remove V4L2_FL_LOCK_ALL_FOPS (2012-07-04 19:35:22 +0200) Hans Verkuil (57): v4l2-ioctl.c: move a block of code down, no other changes. v4l2-ioctl.c: introduce INFO_FL_CLEAR to replace switch. v4l2-ioctl.c: v4l2-ioctl: add debug and callback/offset functionality. v4l2-ioctl.c: remove an unnecessary #ifdef. v4l2-ioctl.c: use the new table for querycap and i/o ioctls. v4l2-ioctl.c: use the new table for priority ioctls. v4l2-ioctl.c: use the new table for format/framebuffer ioctls. v4l2-ioctl.c: use the new table for overlay/streamon/off ioctls. v4l2-ioctl.c: use the new table for std/tuner/modulator ioctls. v4l2-ioctl.c: use the new table for queuing/parm ioctls. v4l2-ioctl.c: use the new table for control ioctls. v4l2-ioctl.c: use the new table for selection ioctls. v4l2-ioctl.c: use the new table for compression ioctls. v4l2-ioctl.c: use the new table for debug ioctls. v4l2-ioctl.c: use the new table for preset/timings ioctls. v4l2-ioctl.c: use the new table for the remaining ioctls. v4l2-ioctl.c: finalize table conversion. v4l2-dev.c: add debug sysfs entry. v4l2-ioctl: remove v4l_(i2c_)print_ioctl ivtv: don't mess with vfd-debug. cx18: don't mess with vfd-debug. vb2-core: refactor reqbufs/create_bufs. vb2-core: add support for count == 0 in create_bufs. Spec: document CREATE_BUFS behavior if count == 0. v4l2-dev/ioctl.c: add vb2_queue support to video_device. videobuf2-core: add helper functions. vivi: remove pointless g/s_std support vivi: embed struct video_device instead of allocating it. vivi: use vb2 helper functions. vivi: add create_bufs/preparebuf support. v4l2-dev.c: also add debug support for the fops. pwc: use the new vb2 helpers. pwc: v4l2-compliance fixes. v4l2-framework.txt: Update the locking documentation. ivtv: remove V4L2_FL_LOCK_ALL_FOPS saa7146: remove V4L2_FL_LOCK_ALL_FOPS cpia2: remove V4L2_FL_LOCK_ALL_FOPS usbvision: remove V4L2_FL_LOCK_ALL_FOPS em28xx: remove V4L2_FL_LOCK_ALL_FOPS tm6000: remove V4L2_FL_LOCK_ALL_FOPS mem2mem_testdev: remove V4L2_FL_LOCK_ALL_FOPS dt3155v4l: remove V4L2_FL_LOCK_ALL_FOPS wl128x: remove V4L2_FL_LOCK_ALL_FOPS fsl-viu: remove V4L2_FL_LOCK_ALL_FOPS s2255drv: remove V4L2_FL_LOCK_ALL_FOPS vpbe_display: remove V4L2_FL_LOCK_ALL_FOPS vpif_capture: remove V4L2_FL_LOCK_ALL_FOPS vpif_display: remove V4L2_FL_LOCK_ALL_FOPS mx2_emmaprp: remove V4L2_FL_LOCK_ALL_FOPS sh_vou: remove V4L2_FL_LOCK_ALL_FOPS bfin_capture: remove V4L2_FL_LOCK_ALL_FOPS cx231xx: remove V4L2_FL_LOCK_ALL_FOPS soc_camera: remove V4L2_FL_LOCK_ALL_FOPS s5p-jpeg: remove V4L2_FL_LOCK_ALL_FOPS s5p-g2d: remove V4L2_FL_LOCK_ALL_FOPS s5p-tv: remove V4L2_FL_LOCK_ALL_FOPS s5p-mfc: remove V4L2_FL_LOCK_ALL_FOPS Documentation/DocBook/media/v4l/vidioc-create-bufs.xml |8 +- Documentation/video4linux/v4l2-framework.txt | 73 +- drivers/media/common/saa7146_core.c|8 - drivers/media/common/saa7146_fops.c| 55 +- drivers/media/radio/wl128x/fmdrv_v4l2.c| 38 +- drivers/media/video/blackfin/bfin_capture.c| 17 +- drivers/media/video/cpia2/cpia2_v4l.c | 39 +- drivers/media/video/cx18/cx18-ioctl.c | 18 - drivers/media/video/cx18/cx18-ioctl.h |2 - drivers/media/video/cx18/cx18-streams.c|4 +- drivers/media/video/cx231xx/cx231xx-video.c| 47 +- drivers/media/video/davinci/vpbe_display.c | 22 +- drivers/media/video/davinci/vpif_capture.c | 28 +- drivers/media/video/davinci/vpif_display.c | 34 +-
Re: Info on Remote controller keys like upper-right, upper-left , lower-right, lower-left ,sub-picture etc.
On 07/04/2012 09:34 PM, Dharam Kumar wrote:
Hi All,
I've been working on a MHL( www.mhltech.org ) transmitter driver
which needs to receive/handle incoming Remote control keys.
The specification tells me that other than normal keys[up,down,left,
right etc.] there are certain remote control keys like Upper-right,
Upper-left, Lower-right, Lower-left, Sub-picture etc.
While creating a key map in the driver, I tried to find whether these
keys has been defined in linux/input.h ,but I could not find such
key definitions
in the header file.
Please note that, although the Specs do define these Remote Controller
keys, the driver will have the choice
to support the key depending on the key-map.
Something like this:
/* Key Map for the driver */
{ KEY_UP, supported },
{ KEY_DOWN, supported},
{KEY_UPPERRIGHT, supported}, /* No definition for
KEY_UPPERRIGHT in input.h */
{KEY_UPPERLEFT, not-supported}, /* No definition for KEY_UPPERLEFT
in input.h, although this key is not supported by driver */
In other mailing lists[linux-input], it has been suggested that these
keys are similar to Joystick keys.
I've looked into drivers/input/joystick/analog.c file, but could not
find any buttons/pads which are similar to the above one[Am I missing
something here??]
any pointers??
Here is list of key bindings used for media device remote controllers
(television, radio, etc):
http://linuxtv.org/wiki/index.php/Remote_Controllers
But still no definitions like up-left etc.
regards
Antti
--
http://palosaari.fi/
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
AF9035 Twinstar has firmware errors
hello, I've downloaded and compiled against karnel 3.0.0 and kernel 3.4.3 the latest git tree from antii, branch dvb-usb-pull, and it doesn't recognize my dual tuner Avermedia Twinstar (af9035 + mxl5007t) anymore. Here's the logs from dmesg (the compiled modules do not have any debug parameters to enable): [44919.461121] WARNING: You are using an experimental version of the media stack. [44919.461125] As the driver is backported to an older kernel, it doesn't offer [44919.461129] enough quality for its usage in production. [44919.461131] Use it with care. [44919.461133] Latest git patches (needed if you report a bug to linux-media@vger.kernel.org): [44919.461136] 635b1d05b4a2c62ebb76a1514e806faa133abc1f dvb_usb_v2: remove usb_clear_halt() from stream [44919.461139] fc86b47f681e0c052cc6e71a4fd55f405fbe6d51 dvb_usb_v2: do not try to remove non-existent adapter [44919.461143] 6b86e957b62381c65f1edc068a4b2483ff9536df dvb_usb_v2: use dev_* logging macros [44919.465073] WARNING: You are using an experimental version of the media stack. [44919.465077] As the driver is backported to an older kernel, it doesn't offer [44919.465080] enough quality for its usage in production. [44919.465082] Use it with care. [44919.465084] Latest git patches (needed if you report a bug to linux-media@vger.kernel.org): [44919.465087] 635b1d05b4a2c62ebb76a1514e806faa133abc1f dvb_usb_v2: remove usb_clear_halt() from stream [44919.465090] fc86b47f681e0c052cc6e71a4fd55f405fbe6d51 dvb_usb_v2: do not try to remove non-existent adapter [44919.465094] 6b86e957b62381c65f1edc068a4b2483ff9536df dvb_usb_v2: use dev_* logging macros [44919.467147] usbcore: registered new interface driver dvb_usb_af9035 [44919.467487] usb 2-1.2: dvb_usbv2: found a 'AVerMedia Twinstar (A825)' in cold state [44919.507679] usb 2-1.2: dvb_usbv2: downloading firmware from file 'dvb-usb-af9035-02.fw' [44919.817562] dvb_usb_af9035: firmware version=11.5.9.0 [44919.817613] usb 2-1.2: dvb_usbv2: found a 'AVerMedia Twinstar (A825)' in warm state [44919.820841] usb 2-1.2: dvb_usbv2: will pass the complete MPEG2 transport stream to the software demuxer [44919.820892] DVB: registering new adapter (AVerMedia Twinstar (A825)) [44919.826864] af9033: firmware version: LINK=11.5.9.0 OFDM=5.17.9.1 [44919.826875] DVB: registering adapter 0 frontend 0 (Afatech AF9033 (DVB-T))... [44920.166089] mxl5007t 16-0060: creating new instance [44920.166883] mxl5007t_get_chip_id: unknown rev (3f) [44920.166891] mxl5007t_get_chip_id: MxL5007T detected @ 16-0060 [44920.178890] usb 2-1.2: dvb_usbv2: 'AVerMedia Twinstar (A825)' error while loading driver (-22) [44920.179065] mxl5007t 16-0060: destroying instance [44920.179599] usb 2-1.2: dvb_usbv2: 'AVerMedia Twinstar (A825)' successfully deinitialized and disconnected [45352.006027] usb 2-1.2: USB disconnect, device number 6 [45370.454070] usbcore: deregistering interface driver dvb_usb_af9035 How can I enable debug parameters in order to provide better informations? I've compiled as usual using the following command sequence: git clone git://linuxtv.org/media_build.git cd media_build ./build --git git://linuxtv.org/anttip/media_tree.git dvb_usb_pull -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: pctv452e
On 07/04/2012 09:53 PM, André Weidemann wrote: On 04.07.2012 18:22, Antti Palosaari wrote: On 07/04/2012 07:04 PM, Steve Hill wrote: Ps. Steve, could you please give me full version of kernel which works with pctv452e? I think it was 2.6.37-1-kirkwood from Debian which I was using (this is an ARM system). As the new DVB-USB fixes many bugs I ask you to test it. I converted pctv452e driver for you: http://git.linuxtv.org/anttip/media_tree.git/shortlog/refs/heads/pctv452e Only PCTV device supported currently, not TechnoTrend at that time. Can I ask why it only works on the PCTV devices? I was under the impression that the TechnoTrend hardware was identical? If you are able to provide any pointers as to where the TechnoTrend support is broken (or what debugging I should be turning on to figure out where it is broken) then that would be helpful. I don't have hardware, no PCTV neither TechnoTrend. I just converted PCTV as Marx seems to have such device and he was blaming. Code wasn't 100% similar, for example TechnoTrend has CI PCTV doesn't. It should not fix problems but it could since I fixed some nasty bugs. Lets wait test report first and make decision what to do after that. The pctv452e and TT-connect S2-3600 are identical in hardware. Only USB IDs and remote control codes differ between the two. The Pinnacle box has its own remote. The TT-connect uses the same RC as the TT-budget series. The TT-connect S2-3650-CI has an additional CI slot. OK. In addition to CI support and remote controller there was also .read_mac_address() callback implemented for TechnoTrend. But as .read_mac_address() is heavily optional and useless it could be possible driver author just left it unimplemented for PCTV - or PCTV does not has MAC address. You seems to be marked as a one module author, I can guess you know reason? Also if you has hardware, could you make some tests in order to get that driver fixed :] regards Antti -- http://palosaari.fi/ -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: pctv452e
On 04.07.2012 18:22, Antti Palosaari wrote: On 07/04/2012 07:04 PM, Steve Hill wrote: Ps. Steve, could you please give me full version of kernel which works with pctv452e? I think it was 2.6.37-1-kirkwood from Debian which I was using (this is an ARM system). As the new DVB-USB fixes many bugs I ask you to test it. I converted pctv452e driver for you: http://git.linuxtv.org/anttip/media_tree.git/shortlog/refs/heads/pctv452e Only PCTV device supported currently, not TechnoTrend at that time. Can I ask why it only works on the PCTV devices? I was under the impression that the TechnoTrend hardware was identical? If you are able to provide any pointers as to where the TechnoTrend support is broken (or what debugging I should be turning on to figure out where it is broken) then that would be helpful. I don't have hardware, no PCTV neither TechnoTrend. I just converted PCTV as Marx seems to have such device and he was blaming. Code wasn't 100% similar, for example TechnoTrend has CI PCTV doesn't. It should not fix problems but it could since I fixed some nasty bugs. Lets wait test report first and make decision what to do after that. The pctv452e and TT-connect S2-3600 are identical in hardware. Only USB IDs and remote control codes differ between the two. The Pinnacle box has its own remote. The TT-connect uses the same RC as the TT-budget series. The TT-connect S2-3650-CI has an additional CI slot. André -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
cron job: media_tree daily build: ERRORS
This message is generated daily by a cron job that builds media_tree for the kernels and architectures in the list below. Results of the daily build of media_tree: date:Wed Jul 4 19:00:20 CEST 2012 git hash:704a28e88ab6c9cfe393ae626b612cab8b46028e gcc version: i686-linux-gcc (GCC) 4.7.1 host hardware:x86_64 host os: 3.4.07-marune linux-git-arm-eabi-davinci: WARNINGS linux-git-arm-eabi-exynos: WARNINGS linux-git-arm-eabi-omap: WARNINGS linux-git-i686: WARNINGS linux-git-m32r: WARNINGS linux-git-mips: WARNINGS linux-git-powerpc64: WARNINGS linux-git-x86_64: WARNINGS linux-2.6.31.12-x86_64: ERRORS linux-2.6.32.6-x86_64: ERRORS linux-2.6.33-x86_64: WARNINGS linux-2.6.34-x86_64: WARNINGS linux-2.6.35.3-x86_64: WARNINGS linux-2.6.36-x86_64: WARNINGS linux-2.6.37-x86_64: WARNINGS linux-2.6.38.2-x86_64: WARNINGS linux-2.6.39.1-x86_64: WARNINGS linux-3.0-x86_64: WARNINGS linux-3.1-x86_64: WARNINGS linux-3.2.1-x86_64: WARNINGS linux-3.3-x86_64: WARNINGS linux-3.4-x86_64: WARNINGS linux-2.6.31.12-i686: ERRORS linux-2.6.32.6-i686: ERRORS linux-2.6.33-i686: WARNINGS linux-2.6.34-i686: WARNINGS linux-2.6.35.3-i686: WARNINGS linux-2.6.36-i686: WARNINGS linux-2.6.37-i686: WARNINGS linux-2.6.38.2-i686: WARNINGS linux-2.6.39.1-i686: WARNINGS linux-3.0-i686: WARNINGS linux-3.1-i686: WARNINGS linux-3.2.1-i686: WARNINGS linux-3.3-i686: WARNINGS linux-3.4-i686: WARNINGS apps: WARNINGS spec-git: WARNINGS sparse: ERRORS Detailed results are available here: http://www.xs4all.nl/~hverkuil/logs/Wednesday.log Full logs are available here: http://www.xs4all.nl/~hverkuil/logs/Wednesday.tar.bz2 The V4L-DVB specification from this daily build is here: http://www.xs4all.nl/~hverkuil/spec/media.html -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: pctv452e
W dniu 2012-07-04 18:22, Antti Palosaari pisze: I don't have hardware, no PCTV neither TechnoTrend. I just converted PCTV as Marx seems to have such device and he was blaming. Code wasn't 100% similar, for example TechnoTrend has CI PCTV doesn't. It should not fix problems but it could since I fixed some nasty bugs. Lets wait test report first and make decision what to do after that. I've connected device and I'm starting to checkout from git and compiling. Marx -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: AF9035 Twinstar has firmware errors
Hello and thank you for testing. On 07/04/2012 09:55 PM, pierigno wrote: hello, I've downloaded and compiled against karnel 3.0.0 and kernel 3.4.3 the latest git tree from antii, branch dvb-usb-pull, and it doesn't recognize my dual tuner Avermedia Twinstar (af9035 + mxl5007t) anymore. Here's the logs from dmesg (the compiled modules do not have any debug parameters to enable): It is uses new / current dynamic debugs. modprobe dvb_usbv2; echo -n 'module dvb_usbv2 +p' /sys/kernel/debug/dynamic_debug/control echo 'file drivers/media/dvb/dvb-usb/usb_urb.c line 30 -p' /sys/kernel/debug/dynamic_debug/control modprobe dvb_usb_af9035; echo -n 'module dvb_usb_af9035 +p' /sys/kernel/debug/dynamic_debug/control [44919.820892] DVB: registering new adapter (AVerMedia Twinstar (A825)) [44919.826864] af9033: firmware version: LINK=11.5.9.0 OFDM=5.17.9.1 [44919.826875] DVB: registering adapter 0 frontend 0 (Afatech AF9033 (DVB-T))... [44920.166089] mxl5007t 16-0060: creating new instance [44920.166883] mxl5007t_get_chip_id: unknown rev (3f) [44920.166891] mxl5007t_get_chip_id: MxL5007T detected @ 16-0060 [44920.178890] usb 2-1.2: dvb_usbv2: 'AVerMedia Twinstar (A825)' error while loading driver (-22) hmm, -22 == -EINVAL. Should look where this is coming from... How can I enable debug parameters in order to provide better informations? I've compiled as usual using the following command sequence: git clone git://linuxtv.org/media_build.git cd media_build ./build --git git://linuxtv.org/anttip/media_tree.git dvb_usb_pull I wasn't even aware that is possible. Nice! regards Antti -- http://palosaari.fi/ -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [GIT PULL FOR v3.6] mostly remove V4L2_FL_LOCK_ALL_FOPS
Hi Hans, On 07/04/2012 07:42 PM, Hans Verkuil wrote: Hi Mauro, This pull request builds on (and includes) this core patch series: http://patchwork.linuxtv.org/patch/13180/ It is identical to the RFC patch series I posted before: http://www.mail-archive.com/linux-media@vger.kernel.org/msg48184.html ...except that I dropped the patches touching s5p-fimc and fimc-lite and the final patch removing the flag altogether. Sylwester posted patches for those two drivers, but they won't apply. Sylwester, can you rebase those patches? Once I have those, then I can make another pull request that fixes those two drivers and removes the flag completely. First of all, sorry about the trouble. These patches are available at: git://git.infradead.org/users/kmpark/linux-samsung v4l-fimc-next The first one was already included in a pull request with fixes for 3.5-rc: http://patchwork.linuxtv.org/patch/13149. It is not really needed for your V4L2_FL_LOCK_ALL_FOPS removal changeset. You only need the top one from the above branch. The reason why those 2 patches won't apply to the current media tree is a pending fixups pull request from over a month ago - http://patchwork.linuxtv.org/patch/11503. These are mostly important fixes for new code that went into 3.5, and I'm really not happy they're still not upstream :( So I would propose you to merge v4l-fimc-fixes branch from git://git.infradead.org/users/kmpark/linux-samsung, then there won't be any merge conflicts. Please feel free to add the top patch: s5p-fimc: Remove V4L2_FL_LOCK_ALL_FOPS flag to your pull request including the patch removing V4L2_FL_LOCK_ALL_FOPS. Here is a gitweb link: http://git.infradead.org/users/kmpark/linux-samsung/shortlog/refs/heads/v4l-fimc-next -- Regards, Sylwester -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
CrystalHD - Add 32 bits layer compatibility for 64 bits processor mode - patch
This patch attached hereafter add mainly the CONFIG_COMPAT 32 bits compatibility layer to the linux crystalhd repository code git://linuxtv.org/jarod/crystalhd.git release: fdd2f19ac739a3db1fd7469ea19ceaefe0822e5a, and fixes minor bugs. I hope it may be useful. Changes: Add 32 bits layer compatibility for 64 bits processor mode. Enums in headers are modified for better compatibility with kernel source code. Some general minor fixes added too. This works fine while using ia32 mode on a x86-64 kernel, and I hope with the new x32 abi too. Best Regards, Patrick LERDA. crystalhd-20120704-r0.patch.xz Description: application/xz
Re: AF9035 Twinstar has firmware errors
On 07/04/2012 10:08 PM, Antti Palosaari wrote: Hello and thank you for testing. On 07/04/2012 09:55 PM, pierigno wrote: hello, I've downloaded and compiled against karnel 3.0.0 and kernel 3.4.3 the latest git tree from antii, branch dvb-usb-pull, and it doesn't recognize my dual tuner Avermedia Twinstar (af9035 + mxl5007t) anymore. Here's the logs from dmesg (the compiled modules do not have any debug parameters to enable): It is uses new / current dynamic debugs. modprobe dvb_usbv2; echo -n 'module dvb_usbv2 +p' /sys/kernel/debug/dynamic_debug/control echo 'file drivers/media/dvb/dvb-usb/usb_urb.c line 30 -p' /sys/kernel/debug/dynamic_debug/control modprobe dvb_usb_af9035; echo -n 'module dvb_usb_af9035 +p' /sys/kernel/debug/dynamic_debug/control [44919.820892] DVB: registering new adapter (AVerMedia Twinstar (A825)) [44919.826864] af9033: firmware version: LINK=11.5.9.0 OFDM=5.17.9.1 [44919.826875] DVB: registering adapter 0 frontend 0 (Afatech AF9033 (DVB-T))... [44920.166089] mxl5007t 16-0060: creating new instance [44920.166883] mxl5007t_get_chip_id: unknown rev (3f) [44920.166891] mxl5007t_get_chip_id: MxL5007T detected @ 16-0060 [44920.178890] usb 2-1.2: dvb_usbv2: 'AVerMedia Twinstar (A825)' error while loading driver (-22) hmm, -22 == -EINVAL. Should look where this is coming from... It was coming from the remote controller registration when there is no keytable defined :/ Maybe best to load RC_MAP_EMPTY from af9035 in case no remote map defined... rc-map_name = RC_MAP_EMPTY; Anyhow, I have to look how to resolve that correctly. regards Antti -- http://palosaari.fi/ -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH 1/2] [media] drxk: Make the QAM demodulator command parameters configurable. [v3]
Hi, here's an updated patch which fixes the style issues (sorry for that). Regards, Martin -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH 1/2] [media] drxk: Make the QAM demodulator command parameters configurable.
Currently there are two different implementations (in the firmware) for
the QAM demodulator command: one takes 4 and the other takes 2 parameters.
The driver shows an error in dmesg When using the 4-parameter command with
firmware that implements the 2-parameter command.
Unfortunately this happens every time when chaning the frequency (on DVB-C).
This patch simply makes configurable, how many command parameters will be
used.
All existing drxk_config instances using the drxk_a3.mc were updated
because this firmware is the only loadable firmware where the QAM
demodulator command takes 4 parameters. Some firmwares in the ROM
might also use it.
The drxk instances in the em28xx-dvb driver were also updated to
silence the warnings.
If no qam_demod_parameter_count is given in the drxk_config struct,
then the correct number of parameters will be auto-detected.
Signed-off-by: Martin Blumenstingl martin.blumensti...@googlemail.com
---
drivers/media/dvb/ddbridge/ddbridge-core.c | 1 +
drivers/media/dvb/frontends/drxk.h | 11 ++-
drivers/media/dvb/frontends/drxk_hard.c| 112 ++---
drivers/media/dvb/frontends/drxk_hard.h| 1 +
drivers/media/dvb/ngene/ngene-cards.c | 1 +
drivers/media/video/em28xx/em28xx-dvb.c| 4 ++
6 files changed, 104 insertions(+), 26 deletions(-)
diff --git a/drivers/media/dvb/ddbridge/ddbridge-core.c
b/drivers/media/dvb/ddbridge/ddbridge-core.c
index 131b938..ebf3f05 100644
--- a/drivers/media/dvb/ddbridge/ddbridge-core.c
+++ b/drivers/media/dvb/ddbridge/ddbridge-core.c
@@ -578,6 +578,7 @@ static int demod_attach_drxk(struct ddb_input *input)
memset(config, 0, sizeof(config));
config.microcode_name = drxk_a3.mc;
+ config.qam_demod_parameter_count = 4;
config.adr = 0x29 + (input-nr 1);
fe = input-fe = dvb_attach(drxk_attach, config, i2c);
diff --git a/drivers/media/dvb/frontends/drxk.h
b/drivers/media/dvb/frontends/drxk.h
index 9d64e4f..d615d7d 100644
--- a/drivers/media/dvb/frontends/drxk.h
+++ b/drivers/media/dvb/frontends/drxk.h
@@ -20,6 +20,14 @@
* means that 1=DVBC, 0 = DVBT. Zero means the opposite.
* @mpeg_out_clk_strength: DRXK Mpeg output clock drive strength.
* @microcode_name:Name of the firmware file with the microcode
+ * @qam_demod_parameter_count: The number of parameters used for the command
+ * to set the demodulator parameters. All
+ * firmwares are using the 2-parameter commmand.
+ * An exception is the drxk_a3.mc firmware,
+ * which uses the 4-parameter command.
+ * A value of 0 (default) or lower indicates that
+ * the correct number of parameters will be
+ * automatically detected.
*
* On the *_gpio vars, bit 0 is UIO-1, bit 1 is UIO-2 and bit 2 is
* UIO-3.
@@ -38,7 +46,8 @@ struct drxk_config {
u8 mpeg_out_clk_strength;
int chunk_size;
- const char *microcode_name;
+ const char *microcode_name;
+ int qam_demod_parameter_count;
};
#if defined(CONFIG_DVB_DRXK) || (defined(CONFIG_DVB_DRXK_MODULE) \
diff --git a/drivers/media/dvb/frontends/drxk_hard.c
b/drivers/media/dvb/frontends/drxk_hard.c
index 8fa28bb..07b362f 100644
--- a/drivers/media/dvb/frontends/drxk_hard.c
+++ b/drivers/media/dvb/frontends/drxk_hard.c
@@ -5415,12 +5415,67 @@ static int GetQAMLockStatus(struct drxk_state *state,
u32 *pLockStatus)
#define QAM_LOCKRANGE__M 0x10
#define QAM_LOCKRANGE_NORMAL 0x10
+static int QAMDemodulatorCommand(struct drxk_state *state,
+int numberOfParameters)
+{
+ int status;
+ u16 cmdResult;
+ u16 setParamParameters[4] = { 0, 0, 0, 0 };
+
+ setParamParameters[0] = state-m_Constellation; /* modulation */
+ setParamParameters[1] = DRXK_QAM_I12_J17; /* interleave mode */
+
+ if (numberOfParameters == 2) {
+ u16 setEnvParameters[1] = { 0 };
+
+ if (state-m_OperationMode == OM_QAM_ITU_C)
+ setEnvParameters[0] = QAM_TOP_ANNEX_C;
+ else
+ setEnvParameters[0] = QAM_TOP_ANNEX_A;
+
+ status = scu_command(state,
+SCU_RAM_COMMAND_STANDARD_QAM |
SCU_RAM_COMMAND_CMD_DEMOD_SET_ENV,
+1, setEnvParameters, 1, cmdResult);
+ if (status 0)
+ goto error;
+
+ status = scu_command(state,
+SCU_RAM_COMMAND_STANDARD_QAM |
SCU_RAM_COMMAND_CMD_DEMOD_SET_PARAM,
+numberOfParameters, setParamParameters,
+1, cmdResult);
+ } else if (numberOfParameters == 4) {
+ if
[PATCH 2/2] [media] drxk: Improve logging. [v3]
Hi, here's an updated patch, rebased for the changes in patch 1. Regards, Martin -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH 2/2] [media] drxk: Improve logging.
This patch simply fixes some logging calls:
- Use KERN_INFO when printing the chip status.
- Add a missing space when logging the drxk_gate_ctrl call.
- Use the same logging text as always if the scu_command in GetQAMLockStatus
fails.
Signed-off-by: Martin Blumenstingl martin.blumensti...@googlemail.com
---
drivers/media/dvb/frontends/drxk_hard.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/media/dvb/frontends/drxk_hard.c
b/drivers/media/dvb/frontends/drxk_hard.c
index 07b362f..1e4d3d5 100644
--- a/drivers/media/dvb/frontends/drxk_hard.c
+++ b/drivers/media/dvb/frontends/drxk_hard.c
@@ -959,7 +959,7 @@ static int GetDeviceCapabilities(struct drxk_state *state)
if (status 0)
goto error;
-printk(KERN_ERR drxk: status = 0x%08x\n, sioTopJtagidLo);
+ printk(KERN_INFO drxk: status = 0x%08x\n, sioTopJtagidLo);
/* driver 0.9.0 */
switch ((sioTopJtagidLo 29) 0xF) {
@@ -5388,7 +5388,7 @@ static int GetQAMLockStatus(struct drxk_state *state, u32
*pLockStatus)
SCU_RAM_COMMAND_CMD_DEMOD_GET_LOCK, 0, NULL, 2,
Result);
if (status 0)
- printk(KERN_ERR drxk: %s status = %08x\n, __func__, status);
+ printk(KERN_ERR drxk: Error %d on %s\n, status, __func__);
if (Result[1] SCU_RAM_QAM_LOCKED_LOCKED_DEMOD_LOCKED) {
/* 0x NOT LOCKED */
@@ -6327,7 +6327,7 @@ static int drxk_gate_ctrl(struct dvb_frontend *fe, int
enable)
{
struct drxk_state *state = fe-demodulator_priv;
- dprintk(1, %s\n, enable ? enable : disable);
+ dprintk(1, : %s\n, enable ? enable : disable);
if (state-m_DrxkState == DRXK_NO_DEV)
return -ENODEV;
--
1.7.11.1
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [bisected] Webcam Genius 1300[AF] V2 not working since kernel 2.6.39
(cc-ing Rafael for runtime PM advice, Peter who reported the same bug,
Laurent and Alexey for uvcvideo advice)
Hi,
Shubhadeep Chaudhuri wrote:
The webcams Genius 1300 V2 and Genius 1300AF V2 (and probably some built-in
MacBook iSight webcams) face an issue
[...]
Every application displays a black screen for the devices except for mplayer
which displays a green screen.
Output of lsusb -vvv -d 0458:7067
http://pastebin.com/9R9atS9L
Attached as lsusb-vvv.out for reference.
Output of mplayer tv:// -tv
driver=v4l2:width=640:height=480:device=/dev/video0
-fps 30
http://pastebin.com/pHuaKDv8
Attached as mplayer.out.
On doing git bisect, I was able to find the commit which brings the
regression.
It's commit e1620d591a75a10b15cf61dbf8243a0b7e6731a2 titled USB: Move runtime
PM callbacks to usb_device_pm_ops.
A bug was reported with UVC on sourceforge by another user
http://sourceforge.net/mailarchive/message.php?msg_id=29030464
Thanks for your work so far tracking this down. What's the newest
kernel you've experienced this bug with?
Others: known problem? Any ideas for tracking it down?
Thanks,
Jonathan
timemanx@TIMEMANX-PC ~ $ lsusb
Bus 001 Device 002: ID 0458:7067 KYE Systems Corp. (Mouse Systems)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
timemanx@TIMEMANX-PC ~ $ lsusb -vvv -d 0458:7067
Bus 001 Device 002: ID 0458:7067 KYE Systems Corp. (Mouse Systems)
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass 2 ?
bDeviceProtocol 1 Interface Association
bMaxPacketSize064
idVendor 0x0458 KYE Systems Corp. (Mouse Systems)
idProduct 0x7067
bcdDevice1.00
iManufacturer 2 KYE SYSTEMS CORP.
iProduct1 iSlim 1300AF V2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 1068
bNumInterfaces 4
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 168mA
Interface Association:
bLength 8
bDescriptorType11
bFirstInterface 0
bInterfaceCount 2
bFunctionClass 14 Video
bFunctionSubClass 3 Video Interface Collection
bFunctionProtocol 0
iFunction 5 iSlim 1300AF V2
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass14 Video
bInterfaceSubClass 1 Video Control
bInterfaceProtocol 0
iInterface 5 iSlim 1300AF V2
VideoControl Interface Descriptor:
bLength13
bDescriptorType36
bDescriptorSubtype 1 (HEADER)
bcdUVC 1.00
wTotalLength 103
dwClockFrequency 15.00MHz
bInCollection 1
baInterfaceNr( 0) 1
VideoControl Interface Descriptor:
bLength 9
bDescriptorType36
bDescriptorSubtype 3 (OUTPUT_TERMINAL)
bTerminalID 2
wTerminalType 0x0101 USB Streaming
bAssocTerminal 0
bSourceID 5
iTerminal 0
VideoControl Interface Descriptor:
bLength26
bDescriptorType36
bDescriptorSubtype 6 (EXTENSION_UNIT)
bUnitID 4
guidExtensionCode {7033f028-1163-2e4a-ba2c-6890eb334016}
bNumControl 8
bNrPins 1
baSourceID( 0) 3
bControlSize1
bmControls( 0) 0x3f
iExtension 0
VideoControl Interface Descriptor:
bLength26
bDescriptorType36
bDescriptorSubtype 6 (EXTENSION_UNIT)
bUnitID 5
guidExtensionCode {3fae1228-d7bc-114e-a357-6f1edef7d61d}
bNumControl 8
bNrPins 1
baSourceID( 0) 4
bControlSize1
bmControls( 0) 0x18
iExtension 0
VideoControl Interface Descriptor:
bLength18
bDescriptorType36
bDescriptorSubtype 2 (INPUT_TERMINAL)
bTerminalID 1
