On Mon, Aug 17, 2009 at 4:25 PM, Malcolm Lewis<coyoteuser@xxxxxxxxx> wrote: > Hi > I've been using the patches from > http://linuxtv.org/hg/~mkrufky/teledongle/rev/676e2f4475ed > on a Sabrent device in openSuSE and SLED, during testing with the > milestone 5 release of > 11.2 and kernel version 2.6.31-rc5-git3-2-desktop there needs to be > some changes to the > au0828-cards.c patch to enable building a kmp module; > > --- au0828-cards.c 2009-08-12 18:16:39.435886920 -0500 > +++ au0828-cards.c.orig 2009-08-12 18:28:22.176126368 -0500 > @@ -116,6 +116,12 @@ > .tuner_addr = ADDR_UNSET, > .i2c_clk_divider = AU0828_I2C_CLK_250KHZ, > }, > + [AU0828_BOARD_SYNTEK_TELEDONGLE] = { > + .name = "Syntek Teledongle [EXPERIMENTAL]", > + .tuner_type = UNSET, > + .tuner_addr = ADDR_UNSET, > + .i2c_clk_divider = AU0828_I2C_CLK_250KHZ, > + }, > }; > > /* Tuner callback function for au0828 boards. Currently only needed > @@ -248,6 +254,7 @@ > case AU0828_BOARD_HAUPPAUGE_HVR950Q: > case AU0828_BOARD_HAUPPAUGE_HVR950Q_MXL: > case AU0828_BOARD_HAUPPAUGE_WOODBURY: > + case AU0828_BOARD_SYNTEK_TELEDONGLE: /* FIXME */ > /* GPIO's > * 4 - CS5340 > * 5 - AU8522 Demodulator > @@ -325,6 +332,8 @@ > .driver_info = AU0828_BOARD_HAUPPAUGE_HVR950Q_MXL }, > { USB_DEVICE(0x2040, 0x8200), > .driver_info = AU0828_BOARD_HAUPPAUGE_WOODBURY }, > + { USB_DEVICE(0x05e1, 0x0400), > + .driver_info = AU0828_BOARD_SYNTEK_TELEDONGLE }, > { }, > }; > > > There are two versions I'm building and src for both can be found here; > http://download.opensuse.org/repositories/home:/malcolmlewis/ Malcolm, I would strongly advise against distributing packages based on these patches... This code was never merged into the master branch because it has potential to break devices at the hardware level, and it will create a support nightmare, based on the fact that there are multiple UNLIKE devices that use the same USB ID but actually contain different hardware components. As the patch may enable support for ONE of the variations, nobody has ever verified that the GPIO programming is safe to use, and there is no way to prevent the potentially harmful code from running on the wrong device. I, personally, do not want the responsibility of explaining to users that their usb sticks may be damaged because of code that got merged into the kernel -- that's why the code is in a separate repository until the issues can be dealt with. In general, users know that if they have to manually apply patches themselves, that they are doing so at their own risk. If you succeed in getting your device to work, please let me know -- I will be very interested to hear about it. Good Luck, Mike -- 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
