public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Damian Kolkowski <damian@kolkowski.no-ip.org>
Cc: Kronos <kronos@kronoz.cjb.net>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	Sergio Vergata <vergata@stud.fbi.fh-darmstadt.de>
Subject: Re: Radeonfb problem
Date: Wed, 18 Feb 2004 22:01:45 +1100	[thread overview]
Message-ID: <1077102104.20787.3.camel@gaston> (raw)
In-Reply-To: <20040218102613.ALLYOURBASEAREBELONGTOUS.A2246@kolkowski.no-ip.org>


> if I use fbset like this:
> 
> 	fbset -fb /dev/fb0 -a -depth 32 1024x768-100
> 
> my CRT monitor MAG 786FD looks like ths:
> 
> |------------|
> |     |      |
> |  a  |      |
> |     |      |
> |-----|      |
> |       b    |
> |            |
> |------------|
> 
> Where "a" is the visual screan after using fbset and "b" is my monitor.

Ok, I see what you mean. This is not a radeonfb problem at this point.

The problem is in the fbcon layer in 2.6 which doesn't adapt to
resolution changes. I have done some work to fix this but it's
not completely right yet. I'll submit something to Andrew & Linus
once I'm happy with it.

The append= you need is radeonfb=, not radeon=

I don't think the cursor issue is related at all. And I don't know
what's up with the firegl binary drivers.

Ben.


  reply	other threads:[~2004-02-18 11:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-17 19:08 Radeonfb problem Sergio Vergata
2004-02-17 20:36 ` Kronos
2004-02-17 21:11   ` Damian Kolkowski
2004-02-17 21:34     ` Kronos
2004-02-17 21:57       ` Damian Kolkowski
2004-02-17 22:22         ` Benjamin Herrenschmidt
2004-02-18  0:02           ` Sergio Vergata
2004-02-18  0:11             ` Benjamin Herrenschmidt
2004-02-18 10:26           ` Damian Kolkowski
2004-02-18 11:01             ` Benjamin Herrenschmidt [this message]
2004-02-18 10:33           ` Damian Kolkowski
2004-02-19 23:21           ` Joshua Kwan

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=1077102104.20787.3.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=damian@kolkowski.no-ip.org \
    --cc=kronos@kronoz.cjb.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vergata@stud.fbi.fh-darmstadt.de \
    /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