From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Cc: Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Andrew Morton <akpm@osdl.org>
Subject: fbdev broken in current bk for PPC
Date: Fri, 10 Sep 2004 12:23:42 +1000 [thread overview]
Message-ID: <1094783022.2667.106.camel@gaston> (raw)
Recent changes upstream are breaking fbdev on pmacs.
I haven't had time to go deep into that (but I suspect Linus sees it
too on his own g5 unless he removed offb from his .config).
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.
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Cc: Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Andrew Morton <akpm@osdl.org>
Subject: fbdev broken in current bk for PPC
Date: Fri, 10 Sep 2004 12:23:42 +1000 [thread overview]
Message-ID: <1094783022.2667.106.camel@gaston> (raw)
Recent changes upstream are breaking fbdev on pmacs.
I haven't had time to go deep into that (but I suspect Linus sees it
too on his own g5 unless he removed offb from his .config).
>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.
Ben.
next reply other threads:[~2004-09-10 2:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 2:23 Benjamin Herrenschmidt [this message]
2004-09-10 2:23 ` fbdev broken in current bk for PPC 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
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=1094783022.2667.106.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.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.