linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>,
	Mathieu Malaterre <malat@debian.org>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: Rational for having CONFIG_FB_RADEON=m
Date: Tue, 14 Jun 2016 21:15:11 +1000	[thread overview]
Message-ID: <1465902911.30200.6.camel@kernel.crashing.org> (raw)
In-Reply-To: <1465874771.18900.4.camel@ellerman.id.au>

On Tue, 2016-06-14 at 13:26 +1000, Michael Ellerman wrote:
> On Mon, 2016-06-13 at 17:46 +0200, Mathieu Malaterre wrote:
> 
> > 2. Try to fix `radeonfb` so that it is able to kick offb out of the
> > way. Eg: https://lists.freedesktop.org/archives/dri-devel/2010-Augu
> > st/002907.html
> > 
> > From my understanding it would make sense to go for (2), since it
> > would allow for proper support for CONFIG_FB_RADEON=m on PowerMac.
> > In
> > this case, would such patch be accepted ?
> 
> Sounds like the right fix to me. Ben's patch above was merged, so
> it's supposed
> to kick out offb AFAICS, the fact that it can't seems like a

Make sure you have CONFIG_VT_HW_CONSOLE_BINDING=y

Ben.

> 
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev

  parent reply	other threads:[~2016-06-14 11:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13 15:46 Rational for having CONFIG_FB_RADEON=m Mathieu Malaterre
2016-06-14  3:26 ` Michael Ellerman
2016-06-14  6:05   ` Mathieu Malaterre
2016-06-14 11:15   ` Benjamin Herrenschmidt [this message]
     [not found]     ` <CA+7wUswqAh+6JLmLy=AmZJb7-mMqX0q-6fMyG_LsRECW4LwA3w@mail.gmail.com>
2016-10-01 12:12       ` Fwd: " Mathieu Malaterre

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=1465902911.30200.6.camel@kernel.crashing.org \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=malat@debian.org \
    --cc=mpe@ellerman.id.au \
    /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).