From: Yuri Bushmelev <jay4mail@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 08/14] zaurus-2.6.inc: switch to kexecboot and deploy kernel in /boot
Date: Sat, 31 Jan 2009 04:01:11 +0300 [thread overview]
Message-ID: <200901310401.11885.jay4mail@gmail.com> (raw)
In-Reply-To: <4c945c9a1076160cee628241443c8a27d8b5e1ca.1232244759.git.andrea.adami@gmail.com>
Hello!
> ---
> conf/machine/include/zaurus-2.6.inc | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/conf/machine/include/zaurus-2.6.inc
> b/conf/machine/include/zaurus-2.6.inc index eee7631..8adb3d5 100644
> --- a/conf/machine/include/zaurus-2.6.inc
> +++ b/conf/machine/include/zaurus-2.6.inc
> @@ -83,3 +83,7 @@ zaurus_make_installkit () {
> RDEPENDS_kernel-base = ""
>
> KERNEL_IMAGETYPE ?= "zImage"
> +
> +# uncomment this if you want to override the legacy layout
> +# and deploy kernel in /boot
> +require conf/machine/include/kexecboot.inc
IMHO, we are ready now to switch on kexecboot by default for all supported
zauruses (at least) in .dev branch.
Kexecboot is stable enough (except some issues with SD/MMC-cards) and
usable. Updating/Flashing procedure is still the same as before.
Why not? :)
Is there any other opinions? :)
BTW, I'll upload screenshots of kexecboot running in qemu in akita emulation
to my picasaweb: http://picasaweb.google.ru/yuri.bushmelev/Kexecboot
--
Yuri Bushmelev
next prev parent reply other threads:[~2009-01-31 1:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 2:24 [PATCH 00/14] [RFC] kexecboot and implementation on Zaurus Andrea Adami
2009-01-18 2:24 ` [PATCH 01/14] linux-kexecboot.inc: revert 71d21c5e379ab3f5d754a967a52240963552a71c Andrea Adami
2009-01-18 2:24 ` [PATCH 02/14] linux-kexecboot_2.6.26: revert 71dade0cdaef0220d31a309d8b6d28b99eb25b29 Andrea Adami
2009-01-18 2:24 ` [PATCH 03/14] linux-kexecboot-2.6.26: defconfig fixes Andrea Adami
2009-01-18 2:24 ` [PATCH 04/14] kexecboot: add new recipe for kexecboot-0.4 Andrea Adami
2009-01-18 2:24 ` [PATCH 05/14] kexecboot: remove kexecboot-0.3 Andrea Adami
2009-01-18 2:24 ` [PATCH 06/14] kexecboot: delete initramfs-kexecboot Andrea Adami
2009-01-18 2:24 ` [PATCH 07/14] kexecboot: use custom device table with mmc and event0 Andrea Adami
2009-01-18 2:54 ` Tom Rini
2009-01-18 8:49 ` Koen Kooi
2009-01-18 10:29 ` Andrea Adami
2009-01-18 10:47 ` Koen Kooi
2009-01-18 2:24 ` [PATCH 08/14] zaurus-2.6.inc: switch to kexecboot and deploy kernel in /boot Andrea Adami
2009-01-31 1:01 ` Yuri Bushmelev [this message]
2009-01-31 2:13 ` Graeme Gregory
2009-01-31 8:02 ` Koen Kooi
2009-01-18 2:24 ` [PATCH 09/14] linux-rp: unlock 2.6.24 and 2.6.26 for Zaurus clamshells Andrea Adami
2009-01-18 2:24 ` [PATCH 10/14] linux-rp: update defconfig for spitz Andrea Adami
2009-01-18 2:24 ` [PATCH 11/14] linux-rp: update defconfigs for c7x0 and akita Andrea Adami
2009-01-18 2:24 ` [PATCH 12/14] zaurus-2.6.inc: modules fixes Andrea Adami
2009-01-18 8:50 ` Koen Kooi
2009-01-18 10:40 ` Andrea Adami
2009-01-18 10:46 ` Koen Kooi
2009-01-18 15:29 ` Andrea Adami
2009-01-18 2:24 ` [PATCH 13/14] base-files: fix fstab for multiboot on Zaurus clamshells Andrea Adami
2009-01-18 2:24 ` [PATCH 14/14] zaurus-clamshell.inc: remove 16 bytes Sharp header Andrea Adami
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=200901310401.11885.jay4mail@gmail.com \
--to=jay4mail@gmail.com \
--cc=openembedded-devel@lists.openembedded.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