linux-kernel - KMS + fb + FBIOPUT

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]

Message-ID: <8563BBE2A1F848B3B98C1A5FAE08BD09@avitech.sk>
Date:	Tue, 28 Apr 2009 10:32:34 +0200
From:	"Peter Hanzel" <hanzelpeter@...il.com>
To:	<linux-kernel@...r.kernel.org>
Cc:	<linux-fbdev-devel@...ts.sourceforge.net>
Subject: KMS + fb + FBIOPUT_VSCREENINFO

Hello.

I have tried DRM with intel KMS and it is workiing. I am using only 
framebuffer console.
Fbcon initializes 1280x800 mode and it works like a charm.

But when I try to call FBIOPUT_VSCREENINFO on /dev/fb0, it always returns 
EINVAL,
I have checked drivers/gpu/drm/i915/intel_fb.c
and found that

intelfb_check_var        returns -EINVAL     if (var->pixclock == -1 || 
!var->pixclock)
intelfb_set_par             returns -EINVAL    if (var->pixclock != -1) { 
DRM_ERROR("PIXEL CLCOK SET\n");  return

So the FBIOPUT_VSCREENINFO always fails.

So is the change of resolution not supported through FBIOPUT_VSCREENINFO 
call?

Thanks.


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