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
