On Mon, 31 Jan 2005 13:10:27 -0800 (PST), kevin thayer
<[EMAIL PROTECTED]> wrote:
> oh i'm sorry, you said framebuffer
>
> i was using XShm... It is absolutely NOT recommended
> to use the framebuffer as a framebuffer device, as
> framebuffers map memory directly.
So the option you were using for mplayer was '-vo x11'?
I've also noticed an oddity if I use "ivtv" as the option for my
xorg.conf like this:
Section "Device"
Identifier "Hauppauge WinTV PVR 350, model 990"
Driver "ivtvdev"
# Option "fbdev" "/dev/fb1"
Option "ivtv" "/dev/fb1"
BusID "2:9:0"
EndSection
which results in an Xorg.0.log with this as the last few lines:
(II) IVTVDEV: driver for framebuffer: PVR-350
(II) Primary Device is: PCI 01:05:0
(--) Chipset PVR-350 found
(EE) ivtvHWProvbe failed to do IVTVFB_IOCTL_GET_STATE for device (null)
(EE) Screen 0 deleted because of no matching config section.
(II) UnloadModule: "ivtvdev"
(EE) Device(s) detected, but none match those in the config file.
if I uncomment the fbdev option and comment the ivtv option, it works,
although slowly.
But if I can give a different option to mplayer or xine I'd be happy.
Alex
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
