On 4/2/08, Another Sillyname <anothersname@xxxxxxxxxxxxxx> wrote: > Aidan > > So are you working on integrating the em28xx devices that are working > in v4l-dvb-kernel version into v4l-dvb (or ever your own version of > same)? > > Or will it require changes to too much code? Occasionally, yes - I can do, and generally it's fairly trivial, but since I don't have access to all this hardware myself, unless someone's willing to test it there's not much I can do. In fact, I just added untested support for the card to http://www.makomk.com/hg/v4l-dvb-em28xx. You'll need to "modprobe em28xx card=17", though, since your device uses a generic USB ID and I can't add autodetection without a copy of the dmesg output when loading the driver without card=17. (Also, while my version of the driver should in theory support DVB-T, the v4l-dvb version doesn't and probably won't any time soon.) > I have to say as a user/observer I find it ridiculous that there are > two branches of working code that are pretty close to the same and > won't work with each other. If there's one area that Linux really > clearly pi**es on Windows it's the handling of media and stuff like > this just switches people off. > > While not looking at the code or drawing any conclusions therein a new > layer on top of v4l-dvb (whichever version) seems counter productive > to me. > > Ho hum.....can someone please just tell me how to get my kit working > without having to re-invent the wheel. Also, you might be able to get it working with v4l-dvb-experimental by passing "card=94" to saa7134. No guarantees, though. > Thanks in advance. > > J > > On 01/04/2008, Aidan Thornton <makosoft@xxxxxxxxxxxxxx> wrote: _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
