From: Shinya Kuribayashi <shinya.kuribayashi@necel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] a problem about rtl8139 driver on sandpoint8245 board
Date: Mon, 01 Oct 2007 18:53:56 +0900 [thread overview]
Message-ID: <4700C3B4.70401@necel.com> (raw)
In-Reply-To: <200709301053117811863@gmail.com>
Lucas Jin wrote:
> Hi, all
>
> I am debuging RTL8139 driver for a board based on Sandpoint8245 and I have a problem.
I don't know much about Sandpoint 8245, but
> The CPU panic on line 529 in rtl8139.c. (outb(CmdReset, ioaddr + ChipCmd);)
>
> Serial port displayed:
> (
> Bad trap at PC: fffffffc, SR: 1000, vector=800
> NIP: FFFFFFFC XER: 20000000 LR: 00001288 REGS: 077ceb30 TRAP: 0800 DAR: 077CECC0
> MSR: 00001000 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 00
>
> GPR00: 00000010 077CEC20 FFFFFF1F 00000000 0000000A 00000010 FFFFFFFB 00000000
> GPR08: 00000040 81000000 00000000 FFFFFFFF 00000020 A7AC5E24 07FFD000 080D1000
> GPR16: 31380950 8E109020 05808002 55D84040 00003032 00000001 00000000 00000001
> GPR24: 00000000 077CEEA8 077CEFC8 00000005 07FF80C8 077CEF94 07FFD6D8 00000000
> Call backtrace:
> Exception in kernel pc fffffffc signal 0
> )
>
> The value of ioaddr is 0x80000000
>
> The value of _IO_BASE outb uses is defined as 0
AFAICT the drivers/rtl8139.c has at least two problems:
- First, the prospekctive target is MIPS
because it uses KSEG1ADDR macro to obtain uncached address.
- Moreover it only works under cache-{disabled,less} CPU
because it lacks of flush_cache() before transmitting data or
reclaiming rx buffers.
thanks,
Shinya Kuribayashi
next prev parent reply other threads:[~2007-10-01 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 2:53 [U-Boot-Users] a problem about rtl8139 driver on sandpoint8245 board Lucas Jin
2007-10-01 9:53 ` Shinya Kuribayashi [this message]
2007-10-01 11:07 ` [U-Boot-Users] a problem about rtl8139 driver on sandpoint8245board Lucas Jin
2007-10-01 17:40 ` [U-Boot-Users] a problem about rtl8139 driver on sandpoint8245 board Scott Wood
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=4700C3B4.70401@necel.com \
--to=shinya.kuribayashi@necel.com \
--cc=u-boot@lists.denx.de \
/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