From: Andrew Morton <akpm@osdl.org>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Fw: [Bugme-new] [Bug 6685] New: Permedia2 framebuffer on E250
Date: Mon, 19 Jun 2006 15:33:20 -0700 [thread overview]
Message-ID: <20060619153320.49a7c736.akpm@osdl.org> (raw)
Begin forwarded message:
Date: Tue, 13 Jun 2006 13:48:20 -0700
From: bugme-daemon@bugzilla.kernel.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 6685] New: Permedia2 framebuffer on E250
http://bugzilla.kernel.org/show_bug.cgi?id=6685
Summary: Permedia2 framebuffer on E250
Kernel Version: 2.6.17-rc6
Status: NEW
Severity: normal
Owner: platform_sparc64@kernel-bugs.osdl.org
Submitter: marvin@mydatex.cz
Most recent kernel where this bug did not occur: 2.4.27
Distribution: Debian Sid
Hardware Environment: Sun E250
Software Environment: Permedia2 FB
Problem Description:
I have E250 with Raptor GFX framebuffer. On 2.4.27 works fine but with any
kernel which I tested > 2.6.12 frame buffer console looks very ugly and is
unreadable fonts is defocusing.
Steps to reproduce:
Compile kernel with Permedia2 framebuffer enabled on E250
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
reply other threads:[~2006-06-19 22:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060619153320.49a7c736.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.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).