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-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090428235723.f9495676.akpm@linux-foundation.org>
Date:	Tue, 28 Apr 2009 23:57:23 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	"Peter Hanzel" <hanzelpeter@...il.com>
Cc:	<linux-kernel@...r.kernel.org>,
	<linux-fbdev-devel@...ts.sourceforge.net>,
	dri-devel@...ts.sourceforge.net
Subject: Re: KMS + fb + FBIOPUT_VSCREENINFO

(cc dri-devel)

On Tue, 28 Apr 2009 10:32:34 +0200 "Peter Hanzel" <hanzelpeter@...il.com> wrote:

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

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ