> > Hi, > > I've deliberately avoided adding code for VBI - it's just too > difficult to get right on em28xx due to interesting buffer management > and locking issues. (For example, have you fixed the issue that causes > a kernel panic when recording analog video with MythTV? That was a > particularly interesting one.) In any case, that's another issue > entirely - this code is for DVB-T support. > > Also, just because this device isn't being sold anymore doesn't mean > it's not worth adding - there are other, fairly similar devices still > on sale. Unfortunately, I don't have access to newer hardware, and > most of the people with the access and knowledge don't seem to want to > have anything to do with it. (Why do I have a feeling that you have a > hand in this?) However, adding support should be easy - all the > necessary code exists and has done for a while (even drx397xd support > for the Pinnacle 330e and the new HVR-900). > The drx397x is only one chip of a series of newer ones which will follow in future. > Mainly, though, I'm doing it for my own benefit - I have this > hardware, and the changes are small and self-contained enough that I > should be able to stay up-to-date with upstream and keep newer kernels > working with minimal effort. (This tree is actually an updated version > of code I've been using for the past few months on PAL-I and DVB-T, > but didn't publish due to a bug with switching from digital to > analog.) > it's fine that you do it on your own purpose for yourself, although there's much more development going on on the other side. > (By the way, I still reckon your userspace code is a dead end, at > least as far as getting anything merged into the kernel. I think I may > have already explained why.) > There are several reasons for going that way I'm not up for waiting 2 years till something is implemented because some people don't want to discuss certain things. It's like discussing issues with a wall. This is the main point why I'm going the other way since this is simply no option, and everyone can see the result in earlier supported devices. The thing you're doing is of course based on my work again and even in future you cannot avoid to base things on that. As long as this root problem isn't solved I don't see any other way, and I'm definitely not the one who will delay any further devices anymore. Markus _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
