public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Krufky <mkrufky@m1k.net>
To: Mark Knecht <markknecht@gmail.com>
Cc: 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:47:49 -0500	[thread overview]
Message-ID: <43B0D585.3070700@m1k.net> (raw)
In-Reply-To: <5bdc1c8b0512261002n6167a78ewfc45a6d3a5078ac0@mail.gmail.com>

Mark Knecht wrote:

>On 12/24/05, Linus Torvalds <torvalds@osdl.org> wrote:
>  
>
>>Please do give it a try, and if you have any issues/regressions, send out
>>a note (even if you sent one earlier) so that we don't forget about it.
>>    
>>
>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:
>  
>
>>>>Unpacking ivtv-0.4.0.tar.gz to /var/tmp/portage/ivtv-0.4.0-r2/work
>>>>Unpacking pvr_2.0.24.23035.zip to /var/tmp/portage/ivtv-0.4.0-r2/work
>>>>Source unpacked.
>>>>        
>>>>
> * Preparing ivtv module
>created ivtv-svnversion.h
>make CONFIG_VIDEO_IVTV=m -C /usr/src/linux
>M=/var/tmp/portage/ivtv-0.4.0-r2/work /ivtv-0.4.0/driver modules
>make[1]: Entering directory `/usr/src/linux-2.6.15-rc7'
>  CC [M]  /var/tmp/portage/ivtv-0.4.0-r2/work/ivtv-0.4.0/driver/msp3400.o
>In file included from
>/var/tmp/portage/ivtv-0.4.0-r2/work/ivtv-0.4.0/driver/comp at.h:77,
>                 from
>/var/tmp/portage/ivtv-0.4.0-r2/work/ivtv-0.4.0/driver/msp3 400.c:52:
>include/linux/videodev.h: In function `video_device_create_file':
>include/linux/videodev.h:21: error: dereferencing pointer to incomplete type
>include/linux/videodev.h: In function `video_device_remove_file':
>include/linux/videodev.h:27: error: dereferencing pointer to incomplete type
>In file included from
>/var/tmp/portage/ivtv-0.4.0-r2/work/ivtv-0.4.0/driver/comp at.h:77,
>                 from
>/var/tmp/portage/ivtv-0.4.0-r2/work/ivtv-0.4.0/driver/msp3 400.c:52:
>include/linux/videodev.h:30:5: warning: "OBSOLETE_OWNER" is not defined
>include/linux/videodev.h: At top level:
>include/linux/videodev.h:204: error: `VIDEO_MAX_FRAME' undeclared here
>(not in a  function)
>make[2]: *** [/var/tmp/portage/ivtv-0.4.0-r2/work/ivtv-0.4.0/driver/msp3400.o]
>E rror 1
>make[1]: *** [_module_/var/tmp/portage/ivtv-0.4.0-r2/work/ivtv-0.4.0/driver]
>Err or 2
>make[1]: Leaving directory `/usr/src/linux-2.6.15-rc7'
>make: *** [all] Error 2
>
>!!! ERROR: media-tv/ivtv-0.4.0-r2 failed.
>!!! Function linux-mod_src_compile, Line 505, Exitcode 2
>!!! Unable to make                                  KDIR=/usr/src/linux all.
>!!! If you need support, post the topmost build error, NOT this status message.
>
>gandalf src #
>
>   Most probably this is stuff the Gentoo devs will clean up when the
>real kernel comes out but I *think* you were asking for this sort of
>info so I'm posting it back.
>  
>
Mark-

You don't have to worry about this... Since ivtv is an out-of-tree 
kernel module, and 2.6.15 is not released to mainline yet, so you cant 
expect the distros to make their external driver packages compatable.

Anyhow, I believe that ivtv 0.5.x is meant to be built against 2.6.15 
...  We have been merging some of the modules from ivtv into v4l, and 
some of those modules have already made it into 2.6.15.  I think you 
will run into module collisions using ivtv 0.4.x with kernel 2.6.15, but 
i'm not sure about that.  Please see the ivtv mailing list / web site 
for more information about this, and how to get it to work with your kernel.

Eventually, the ivtv driver will entirely be merged into v4l (and the 
kernel), and things will be much easier.  Until then, you should try the 
new 0.5.x version of ivtv with Kernel 2.6.15

Cheers,

-Michael

  parent reply	other threads:[~2005-12-27  8:35 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
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 [this message]
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=43B0D585.3070700@m1k.net \
    --to=mkrufky@m1k.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markknecht@gmail.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