linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hendrik Sattler <post@hendrik-sattler.de>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: small radeon frame buffer issues
Date: Sun, 10 Apr 2005 11:59:32 +0200	[thread overview]
Message-ID: <200504101159.36819.post@hendrik-sattler.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]

Hi,

I write this to you because you are also in the MAINTAINERS file for 
linux-2.6.11.
I have some issues with the radeonfb, rather minor but I want to tell you 
anyways. I am not subscribed to the list, so please CC me when answering.

1.
RADEON FRAMEBUFFER DISPLAY DRIVER
P:      Ani Joshi
M:      ajoshi@shell.unixbox.com
is unreachable. The file should be updated.

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

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

-- 
Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de
        oder über pgp.net

PingoS - Linux-User helfen Schulen: http://www.pingos.org

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2005-04-10 10:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-10  9:59 Hendrik Sattler [this message]
2005-04-10 23:17 ` small radeon frame buffer issues Benjamin Herrenschmidt
2005-04-10 23:17 ` Benjamin Herrenschmidt

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=200504101159.36819.post@hendrik-sattler.de \
    --to=post@hendrik-sattler.de \
    --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).