linux-kernel - Intel KMS + fbcon + Mplayer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 29 Apr 2009 12:04:07 +0200
From:	"Peter Hanzel" <hanzelpeter@...il.com>
To:	<linux-kernel@...r.kernel.org>,
	<linux-fbdev-devel@...ts.sourceforge.net>,
	<dri-devel@...ts.sourceforge.net>
Subject: Intel KMS + fbcon + Mplayer

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).

--
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/