From: Ralf Baechle <ralf@linux-mips.org>
To: Guo Michael <michael_e_guo@hotmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: linux_2_4 on RM7000
Date: Sun, 4 May 2003 16:31:19 +0200 [thread overview]
Message-ID: <20030504163119.A9719@linux-mips.org> (raw)
In-Reply-To: <BAY8-F66OgRGkQ6mByS0000fd73@hotmail.com>; from michael_e_guo@hotmail.com on Sun, May 04, 2003 at 10:01:16PM +0800
On Sun, May 04, 2003 at 10:01:16PM +0800, Guo Michael wrote:
> I've found the problem, I should define CONFIG_BOARD_SCACHE and
> CONFIG_RM7000_CPU_SCACHE first, right? But it still said scache_way_size is
> undefined in sc-rm7k.c and the printk on line 143 in rm7k_sc_probe need a
> little fix. After I fixed these it works.
Oh - seems like I fixed that little problem without noticing in this
source tree. Actually I tried to fix some R10000 silliness :-)
Ralf
next prev parent reply other threads:[~2003-05-04 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-04 14:01 linux_2_4 on RM7000 Guo Michael
2003-05-04 14:31 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-04 3:15 Guo Michael
2003-05-04 13:16 ` Ralf Baechle
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=20030504163119.A9719@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=michael_e_guo@hotmail.com \
/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