From: Michael Krufky <mkrufky@gmail.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Mark Knecht <markknecht@gmail.com>,
Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Ho ho ho.. Linux 2.6.15-rc7
Date: Tue, 27 Dec 2005 00:56:25 -0500 [thread overview]
Message-ID: <43B0D789.6060208@gmail.com> (raw)
In-Reply-To: <1135620892.8293.60.camel@mindpipe>
Lee Revell wrote:
>On Mon, 2005-12-26 at 10:02 -0800, Mark Knecht wrote:
>
>
>>Hi Linus,
>> I've visiting at my parents house and gave 2.6.15-rc7 a try on my
>>dad's machine. This machine is his normal desktop box which I
>>administer remotely, as well as a MythTV server. The new kernel built
>>and booted fine. I then built the NVidia stuff. However when I tried
>>to build the ivtv driver from portage it failed:
>>
>>
>There's nothing the kernel developers can do about regressions in out of
>tree modules - there is no stable kernel module API so the authors of
>that module will have to fix it.
>
>Any idea why the IVTV module has not been submitted for mainline?
>
Little by little, ivtv is being merged into V4L. There is a lot of
reorganization that is taking place, and it is not a very fast process.
As of 2.6.15-rc1, many of the modules from ivtv were merged into the
kernel through V4L. Recently, there was another ivtv fork discovered,
called paken. (for better details, see ivtv mailing list archives) The
ivtv guys are currently working on cleaning up the main ivtv module, and
merging in the code from the paken repo. When all is ready, it will all
be merged into v4l, and eventually the kernel.
Cheers,
Michael Krufky
next prev parent reply other threads:[~2005-12-27 5:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-25 3:39 Ho ho ho.. Linux 2.6.15-rc7 Linus Torvalds
2005-12-25 5:00 ` Keith Owens
2005-12-26 5:23 ` Grant Coady
2005-12-26 13:54 ` Kalin KOZHUHAROV
2005-12-28 9:11 ` Paul Rolland
2005-12-26 18:02 ` Mark Knecht
2005-12-26 18:14 ` Lee Revell
2005-12-27 2:49 ` Mark Knecht
2005-12-27 5:56 ` Michael Krufky [this message]
2005-12-27 13:23 ` James Courtier-Dutton
2005-12-27 17:53 ` Michael Krufky
2005-12-26 18:50 ` Markus Koßmann
2005-12-26 23:24 ` Mauro Carvalho Chehab
2005-12-27 5:47 ` Michael Krufky
2005-12-27 12:43 ` Pekka Enberg
2005-12-29 13:39 ` [2.6.15-rc7 patch] Reject SRAT tables that don't cover all memory Adrian Bunk
2005-12-29 16:07 ` Andi Kleen
2005-12-29 16:20 ` Adrian Bunk
2005-12-29 16:23 ` Andi Kleen
2006-01-02 16:46 ` 2.6.15-rc7: known regressions Adrian Bunk
2006-01-02 17:07 ` Andi Kleen
2006-01-02 17:23 ` Adrian Bunk
2006-01-02 17:38 ` Andi Kleen
2006-01-02 18:30 ` Ochal Christophe
2006-01-02 18:57 ` Paul E. McKenney
-- strict thread matches above, loose matches on Subject: below --
2005-12-27 11:44 Ho ho ho.. Linux 2.6.15-rc7 Luuk van der Duim
2005-12-28 16:10 Nicolas Mailhot
2005-12-28 17:13 ` Michael Krufky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43B0D789.6060208@gmail.com \
--to=mkrufky@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markknecht@gmail.com \
--cc=rlrevell@joe-job.com \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox