From: Sven Luther <luther@dpt-info.u-strasbg.fr>
To: Sven Luther <luther@dpt-info.u-strasbg.fr>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Radeon 9000 on a linux 2.4.18 kernel.
Date: Fri, 24 Jan 2003 19:31:39 +0100 [thread overview]
Message-ID: <20030124183139.GA21161@iliana> (raw)
In-Reply-To: <20030124090423.GA1690@iliana>
On Fri, Jan 24, 2003 at 10:04:23AM +0100, Sven Luther wrote:
> Hello, ...
>
> I am trying to use a Radeon 9000 on my pegasos board, and had the same
> success with it as with the matrox millenium II i used previously. Well,
> it is even worse, since radeonfb doesn't even output a bit in the boot
> log.
>
> After a bit of thinking, i realize that this is quite normal, sine i
> have to use a 2.4.18 kernel, which knows nothing of the Radeon 9000,
> since it did not exist at that time.
>
> So, my questions are :
>
> 1) is it ok to just add the Radeon 9000 pci ids and whatever to the
> 2.4.28 kernel and hope it works. (Maybe not, but then the Radeon 9000
> and the Radeon 8500 are supposed to be really similar).
Mmm, i got the info from the 2.5.x radeonfb, and added it to the 2.4.18
radeonfb (just the pll thingies and the chip detection, as i didn't see
anything else specific in the 2.5.X radeonfb.c).
but the kernel dies with :
Oops: kernel access of bad area, sig: 11
NIP: C012DD40 XER: 20000000 LR: C012DD40 SP: C07F7E90 REGS: c07f7de0 TRAP:
0300 Not tainted
MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: 00000000, DSISR: 40000000
TASK = c07f6000[1] 'swapper' Last syscall: 120
last math 00000000 last altivec 00000000
GPR00: C012DD40 C07F7E90 C07F6000 00000000 C01E1DF0 C02ADF4C C07DA299 00000003
GPR08: C01E1AC4 00000001 00000006 00000000 82002022 FFFC507C 00000034 00000014
GPR16: FFFFFFFF FDFFFDF7 FFFFDFFF FFFFFFFF 003FF000 C07DA299 00EFFF48 00EFFF4C
GPR24: 00000000 002AF8FC 40010000 C07DA288 C07EC000 C07DA000 C07EC000 C07DA000
Call backtrace:
C012DD40 C012D364 C012CD9C C0122598 C012262C C023EF64 C023E114
C0236294 C02267B0 C02267FC C0003F1C C0006AB4
the call trace corresponds to :
radeon_read_OF
radeon_get_pllinfo
radoenfb_pci_register
...
I suppose there is something wrong with the data passed from OF, but may
be wrong. I will now try to dump the content of the OF that is created
by the kernel in the begining, just to check it is ok. Any hint on how
to best do this ?
Friendly,
Sven Luther
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
next prev parent reply other threads:[~2003-01-24 18:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 9:04 Radeon 9000 on a linux 2.4.18 kernel Sven Luther
2003-01-24 9:23 ` Geert Uytterhoeven
2003-01-24 9:31 ` Sven Luther
2003-01-24 9:34 ` Geert Uytterhoeven
2003-01-24 9:39 ` Sven Luther
2003-01-24 18:31 ` Sven Luther [this message]
2003-01-24 19:09 ` Ani Joshi
2003-02-10 16:59 ` Sven Luther
2003-01-24 22:59 ` James Simmons
2003-01-25 11:40 ` Sven Luther
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=20030124183139.GA21161@iliana \
--to=luther@dpt-info.u-strasbg.fr \
--cc=linux-fbdev-devel@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).