[ATrpms-users] Packages required for working ivtv-fb

[Axel Thimm]

On Mon, Jun 04, 2007 at 02:45:59PM +0100, Kevin R. Page wrote:
> On Mon, 2007-06-04 at 11:35 +0200, Axel Thimm wrote: 
> > ivtv-fb's requirements may not be fulfilled by the kenrel
> > (haven't checked on Fedora 7 whether that's true)
> 
> saa7127 still isn't built by default in the F7 kernel.
> 
> > either rbeuild your own kernel, or supply
> > v4l kernel modules. You should try to address this on ivtv-devel 
> > (which is actually the same server, but Hans Verkuil is found 
> > only there :).
> 
> I've read some more of the list archives...
> 
> It seems I shouldn't expect ivtv.ko and ivtv-fb.ko from the ivtv-kmdl to
> work with v4l drivers from video4linux-kmdl, because if you are using
> the video4linux-kmdl package you should be using the corresponding
> video4linux-ivtv-kmdl. Correct?

No, not really. I split out video4linux-ivtv-kmdl for people to be
able to use video4linux-kmdl with ivtv-kmdl, otherwise they would
always conflict.

> Do you build ivtv-kmdl against the modules in video4linux-kmdl, or the
> stock F7 v4l drivers?

It depends on the settings, currently it builds against F7's headers.

> If the latter, I don't think I should presume ivtv-fb should work.

Why not? it doesn't really deeply intervene with the v4l parts, it is
more on the fb side of the kernel.

> As far as I can tell, this is because as v4l2 has developed, ivtv has
> been subsumed into it; before you created the video4linux-ivtv-kmdl
> package ivtv.ko was included in video4linux-kmdl.
> 
> Unfortunately, this transition leaves ivtv-fb temporarily orphaned: as a
> framebuffer device, it shouldn't really live in v4l?
> 
> 
> Given that ivtv-kmdl can't be installed with video4linux-ivtv-kmdl,

I'm not sure about this. Perhaps it needs still some tweaking and
tuning until we get there, but this was the desired outcome of the
package split.

> and the F7 kernel doesn't include saa7127, wouldn't it be ok to
> build saa7127 in the ivtv-kmdl for those that don't want to use the
> newer v4l packages, given that ivtv-fb _requires_ saa7127 to work?

I asked Hans to include saa7127 in the ivtv tarball that would get
built & installed when the base kernel offers no saa7127. That was the
way the msp migration worked, too. IMHO that would be the best
solution.

> I guess the alternative is to file a bug on the missing saa7127 in
> Fedora bugzilla - I'll do this if you think it the correct way to
> proceed.

That owuld solve it, too, I think there already is one bugzilla on
this, and Jarow Wilson, who works now at Red Hat even talked to the
kernel guys about the missing modules. But file a bug against Red
Hat's bugzilla as well, in the worst case it will be marked as
duplicate of another, but people will become more aware of the need
for this module.

> > It fails with
> > In file included from ivtvhw.c:74:
> [snip]
> > I brought it up with Fedora's X people, but they say ivtv_xdriver
> > needs fixing.
> 
> Yes, I found the bug you filed at:
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229553
> http://ivtvdriver.org/pipermail/ivtv-devel/2007-February/004453.html

Ah, thanks, I was looking for the bug, when I quoted it, but couldn't
find it because it is closed.

> Do you know of any further progress since February? If not, I'll try
> and build it myself, and report errors to ivtv-devel.

Sure, try it.

What is really lacking is a ticket system for ivtv. ivtv have trac
support, but it doesn't really work due to spammers. I need to fix
this so that stuff like that doesn't get forgotten (I'm running the
ivtvdriver.org site as well)
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-users/attachments/20070604/2b90be52/attachment.bin