So I just found this as a ticket:
------BEGIN PASTE------
I can verify this behavior on debian sarge with the 2.4.27-2-386
kernel running a pvr-350.
It does not build tuner.o or tda9887.o
When i force tuner to build to build i get the same errors. I changed
#include <media/audiochip.h> to #include "audiochip.h" so it could
find it. It did not fix any of the other errors.
12/03/05 16:07:56: Modified by hverkuil
* status changed from new to closed.
* resolution set to fixed.
This is fixed in the upcoming 0.4.1.
------END PASTE------
So it looks like 0.4.0 will not compile tuner (I actually tried adding
tuner.o to the OBJS list, and got the error they were mentioning
here). And it looks like 0.4.1 is the fix. My problem with 0.4.1, as
you recall, was that hotplug was complaining a bit. Perhaps I will
try fixing that up, and try to work with 0.4.1.
Yes, I do have my reasons for going with 2.4 over 2.6. Actually, just
before starting to post about my problems here, I tried migrating to
2.6. I spent 6 hours on the migration and still couldn't get my
system working well; couldn't even get into X after that time, and X
was NOT reporting any errors in its log. It would just look like it
was starting, then drop me back at a prompt. So I decided that going
back to 2.4 was the better route, and to try to get myth working from
that direction. Obviously, that's been a pain too, but at least I
have a working computer, otherwise. :)
Of course, if I just can't get this working, perhaps a move to 2.6 is
in my future. And I had been so hoping to have myth up and running by
today - Battlestar Galactica starts up again tonight. :)
So I will try to fix up my hotplug problem, and then try ivtv again. Thanks!
Mike
On 1/6/06, Keith C <[EMAIL PROTECTED]> wrote:
> On Jan 6, 2006, at 10:28 AM, Michael Banys wrote:
>
> > Hi Keith,
> >
> >> I used an SVN checkout to grab it. Not sure where your 0.4.0 is
> >> from, but it doesn't look right.
> >
> >
> > I looked through the svn repository, and it seems that the 0.4 branch
> > that is there (http://ivtvdriver.org/svn/ivtv/branches/0.4/) is the
> > 0.4.1 version. I compared it with the 0.4.0 and 0.4.1 source tarballs
> > that I downloaded, and the Makefile2.4 in svn and in the 0.4.1 source
> > tarball were the same. The version of Makefile2.4 I have in the 0.4.0
> > source tarball is different.
> >
> > Even though the repository seems to only contain the 0.4.1 version
> > under the 0.4 branch, I tried getting only the 0.4.0 version with the
> > following command:
> >
> > svn co http://ivtvdriver.org/svn/ivtv/branches/0.4 ivtv-0.4.0
> >
> > So it downloaded, and I compiled/installed it. But it's still the
> > 0.4.1 version, as when I ran it, it complained about hotplug and was
> > looking for the firmware files as named in 0.4.1. Is there some other
> > way to obtain specifically the 0.4.0 branch from svn?
> >
>
> Well, thats how I checked it out, and was assuming I was getting the
> right one, but I was very wrong. Now that I've read up on svn a
> little, the correct checkout would have been :
> svn co http://ivtvdriver.org/svn/ivtv/tags/0.4.0 ivtv-0.4.0
>
> This would result in exactly the Makefile2.4 that you have, which
> just doesn't seem to work very well for you at all. You could try
> adding tuner.o to the list of OBJS in that make file and see if that
> fixes your problem. It will still overwrite the original kernel
> modules, which I'm not a fan of, but there must be a reason they took
> that route for 2.4 kernels. By the way, you probably have your
> reasons for being on 2.4, but I've found 2.6 to be much better for my
> Myth box.
>
> Keith C
>
> >
> >
> >
> >
> >
> >
> > On 1/6/06, Keith C <[EMAIL PROTECTED]> wrote:
> >> On Jan 5, 2006, at 8:49 PM, Michael Banys wrote:
> >>
> >>> ...... BEGIN QUOTE ......
> >>> Crap, I've been backwards and forwards through the Makefiles and
> >>> can't explain your output below. First, any time tveeprom is
> >>> getting
> >>> built, so is tuner. Secondly, they would never install to /lib/
> >>> modules/2.4.27/kernel/drivers/media/video, they would install to /
> >>> lib/
> >>> modules/2.4.27/kernel/ivtv. Thats the way it work for > 2.4
> >>> kernels,
> >>> and the Makefile2.4 doesn't seem to vary from that.
> >>> ...... END QUOTE ......
> >>>
> >>> Ok, Keith, so I looked through my makefile, Makefile2.4, in the
> >>> driver
> >>> directory under ivtv0.4.0, and I wonder if we're looking at the same
> >>> file. In mine, which I'll paste below, there is NO mention of
> >>> tuner.o; also, the 3rd line seems to, by default, put the compiled
> >>> modules into /lib/modules/2.4.27/kernel/drivers/media/video. I
> >>> got my
> >>> source from the ivtvdriver.org website. Any thoughts?
> >>>
> >>> cat Makefile2.4:
> >>
> >> The Makefile2.4 listed below is NOT what is in SVN right now for
> >> 0.4.0. The correct one would start with :
> >> $ cat Makefile2.4
> >> ifneq ($(KERNELRELEASE),)
> >> include $(CURDIR)/Kbuild
> >>
> >> I used an SVN checkout to grab it. Not sure where your 0.4.0 is
> >> from, but it doesn't look right.
> >
> > _______________________________________________
> > ivtv-users mailing list
> > [email protected]
> > http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
>
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
--
.
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
