From: Jun Sun <jsun@mvista.com>
To: henaldohzh@hotmail.com
Cc: linux-mips@linux-mips.org, jsun@mvista.com
Subject: Re: Problem about porting mips kernel
Date: Mon, 2 Dec 2002 11:20:20 -0800 [thread overview]
Message-ID: <20021202112020.I4363@mvista.com> (raw)
In-Reply-To: <F116EbjkyqU7a0xtAEH00000946@hotmail.com>; from henaldohzh@hotmail.com on Thu, Nov 28, 2002 at 02:42:22AM +0000
I have vr4131 board running just fine here for quite a while now.
A couple of basic things you may to check with:
. Make sure you have CONFIG_CPU_VR41XX set (obviously).
. Use your own init program that poke some devices other
than console. Just to make sure it is *not* the SIU
console driver problem.
Other things you want to check is the CPU revision. Make sure
it is 0x0c82, which is v2.2. Otherwise there are some nasty
cache problems you need to work around.
What is your kernel base? The latest linux-mips.org CVS tree?
Jun
On Thu, Nov 28, 2002 at 02:42:22AM +0000, henaldohzh@hotmail.com wrote:
> I carefully check the codes of TLB, but no any problem found.
> And I debug my kernel, I found that before init task jump into
> application, it means after do_execve, sp is 0. it is for
> __strnlen_user_asm function return invalid result. And I done a little
> change(only for test), the system stop after ret_from_syscall. In normal,
> it should jump to user space to execute user task.
> before ret_from_syscall, the start_thread arguments
> is:"elf_entry:0x2aaa8a00,user_sp is:0x7fff7f40,cp0_status is:0x200cc13".I
> determine that the arguments are correct. But why my application cann't run
> at all?
> > > 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 Messenger: http://messenger.msn.com/cn
>
>
next prev parent reply other threads:[~2002-12-02 19:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 2:42 Problem about porting mips kernel henaldohzh
2002-12-02 19:20 ` Jun Sun [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-26 2:22 henaldohzh
2002-11-26 2:06 henaldohzh
2002-11-26 2:23 ` jeff
2002-11-26 2:23 ` jeff
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=20021202112020.I4363@mvista.com \
--to=jsun@mvista.com \
--cc=henaldohzh@hotmail.com \
--cc=linux-mips@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox