Hello Christoph,
> What the problem with 2.5, dvb and devfs?
The main problem is that our development "dvb-kernel" CVS tree *should*
compile under 2.4 aswell, because most of the dvb-users don't want to
participate in kernel development in general, but only on the
development of the dvb subsystem. So work is done on the "dvb-kernel"
tree, which should be synced with the 2.5 kernel frequently.
So, regarding devfs, I introduced #ifdefs around the functions that have
changed recently. That's not nice, I know. But in my eyes it's important
to keep the CVS and the kernel version more in sync.
IIRC Gerd Knorr has the same problems with his driver packages
(regarding the i2c subsystem mainly), but he has written some perl
scripts to remove the #ifdef stuff before submitting his patches...
> I already told one of the DVB folks
> (it wasn't you IIRC) that I'll publish a 2.5 devfs API on 2.4 header.
No, you spoke to Holger I think, who has maintained the dvb-core kernel
submissions before me.
> But first I have to fix the devfs API on 2.5 and randomly bringing
> back old crap and lots of ifdefs in those changing areas won't help.
I understand. But delaying the dvb updates just because a few calls to
the devfs subsystem (which are now separated by #ifdefs and can easily
be found) is not a good option either, or is it?
CU
Michael.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed May 07 2003 - 22:00:30 EST