[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <CCB52791-FFE9-487A-97E8-C902622CC162@vmware.com>
Date: Wed, 29 Apr 2009 15:15:23 +0200
From: Jakob Bornecrantz <jakob@...are.com>
To: Peter Hanzel <hanzelpeter@...il.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-fbdev-devel@...ts.sourceforge.net"
<linux-fbdev-devel@...ts.sourceforge.net>,
"dri-devel@...ts.sourceforge.net" <dri-devel@...ts.sourceforge.net>
Subject: Re: Intel KMS + fbcon + Mplayer
On 29 apr 2009, at 12.04, Peter Hanzel wrote:
> Hello.
>
> I have tried Intel KMS in kernel 2.6.91.1 with fbcon. I am using only
> framebuffer console.
> Most fb apps works, but I have problem with mplayer.
> The init works but the video is badly displayed.
> I have investigated the problem and found, that for my laptop mode
> 1280x800-32.
>
> The ioctl on /dev/fb0 FBIOGET_VSCREENINFO returns.
> var.bits_per_pixel=32
> var.transp.length = 0.
>
> So the mplayer thinks we are in 24 bit mode (maybe this is bug in
> mplayer,
> because bits_per_pixel is 32).
>
> But next I have checked it with kernel vesafb and for same mode
> (1280x800-32, vga=0x362 )
> The fb ioctl returns
> var.bits_per_pixel=32
> var.transp.length = 8.
>
> So is this intentionally made so. Because I think this mode use only
> red,
> green,blue and no transp. But for one pixel you must write 4 bytes.
> (so
> transp is not used).
Hmm, if I remember correctly from running mplayer in the early days of
kms mplayer has two fbdev drivers and I think that only #2 worked. It
did worked back then but it was a long time ago. Heck it was one of
the first things we demoed kms with.
Cheers Jakob.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists