All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Eger <eger@havoc.gtf.org>
To: adaplas@pol.net
Cc: linux-fbdev-devel@lists.sourceforge.net,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [Linux-fbdev-devel] fbdev broken in current bk for PPC
Date: Fri, 10 Sep 2004 19:40:44 -0400	[thread overview]
Message-ID: <20040910234044.GA30180@havoc.gtf.org> (raw)
In-Reply-To: <200409110527.05516.adaplas@hotpop.com>

On Sat, Sep 11, 2004 at 05:27:05AM +0800, Antonino A. Daplas wrote:
> On Saturday 11 September 2004 01:52, David Eger wrote:
> > On Fri, Sep 10, 2004 at 01:28:57PM +0800, Antonino A. Daplas wrote:
> > > On Friday 10 September 2004 10:23, Benjamin Herrenschmidt wrote:
> > > > Recent changes upstream are breaking fbdev on pmacs.
> > > >
> > > > From what I see, it seems that offb is kicking in by default, reserves
> > > > the mmio regions, and then whatever chip driver loads can't access
> > > > them.
> > > >
> > > > offb is supposed to be a "fallback" driver in case no fbdev is taking
> > > > over, it should also be "forced" in with video=ofonly kernel command
> > > > line. This logic has been broken.
> >
> > I *hope* this is what I'm seeing with recent kernels, though I
> > have my doubts....  What I *do* know is that with recent bk snapshots
> > (post bk-1.2115) I have the following:  radeonfb seems to load, but when I
> > try to load X, my y-resolution seems to be half of what it ought to be...
> 
> X-fbdev, or X + native radeon driver?  Do still get a framebuffer console?
> Any other fb apps you have that's also broken?

Hold my tongue: BenH's latest patch (already in mainline) fixes it for me.

-David

  reply	other threads:[~2004-09-10 23:40 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-10  2:23 fbdev broken in current bk for PPC Benjamin Herrenschmidt
2004-09-10  2:23 ` Benjamin Herrenschmidt
2004-09-10  5:28 ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-09-10  5:28   ` Antonino A. Daplas
2004-09-10  6:00   ` Benjamin Herrenschmidt
2004-09-10  6:00     ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2004-09-10  8:07     ` Geert Uytterhoeven
2004-09-10  8:07       ` [Linux-fbdev-devel] " Geert Uytterhoeven
2004-09-10  8:35       ` Antonino A. Daplas
2004-09-10  8:35         ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-09-11  1:04         ` Antonino A. Daplas
2004-09-11  1:04           ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-09-10  8:35     ` Antonino A. Daplas
2004-09-10  8:48       ` Anton Blanchard
2004-09-10 17:52   ` David Eger
2004-09-10 21:27     ` Antonino A. Daplas
2004-09-10 21:27       ` Antonino A. Daplas
2004-09-10 23:40       ` David Eger [this message]
2004-09-11  7:19   ` Geert Uytterhoeven
2004-09-11  7:19     ` [Linux-fbdev-devel] " Geert Uytterhoeven
2004-09-10 21:04 ` Antonino A. Daplas
2004-09-11  1:00   ` Benjamin Herrenschmidt
2004-09-13  1:52   ` Joseph Fannin
2004-09-20  9:27   ` Benjamin Herrenschmidt
2004-09-20  9:27     ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2004-09-20 15:52     ` Andrew Morton
2004-09-20 19:38       ` Antonino A. Daplas
2004-09-20 19:59         ` Antonino A. Daplas
2004-09-20 19:59           ` Antonino A. Daplas

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=20040910234044.GA30180@havoc.gtf.org \
    --to=eger@havoc.gtf.org \
    --cc=adaplas@pol.net \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /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.