ivtv has an ioctl to tell you which framebuffer device it got, in case you weren't aware..
takes all the guesswork out of it :) -tmk --- John Harvey <[EMAIL PROTECTED]> wrote: > I have just been investigating a problem whereby the > current X driver uses > the wrong frame buffer device. > > This is caused by a change that happened ages ago > and instead of looking for > the fbdev option it is currently looking for ivtv. > > > > Since it doesn't find an ivtv option it will default > to looking for a device > specified in the FRAMEBUFFER environment variable > and then defaults to > /dev/fb0 > > > > So if you need to use a device other than /dev/fb0 > and you are using V04-V06 > of the ivtv X driver then you need to either > > > > 1) modify your Config file to add an ivtv > option (I would suggest > adding an ivtv option rather than changing the fbdev > since I want to change > this back for V07) > > Section "device" > > Identifier "Haupagge 350" > > Driver "ivtvdev" > > Option "fbdev" "/dev/fb1" > > Option "ivtv" "/dev/fb1" > > BusID "..." > > EndSection > > > > > > 2) set the FRAMEBUFFER environment variable ie > > > > export FRAMEBUFFER=/dev/fb1 > > > > For the next version I will also try to add some > code so that the probe does > more than just open the device. It should really > determine that the device > it opens is actually an ivtv driver. > > > > John > > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ ivtv-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
