From: Manish Lachwani <m_lachwani@yahoo.com>
To: Rishabh@soc-soft.com, linux-mips@linux-mips.org
Subject: Re: Problem with HIGHMEM implementation for 32 bit mips-el port
Date: Mon, 31 Jan 2005 00:59:56 -0800 (PST) [thread overview]
Message-ID: <20050131085956.9969.qmail@web52809.mail.yahoo.com> (raw)
In-Reply-To: <4BF47D56A0DD2346A1B8D622C5C5902C472FE1@soc-mail.soc-soft.com>
please provide the detailed boot log. Also, Please use
the latest 2.4 kernel
Thanks
Manish
--- Rishabh@soc-soft.com wrote:
>
> Hi all,
>
> I am working on MIPS32 port of linux (kernel version
> 2.4.18) for R4000
> processor. While compilation was fine but the kernel
> boot up panics in
> "init".
>
> I have 128MB RAM on the system where 64MB is located
> at 0x00000000
> physical address and the other 64MB is located at
> 0x20000000.
>
> Also how is the address map for mips defined
> (highmem)?
>
> Regards,
>
> Rishabh
>
>
> The information contained in this e-mail message and
> in any annexure is
> confidential to the recipient and may contain
> privileged information. If you are not
> the intended recipient, please notify the sender and
> delete the message along with
> any annexure. You should not disclose, copy or
> otherwise use the information contained
> in the message or any annexure. Any views expressed
> in this e-mail are those of the
> individual sender except where the sender
> specifically states them to be the views of
> SoCrates Software India Pvt Ltd., Bangalore.
next prev parent reply other threads:[~2005-01-31 9:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-31 7:19 Problem with HIGHMEM implementation for 32 bit mips-el port Rishabh
2005-01-31 7:19 ` Rishabh
2005-01-31 7:35 ` Jan-Benedict Glaw
2005-01-31 8:59 ` Manish Lachwani [this message]
2005-01-31 21:14 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2005-02-01 5:29 Rishabh
2005-02-01 5:29 ` Rishabh
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=20050131085956.9969.qmail@web52809.mail.yahoo.com \
--to=m_lachwani@yahoo.com \
--cc=Rishabh@soc-soft.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