From: Darren Hart <dvhart@linux.intel.com>
To: tom.zanussi@intel.com
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH 5/9][KERNEL] meta/jasperforest: remove boot-live options
Date: Wed, 09 May 2012 11:14:07 -0700 [thread overview]
Message-ID: <4FAAB3EF.7000301@linux.intel.com> (raw)
In-Reply-To: <baa4fcbfd70feedeef680b214a6f4186743e3c4b.1336510044.git.tom.zanussi@intel.com>
On 05/08/2012 02:37 PM, tom.zanussi@intel.com wrote:
> From: Tom Zanussi <tom.zanussi@intel.com>
>
> The boot-live options are already included via common-pc-64 so remove
> the associated config settings from the top-level feature.
The appropriate place for these in my opinion is in BSP-standard.scc and
BSP-preempt_rt.scc. That would be the common-pc-64-standard.scc for
example in this case.
This should not be part of a machine config fragment as it is more of a
ktype policy item than it is a bsp item. I expect "standard" kernels to
be able to do live boot, but "tiny" images should not.
Note that usb-mass-storage.scc should also be added to the standard and
preempt-rt scc files per BSP. I've done the former and am currently
working through the latter with my BSPs.
--
Darren
>
> Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
> ---
> .../kernel-cache/bsp/jasperforest/jasperforest.cfg | 7 -------
> 1 files changed, 0 insertions(+), 7 deletions(-)
>
> diff --git a/meta/cfg/kernel-cache/bsp/jasperforest/jasperforest.cfg b/meta/cfg/kernel-cache/bsp/jasperforest/jasperforest.cfg
> index 0a81a19..e2310a5 100644
> --- a/meta/cfg/kernel-cache/bsp/jasperforest/jasperforest.cfg
> +++ b/meta/cfg/kernel-cache/bsp/jasperforest/jasperforest.cfg
> @@ -34,13 +34,6 @@ CONFIG_PM=y
> CONFIG_ACPI=y
> CONFIG_INPUT=y
>
> -# Needed for booting (and using) USB memory sticks
> -CONFIG_BLK_DEV_LOOP=y
> -CONFIG_NLS_CODEPAGE_437=y
> -CONFIG_NLS_ISO8859_1=y
> -
> -CONFIG_RD_GZIP=y
> -
> # NUMA support
> CONFIG_NUMA=y
> CONFIG_X86_64_ACPI_NUMA=y
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-05-09 18:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 21:37 [PATCH 0/9][KERNEL] meta-intel updates tom.zanussi
2012-05-08 21:37 ` [PATCH 1/9][KERNEL] meta/emenlow: use usb features tom.zanussi
2012-05-08 21:37 ` [PATCH 2/9][KERNEL] meta/fishriver: " tom.zanussi
2012-05-08 21:37 ` [PATCH 3/9][KERNEL] meta/jasperforest: " tom.zanussi
2012-05-08 21:37 ` [PATCH 4/9][KERNEL] meta/sugarbay: " tom.zanussi
2012-05-08 21:37 ` [PATCH 5/9][KERNEL] meta/jasperforest: remove boot-live options tom.zanussi
2012-05-09 18:14 ` Darren Hart [this message]
2012-05-09 18:50 ` Tom Zanussi
2012-05-09 19:11 ` Darren Hart
2012-05-09 19:36 ` Tom Zanussi
2012-05-08 21:37 ` [PATCH 6/9][KERNEL] meta/sugarbay: " tom.zanussi
2012-05-08 21:37 ` [PATCH 7/9][KERNEL] meta/crownbay: move smp options from recipe-space tom.zanussi
2012-05-08 21:38 ` [PATCH 8/9][KERNEL] meta/emenlow: " tom.zanussi
2012-05-08 21:38 ` [PATCH 9/9][KERNEL] meta/fishriver: " tom.zanussi
2012-05-09 4:25 ` [PATCH 0/9][KERNEL] meta-intel updates Bruce Ashfield
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=4FAAB3EF.7000301@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=tom.zanussi@intel.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.