linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: small radeon frame buffer issues
Date: Mon, 11 Apr 2005 09:17:51 +1000	[thread overview]
Message-ID: <1113175071.9517.514.camel@gaston> (raw)
In-Reply-To: <200504101159.36819.post@hendrik-sattler.de>


> I tried with
> video=radeonfb:1024x768-24@60
> and this resulted in no framebuffer console at all. 24bpp is a common setting 
> for X and in my opinion, the driver should just do the right thing with the 
> request (e.g. map it 32bpp if necessary).
> Or at least you could print a kernel message in the default case that the 
> selected bpp value is not supported.

Hrm... Is this the "old" or "new" radeonfb ? Also does it actually work
if you just replace 24 with 32 on the kernel command line ?

> 3.
> radeonfb is mentioned in no file in Documentation/fb/. This lets one guess on
> how to use it. Please add radeonfb to the supported list in 
> Documentation/fb/modedb.txt
> 
> Thanks.
> 
> Hendrik Sattler
> 
-- 
Benjamin Herrenschmidt <benh@kernel.crashing.org>



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

      parent reply	other threads:[~2005-04-10 23:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-10  9:59 small radeon frame buffer issues Hendrik Sattler
2005-04-10 23:17 ` Benjamin Herrenschmidt
2005-04-10 23:17 ` 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=1113175071.9517.514.camel@gaston \
    --to=benh@kernel.crashing.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).