From: Andrew Morton <akpm@osdl.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: steven@uplinklabs.net
Subject: Fw: [Bugme-new] [Bug 4394] New: Intel 855 (i810): 1280x768 wide screen FB resolution not available
Date: Wed, 23 Mar 2005 18:37:29 -0800 [thread overview]
Message-ID: <20050323183729.3797ce87.akpm@osdl.org> (raw)
Begin forwarded message:
Date: Wed, 23 Mar 2005 16:45:12 -0800
From: bugme-daemon@osdl.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 4394] New: Intel 855 (i810): 1280x768 wide screen FB resolution not available
http://bugme.osdl.org/show_bug.cgi?id=4394
Summary: Intel 855 (i810): 1280x768 wide screen FB resolution not
available
Kernel Version: 2.6.11
Status: NEW
Severity: normal
Owner: davej@codemonkey.org.uk
Submitter: steven@uplinklabs.net
Distribution: Gentoo 2004.3
Hardware Environment:
Sony Vaio PCG-TR1AP
Intel 855GM graphics controller
1280x768 wide screen LCD flat panel
Software Environment: N/A
Problem Description:
Wide screen resolutions, such as 1280x768 are not supported by the console
framebuffer. Can this support be added?
Steps to reproduce: N/A
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
-------------------------------------------------------
This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005
Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows
Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register
by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click
next reply other threads:[~2005-03-24 2:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 2:37 Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-26 0:22 Fw: [Bugme-new] [Bug 4394] New: Intel 855 (i810): 1280x768 wide screen FB resolution not available Andrew Morton
2005-06-06 19:05 ` James Simmons
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050323183729.3797ce87.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=steven@uplinklabs.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).