From: Darren Hart <dvhart@linux.intel.com>
To: tom.zanussi@intel.com
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH 1/6] meta-intel: add a couple common .inc files
Date: Fri, 15 Jul 2011 11:30:53 -0700 [thread overview]
Message-ID: <4E20875D.9090508@linux.intel.com> (raw)
In-Reply-To: <f69321f9d19943ec1815681e6568524387cfe5c0.1310689271.git.tom.zanussi@intel.com>
On 07/14/2011 05:55 PM, tom.zanussi@intel.com wrote:
> From: Tom Zanussi <tom.zanussi@intel.com>
>
> The meta-intel BSPs currently have a number of machine settings common
> to all - factor these out into a couple common include files.
>
> Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
> ---
> common/common-bsp-mach.inc | 13 +++++++++++++
> common/common-bsp-x.inc | 4 ++++
> 2 files changed, 17 insertions(+), 0 deletions(-)
> create mode 100644 common/common-bsp-mach.inc
> create mode 100644 common/common-bsp-x.inc
>
> diff --git a/common/common-bsp-mach.inc b/common/common-bsp-mach.inc
> new file mode 100644
> index 0000000..b020a84
> --- /dev/null
> +++ b/common/common-bsp-mach.inc
> @@ -0,0 +1,13 @@
> +MACHINE_FEATURES = "kernel26 screen keyboard pci usbhost ext2 ext3 x86 \
> + acpi serial usbgadget"
> +
> +KERNEL_IMAGETYPE = "bzImage"
> +
> +SERIAL_CONSOLE = "115200 ttyS0"
> +
> +MACHINE_EXTRA_RRECOMMENDS = "kernel-modules eee-acpi-scripts"
> +
If these are going in common .inc files we need them to be easily
overridden, shouldn't all the above be using the ?= operator?
--
Darren
> +IMAGE_FSTYPES ?= "ext3 cpio.gz"
> +
> +GLIBC_ADDONS = "nptl"
> +GLIBC_EXTRA_OECONF = "--with-tls"
> diff --git a/common/common-bsp-x.inc b/common/common-bsp-x.inc
> new file mode 100644
> index 0000000..c012efd
> --- /dev/null
> +++ b/common/common-bsp-x.inc
> @@ -0,0 +1,4 @@
> +PREFERRED_PROVIDER_virtual/libx11 ?= "libx11-trim"
> +PREFERRED_PROVIDER_virtual/libgl ?= "mesa-dri"
> +PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xf86-dri-lite"
> +PREFERRED_PROVIDER_virtual/xserver-xf86 ?= "xserver-xf86-dri-lite"
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-07-15 18:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 0:55 [PATCH 0/6] factor out some common meta-intel settings tom.zanussi
2011-07-15 0:55 ` [PATCH 1/6] meta-intel: add a couple common .inc files tom.zanussi
2011-07-15 13:23 ` Richard Purdie
2011-07-15 13:36 ` Tom Zanussi
2011-07-15 18:30 ` Darren Hart [this message]
2011-07-15 0:55 ` [PATCH 2/6] meta-sugarbay: use " tom.zanussi
2011-07-15 0:55 ` [PATCH 3/6] meta-crownbay: " tom.zanussi
2011-07-15 0:55 ` [PATCH 4/6] meta-fishriver: " tom.zanussi
2011-07-15 0:55 ` [PATCH 5/6] meta-jasperforest: " tom.zanussi
2011-07-15 0:55 ` [PATCH 6/6] meta-emenlow: " tom.zanussi
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=4E20875D.9090508@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.