From: Stuffed Crust <pizza@shaftnet.org>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Re: [patch] [radeonfb] Radeon M26 and ATOM bios support (take 4)
Date: Wed, 1 Mar 2006 15:36:11 -0500 [thread overview]
Message-ID: <20060301203611.GA14351@shaftnet.org> (raw)
In-Reply-To: <1141184789.4157.30.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1887 bytes --]
On Wed, Mar 01, 2006 at 02:46:29PM +1100, Benjamin Herrenschmidt wrote:
> Or just write a small howto and I will do the job :) I've been very busy
> lately mostly due to my newborn child, thus I didn't help more than
Congratulations (and my condolances :P) on the kid!
> that, but I'm really interested in your work. I also want to bring along
> a bunch of fixes like the memory mapping fixes I've been doing on X.org
> radeon driver recently.
I often get lockups in a radeonfb console, could that be related
to the mmap stuff you've been fixing?
> In fact, we need a way to provide the driver with the full connector
> mapping I think, in case it can't be obtained from the firmware.
I have a crude "bootstrap the connector table via ddc probing" but it
has problems with secondary heads as well, and obviously without ddc it
won't work anyway. Either the user provices a connector table or we
pray the defaults, one way or another, are sane. :)
Of course, once a non-detectable layout is known, we can add it into an
appropriate driver table.
> module option is the easy/cheap way but sucks in some ways... sysfs per
> device instance is nice but a bit "too late" unless we have a way for
> the driver to re-probe... which is a good thing to have anyway since we
> might finally deal with screen hotplug :)
MM, that would be nice.. but I don't want to think about the console
interactions required for display reconfiguration. That said, the new
code is capable of re-detecting at any time, but I'm sure the radeonfb
core has issues.
> I'll look at your stuff in more detail asap and will then let it simmer
> in -mm if I'm happy enough for at least a kernel version...
I'm about to mail out v5 of the patch.
- Solomon
--
Solomon Peachy ICQ: 1318344
Melbourne, FL
Quidquid latine dictum sit, altum viditur.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-03-01 20:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 20:44 [patch] [radeonfb] Radeon Mobility X700 (M26) and ATOM bios support Stuffed Crust
2006-01-03 23:29 ` Petr Vandrovec
2006-01-05 9:59 ` Benjamin Herrenschmidt
2006-01-05 20:13 ` Stuffed Crust
2006-02-14 21:28 ` Benjamin Herrenschmidt
2006-02-22 22:19 ` Stuffed Crust
2006-02-23 6:09 ` Stuffed Crust
2006-02-23 6:50 ` Benjamin Herrenschmidt
2006-02-23 22:36 ` [patch] [radeonfb] Radeon M26 and ATOM bios support (take 4) Stuffed Crust
2006-02-23 23:15 ` Benjamin Herrenschmidt
2006-03-01 3:33 ` Stuffed Crust
2006-03-01 3:46 ` Benjamin Herrenschmidt
2006-03-01 16:56 ` Gabor Gombas
2006-03-01 20:36 ` Stuffed Crust [this message]
2006-03-01 21:34 ` [patch] [radeonfb] Radeon M26 and ATOM bios support (take 5) Stuffed Crust
2006-03-01 21:47 ` 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=20060301203611.GA14351@shaftnet.org \
--to=pizza@shaftnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.