From: "" <henaldohzh@hotmail.com>
To: ralf@linux-mips.org
Cc: linux-mips@linux-mips.org
Subject: Re: Problem about porting mips kernel
Date: Tue, 26 Nov 2002 02:06:21 +0000 [thread overview]
Message-ID: <F61cMzfoV1qdiixjnzi000000e5@hotmail.com> (raw)
I think that kernel had been configured properly, because I can open the
ttyS0 device in ramdisk. It means no ramdisk problem. But I have not any
experience to fix tlb or cache bug. If you can give some more advice? Thx.
>From: Ralf Baechle <ralf@linux-mips.org>
>To: henaldohzh@hotmail.com
>CC: linux-mips@linux-mips.org
>Subject: Re: Problem about porting mips kernel
>Date: Mon, 25 Nov 2002 13:53:10 +0100
>
>On Mon, Nov 25, 2002 at 12:47:28PM +0000, henaldohzh@hotmail.com wrote:
>
> > these days, I am busy with porting mips kernel to a board with vr4131
> > core. This board has only SIU serial port, and some hw have been
modified.
> > Now, I have ported the kernel to it, and modified hw run well. But so
> > puzzling me, the execution file cann't run at all. If some one can help
me
> > or give some advices. I have been crazy for the problem. Off hat for
your
> > help. Thanks a lot.
> > btw, I use the ramdisk with busybox.
>
>In general this kind of problem means the tlb or cache code for a
particular
>platform is faulty or the kernel not configured properly.
>
> Ralf
_________________________________________________________________
免费下载 MSN Explorer: http://explorer.msn.com/lccn/
next reply other threads:[~2002-11-26 2:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 2:06 henaldohzh [this message]
2002-11-26 2:23 ` Problem about porting mips kernel jeff
2002-11-26 2:23 ` jeff
-- strict thread matches above, loose matches on Subject: below --
2002-11-28 2:42 henaldohzh
2002-12-02 19:20 ` Jun Sun
2002-11-26 2:22 henaldohzh
2002-11-25 12:47 henaldohzh
2002-11-25 12:53 ` 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=F61cMzfoV1qdiixjnzi000000e5@hotmail.com \
--to=henaldohzh@hotmail.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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.