From: Andrew Finley <afinley@gis.umn.edu>
To: gentoo-mips@lists.gentoo.org
Subject: [gentoo-mips] please disregard previous question
Date: 28 Nov 2004 12:11:11 -0600 [thread overview]
Message-ID: <1101665471.27092.4.camel@populus> (raw)
In-Reply-To: <41A5443E.7060607@gentoo.org>
On Wed, 2004-11-24 at 20:32, Stephen P. Becker wrote:
> Andrew Finley wrote:
> > Thanks Steve,
> > Ok, should this kernel go in the volume header then use arcboot? If I
> > wanted to build a proper kernel, can I still use the kernel that comes from
> > emerge-source (if so what build options should be used)?
> > -andy
> >
>
> Arcboot loads from the volume header, but it doesn't boot kernels out of
> a volume header at all. Rather, it boots them from an ext2/ext3
> partition. So, you would put arcboot in the volume header, and then the
> kernel on and ext3 or ext3 partition, set up the config file, and then
> just do "boot -f arcboot" from the prom to get going. If you happened
> to do something silly like make your entire filesystem reiserfs or xfs,
> then you are out of luck with respect to arcboot.
>
> As for building your own ip32 kernel, you have to use 2.6 sources, which
> you will have to unmask yourself. You can run "make ip32_defconfig"
> inside the source tree, which will give you a base config to work from.
> You can then enter menuconfig and tweak to your liking. Or, you could
> get my config from /proc/config.gz when/if you are able to boot my
> kernel, and then tweak that. In any case, you can't use the native
> system compiler, since the kernel must be 64-bit. You will either have
> to emerge gcc-mips64 (after making sure you are using the proper
> cascaded profile), or build a mips64 cross-compiler on another machine.
>
> Steve
>
> --
> gentoo-mips@gentoo.org mailing list
>
>
--
gentoo-mips@gentoo.org mailing list
prev parent reply other threads:[~2004-11-28 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 2:16 [gentoo-mips] PANIC: Unexpected exception at boot o2 R5000 Andrew Finley
2004-11-25 2:32 ` Stephen P. Becker
2004-11-28 18:11 ` Andrew Finley [this message]
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=1101665471.27092.4.camel@populus \
--to=afinley@gis.umn.edu \
--cc=gentoo-mips@lists.gentoo.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