From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: "Michel Dänzer" <michel@daenzer.net>, dri-devel@lists.sourceforge.net
Subject: Re: radeon kms on ppc status
Date: Tue, 10 Aug 2010 10:17:47 +1000 [thread overview]
Message-ID: <1281399467.28245.1.camel@pasglop> (raw)
In-Reply-To: <AANLkTi=Drw_5BX2pri7B35ucyva7AxNLiEH8NEhbY4pu@mail.gmail.com>
On Mon, 2010-08-09 at 03:18 -0400, Alex Deucher wrote:
> 2010/8/9 Benjamin Herrenschmidt <benh@kernel.crashing.org>:
> > Just a quick status in case others are interested and want to help
> > as I have -very- little time.
> >
>
> Unfortunately, I don't have much spare time to dedicate to this either
> and I don't have any ppc machines.
I guessed :-) We'll see what we manage.
> > - AGP: locks up before the console shows anything useful, that's
> > going to be fun to debug without a serial port ... I'll see what I can
> > with netconsole or some firewire hack. Works fine with PCI GART.
>
> I think Michel had it working with 1x AGP.
Interesting. Michel, any idea what the problems might be ?
> > - transition from offb. If both kms and offb are built-in, the transition
> > leads to panel blooming. Note that it seems broken with nouveau on the G5 as
> > well, I suspect we are passing a crap mode when picking up from offb at boot.
> >
> > - Power Management.
> >
> > - Sleep/wakeup needs to be ported over from radeonfb (will also
> > be useful for some x86 models).
> >
>
> It would be nice to get this ported over.
Most definitely. I'm still getting my head around the KMS driver
structure.
> > - The other fancy stuff... well, we could make up profiles on powerbooks
> > I suppose, at least dynclk can be enable always and I'm sure we can make up
> > default profiles with something like half clock speed, what do you reckon ?
>
> The dynclks in the drm should work on the ppc. As for the power
> profiles, something like a half clock should work.
Ok. Here too, trying to sort out what the driver is doing for now, and
we'll move from there.
> Probably also useful to come up with some way to add backlight control
> to the macs without conflicting with the acpi backlight stuff on x86.
Yup, forgot about that one. Shouldn't be -too- hard.
Cheers,
Ben.
> Alex
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> --
> _______________________________________________
> Dri-devel mailing list
> Dri-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dri-devel
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
--
next prev parent reply other threads:[~2010-08-10 0:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 6:16 radeon kms on ppc status Benjamin Herrenschmidt
2010-08-09 7:18 ` Alex Deucher
2010-08-10 0:17 ` Benjamin Herrenschmidt [this message]
2010-08-09 9:07 ` Dave Airlie
2010-08-10 0:24 ` Benjamin Herrenschmidt
2010-08-10 0:33 ` Alex Deucher
2010-08-10 12:56 ` Michel Dänzer
2010-08-10 23:38 ` 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=1281399467.28245.1.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=michel@daenzer.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