From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Bart Verwilst <bart@verwilst.be>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Fw: [Bugme-new] [Bug 4218] New: Radeon fb doesn't have correct resolution for lcd screen
Date: Thu, 17 Feb 2005 09:12:56 +1100 [thread overview]
Message-ID: <1108591976.5533.4.camel@gaston> (raw)
In-Reply-To: <200502160948.51781.bart@verwilst.be>
On Wed, 2005-02-16 at 09:48 +0100, Bart Verwilst wrote:
> Hi!
>
> Hm, i'm not sure wether it's radeonfb or not
>
> ----
>
> vesafb: framebuffer at 0xe0000000, mapped to 0xdc880000, using 1875k, total
> 65472k
> vesafb: mode is 800x600x16, linelength=1600, pages=67
> vesafb: protected mode interface info at c000:51a9
> vesafb: scrolling: redraw
> vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
> bootsplash 3.1.4-2004/02/19: looking for picture.... silentjpeg size 14554
> bytes, found (800x600, 14506 bytes, v3).
> Console: switching to colour frame buffer device 92x32
> fb0: VESA VGA frame buffer device
>
> ---
>
> Is radeonfb a driver for vesafb? Or are they unrelated?
>
> Could you give me some more pointers for me what i could do to test more? Or
> will enabling radeonfb debug support still be helpful?
They are unrelated, so your problem is probably not related to
radeonfb...
Ben.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
prev parent reply other threads:[~2005-02-16 22:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 21:39 Fw: [Bugme-new] [Bug 4218] New: Radeon fb doesn't have correct resolution for lcd screen Andrew Morton
2005-02-15 21:47 ` Benjamin Herrenschmidt
2005-02-16 8:48 ` Bart Verwilst
2005-02-16 19:55 ` James Simmons
2005-02-17 9:15 ` Geert Uytterhoeven
2005-02-16 22:12 ` Benjamin Herrenschmidt [this message]
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=1108591976.5533.4.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=bart@verwilst.be \
--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).