Quoted 2 lines · Devel
The path patch_kraxel-2.4.26 from http://dl.bytesex.org/patches/ will be included into kernel 2.4.27? Thanks by now!
Nope, it wont. A quick look shows it touches a hell lot of stuff.

It basically brings v4l(2) of the 2.4.26 kernel to 2.6 level, including the v4l2 API + new drivers (which depend on v4l2).

Quoted 1 line

We should probably try to merge the sane bits? Gerd?

I'm not going to submit v4l2 for 2.4, people better should go with 2.6 of they need it. The only bits I can think of merging are the updates for bttv-cards.c, i.e. support for some new tv cards. New cards are rare these days through as new cards usually don't use bt878-based designs any more. Also it is low priority on my todo list and I'm just back from two weeks holiday with alot of pending stuff, so don't expect me looking at this soon (maybe not at all).

Gerd

Signature · 1 line

return -ENOSIG;

Marcelo Tosatti

2004-08-16 13:35 UTC #3 lore raw

Quoted 12 lines · Gerd Knorr

Quoted 5 lines · Marcelo Tosatti
Quoted 2 lines · Devel
The path patch_kraxel-2.4.26 from http://dl.bytesex.org/patches/ will be included into kernel 2.4.27? Thanks by now!
Nope, it wont. A quick look shows it touches a hell lot of stuff.
It basically brings v4l(2) of the 2.4.26 kernel to 2.6 level, including the v4l2 API + new drivers (which depend on v4l2).
Quoted 1 line
We should probably try to merge the sane bits? Gerd?

Quoted 7 lines

I'm not going to submit v4l2 for 2.4, people better should go with 2.6 of they need it. The only bits I can think of merging are the updates for bttv-cards.c, i.e. support for some new tv cards. New cards are rare these days through as new cards usually don't use bt878-based designs any more. Also it is low priority on my todo list and I'm just back from two weeks holiday with alot of pending stuff, so don't expect me looking at this soon (maybe not at all).

Fine!