From: Ralf Baechle <ralf@linux-mips.org>
To: Vadivelan@soc-soft.com
Cc: linux-mips@linux-mips.org
Subject: Re: Init not working in 64-bit kernel
Date: Fri, 17 Mar 2006 14:12:07 +0000 [thread overview]
Message-ID: <20060317141207.GB3771@linux-mips.org> (raw)
In-Reply-To: <4BF47D56A0DD2346A1B8D622C5C5902C01524E41@soc-mail.soc-soft.com>
On Fri, Mar 17, 2006 at 07:19:08PM +0530, Vadivelan@soc-soft.com wrote:
> I've another doubt. Is it enough to set only the bits KX,SX and UX of
> the status register to work in 64-bit mode?
KX, SX and UX will be set by the kernel itself on startup.
SX doesn't actually matter because Linux doesn't use the supervisor mode.
More for completness sake - there are some slight differences between the
various 64-bit processors if attempting to execute 64-bit instructions or
addresses on a processor configured to 32-bit mode.
> Though I've used the cross compiler mips64_fp_be-gcc from MontaVista,
> the generated vmlinux image seems to boot fine even without setting the
> above bits.
> I don't know if I'm operating in 32-bit or 64-bit mode.
> But I've enabled 64-bit support in kernel configuration.
Always 64-bit mode on a 64-bit kernels - even for 32-bit software.
Always 32-bit mode on 32-bit kernels - even on 64-bit hardware.
Ralf
next prev parent reply other threads:[~2006-03-17 14:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 13:49 Init not working in 64-bit kernel Vadivelan
2006-03-17 13:49 ` Vadivelan
2006-03-17 14:12 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-11 4:20 Vadivelan
2006-04-11 4:20 ` Vadivelan
2006-03-20 12:35 Vadivelan
2006-03-20 12:35 ` Vadivelan
2006-03-20 13:14 ` Ralf Baechle
2006-03-20 14:38 ` Atsushi Nemoto
2006-03-17 10:06 Vadivelan
2006-03-17 10:06 ` Vadivelan
2006-03-17 13:18 ` 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=20060317141207.GB3771@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Vadivelan@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