From: Anton Blanchard <anton@samba.org>
To: adaplas@pol.net
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
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 18:48:46 +1000 [thread overview]
Message-ID: <20040910084846.GA24408@krispykreme> (raw)
In-Reply-To: <200409101635.16803.adaplas@hotpop.com>
> Yes, that should solve the ofonly problem, with the offb in the very last of
> the Makefile, though as you said, it's a little hackish, but very simple to
> implement. This will work for ofonly though, since
> info->fix.name is not necessarily equal to "xxxfb". For instance, offb set
> "OFfb" in info->fix.name, but the boot option is "offb".
FYI Im seeing this on my POWER5 box:
Using unsupported 640x480 MTRX,G450 at e0000000, depth=8, pitch=640
cpu 0x1: Vector: 300 (Data Access) at [c000000074f37230]
pc: c0000000001e20a4: .cfb_imageblit+0x5c0/0x610
lr: c0000000001d358c: .accel_putcs+0x1f0/0x720
sp: c000000074f374b0
msr: 8000000000009032
dar: e000000080000000
dsisr: 42000000
current = 0xc000000074f310e0
paca = 0xc00000000052fa80
pid = 1, comm = swapper
enter ? for help
1:mon> t
[c000000074f375a0] c0000000001d358c .accel_putcs+0x1f0/0x720
[c000000074f37740] c000000000218600 .do_update_region+0x238/0x2ac
[c000000074f37810] c0000000002197c8 .redraw_screen+0x138/0x2b8
[c000000074f378b0] c0000000001d4724 .fbcon_init+0x5a0/0x73c
[c000000074f379a0] c000000000219b74 .visual_init+0x22c/0x2dc
[c000000074f37a50] c00000000021c0c4 .take_over_console+0x43c/0x6dc
[c000000074f37b20] c0000000001d31b4 .fbcon_takeover+0x88/0xf0
[c000000074f37bb0] c0000000001d968c .fbcon_event_notify+0x514/0xc00
[c000000074f37c70] c00000000006284c .notifier_call_chain+0x64/0x98
[c000000074f37d00] c0000000001dc87c .register_framebuffer+0x144/0x20c
[c000000074f37df0] c00000000049dcd0 .offb_init+0x528/0x838
[c000000074f37f00] c00000000000c698 .init+0x23c/0x44c
[c000000074f37f90] c000000000017f14 .kernel_thread+0x4c/0x68
We took a data miss trying to access an ioremapped area (e000000080000000).
Offb might have always been buggy but was hidden by the fact that matroxfb
used to init first.
Anton
next prev parent reply other threads:[~2004-09-10 8:48 UTC|newest]
Thread overview: 19+ 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 5:28 ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-09-10 6:00 ` Benjamin Herrenschmidt
2004-09-10 8:07 ` Geert Uytterhoeven
2004-09-10 8:35 ` Antonino A. Daplas
2004-09-11 1:04 ` Antonino A. Daplas
2004-09-10 8:35 ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-09-10 8:48 ` Anton Blanchard [this message]
2004-09-10 17:52 ` David Eger
2004-09-10 21:27 ` Antonino A. Daplas
2004-09-10 23:40 ` David Eger
2004-09-11 7:19 ` Geert Uytterhoeven
2004-09-10 21:04 ` [Linux-fbdev-devel] " 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 15:52 ` [Linux-fbdev-devel] " Andrew Morton
2004-09-20 19:38 ` 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=20040910084846.GA24408@krispykreme \
--to=anton@samba.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 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).