From: Hauke Mehrtens <hauke@hauke-m.de>
To: ralf@linux-mips.org, john@phrozen.org
Cc: Kevin Cernekee <cernekee@gmail.com>, linux-mips@linux-mips.org
Subject: Re: [PATCH 1/2] MIPS: BCM47XX: select BOOT_RAW
Date: Wed, 21 Nov 2012 22:05:48 +0100 [thread overview]
Message-ID: <50AD422C.50005@hauke-m.de> (raw)
In-Reply-To: <CAJiQ=7B+ohpoksFcH2Z9Twwc=3SbED1hSvssfmx5-kfb4dPJnQ@mail.gmail.com>
On 09/16/2012 05:38 PM, Kevin Cernekee wrote:
> On Sun, Sep 16, 2012 at 7:48 AM, Hauke Mehrtens <hauke@hauke-m.de> wrote:
>> All the boot loaders I have seen are booting the kernel in raw mode by
>> default. CFE seams to support elf kernel images too, but the default
>
> Nitpick: "seems"
>
>> case is raw for the devices I know of. Select this option to make the
>> kernel boot on most of the devices with the default options.
>
> CONFIG_BOOT_RAW only adds about 8 bytes to the kernel image. Since
> early 2008 it's just been implemented as a single jump instruction,
> and it's harmless on platforms that don't need it.
>
> Do you think it is worthwhile to delete the Kconfig option, and enable
> BOOT_RAW behavior on all builds?
>
Ralf should I change the patch to activate BOOT_RAW on all builds like
Kevin suggested?
I just came up with the small change in these patches to make the
bcm47xx SoC boot again without any other patches.
Hauke
prev parent reply other threads:[~2012-11-21 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-16 14:48 [PATCH 1/2] MIPS: BCM47XX: select BOOT_RAW Hauke Mehrtens
2012-09-16 14:48 ` [PATCH 2/2] MIPS BCM47XX: select NO_EXCEPT_FILL Hauke Mehrtens
2012-09-16 15:38 ` [PATCH 1/2] MIPS: BCM47XX: select BOOT_RAW Kevin Cernekee
2012-11-21 21:05 ` Hauke Mehrtens [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=50AD422C.50005@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=cernekee@gmail.com \
--cc=john@phrozen.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox