Hi Devin, On Tue, 19 Jan 2010, Devin Heitmueller wrote:
[..] I want to focus my development on v4l-dvb. That said, I want a stable codebase on which I can write v4l-dvb drivers, without having to worry about whether or not my wireless driver is screwed up this week, or whether the ALSA guys broke my audio support for the fifth time in two years. I don't want to wonder whether the crash I just experienced is because they've replaced the scheduler yet again and they're still shaking the bugs out. I don't want to be at the mercy of whatever ABI changes they're doing this week which break my Nvidia card (and while I recognize as open source developers we care very little about "closed source drivers", we shouldn't really find it surprising that many developers who are rendering HD video might be using Nvidia cards).
I agree with Devin. We can't lose and off-tree build system like we have it today in v4l-dvb.
What I suggested in my first Email was to put the build system outside the v4l-dvb into another repo (e.g. 'v4l-dvb-build') and then telling it to make links from the linux-v4l-dvb/ clone.
I'm not sure what needs to be done for the backward-compat with #if KERNEL_VERSION ... But I'm sure we can find a solution for that. -- Patrick Boettcher - Kernel Labs http://www.kernellabs.com/ -- 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
