All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: [PATCH 1/2] meta: sys940x BSP meta data
Date: Wed, 1 Feb 2012 14:01:13 -0500	[thread overview]
Message-ID: <4F298BF9.5080807@windriver.com> (raw)
In-Reply-To: <8b67c8fb5aadfcb82de8035972efed50c67c0382.1328121321.git.dvhart@linux.intel.com>

On 12-02-01 01:45 PM, Darren Hart wrote:
> The Inforce SYS940x-ECX Developer-Ready Reference Platform features:
> o Intel Atom E6xx (0.6-1.6 GHz)
> o Up to 1GB on-board DDR2
> o Intel Platform Controller Hub EG20T
> o VGA,LVDS
> o HD Audio
> o SD Card
> o Dual SATA
> o Mini-PCIe
>
> http://www.inforcecomputing.com/SYS940X_ECX.html
>
> Signed-off-by: Darren Hart<dvhart@linux.intel.com>
> ---
>   .../bsp/sys940x/sys940x-preempt-rt.scc             |    7 +++
>   .../kernel-cache/bsp/sys940x/sys940x-standard.scc  |    6 ++
>   meta/cfg/kernel-cache/bsp/sys940x/sys940x.cfg      |   49 ++++++++++++++++++++
>   meta/cfg/kernel-cache/bsp/sys940x/sys940x.scc      |   17 +++++++
>   4 files changed, 79 insertions(+), 0 deletions(-)
>   create mode 100644 meta/cfg/kernel-cache/bsp/sys940x/sys940x-preempt-rt.scc
>   create mode 100644 meta/cfg/kernel-cache/bsp/sys940x/sys940x-standard.scc
>   create mode 100644 meta/cfg/kernel-cache/bsp/sys940x/sys940x.cfg
>   create mode 100644 meta/cfg/kernel-cache/bsp/sys940x/sys940x.scc
>
> diff --git a/meta/cfg/kernel-cache/bsp/sys940x/sys940x-preempt-rt.scc b/meta/cfg/kernel-cache/bsp/sys940x/sys940x-preempt-rt.scc
> new file mode 100644
> index 0000000..3b8f0aa
> --- /dev/null
> +++ b/meta/cfg/kernel-cache/bsp/sys940x/sys940x-preempt-rt.scc
> @@ -0,0 +1,7 @@
> +define KMACHINE sys940x
> +define KTYPE preempt-rt
> +define KARCH i386
> +
> +# no new branch required, re-use the ktypes/preempt-rt branch
> +include ktypes/preempt-rt
> +include sys940x.scc
> diff --git a/meta/cfg/kernel-cache/bsp/sys940x/sys940x-standard.scc b/meta/cfg/kernel-cache/bsp/sys940x/sys940x-standard.scc
> new file mode 100644
> index 0000000..1f0edec
> --- /dev/null
> +++ b/meta/cfg/kernel-cache/bsp/sys940x/sys940x-standard.scc
> @@ -0,0 +1,6 @@
> +define KMACHINE sys940x
> +define KTYPE standard
> +define KARCH i386
> +
> +include ktypes/standard
> +include sys940x.scc

Looks like the branch re-use issue worked itself out!

> diff --git a/meta/cfg/kernel-cache/bsp/sys940x/sys940x.cfg b/meta/cfg/kernel-cache/bsp/sys940x/sys940x.cfg
> new file mode 100644
> index 0000000..3d45fe8
> --- /dev/null
> +++ b/meta/cfg/kernel-cache/bsp/sys940x/sys940x.cfg
> @@ -0,0 +1,49 @@
> +CONFIG_X86_32=y
> +CONFIG_MATOM=y
> +CONFIG_PRINTK=y
> +
> +# Basic hardware support for the box - network, USB, PCI, sound
> +CONFIG_NETDEVICES=y
> +CONFIG_ATA=y
> +CONFIG_ATA_GENERIC=y
> +CONFIG_ATA_SFF=y
> +CONFIG_PCI=y
> +CONFIG_MMC=y
> +CONFIG_MMC_SDHCI=y
> +CONFIG_USB_SUPPORT=y
> +CONFIG_USB=y
> +CONFIG_USB_ARCH_HAS_EHCI=y
> +CONFIG_R8169=y
> +CONFIG_PATA_SCH=y
> +CONFIG_MMC_SDHCI_PCI=y
> +CONFIG_USB_EHCI_HCD=y
> +CONFIG_PCIEPORTBUS=y
> +CONFIG_NET=y
> +CONFIG_USB_UHCI_HCD=y
> +CONFIG_USB_OHCI_HCD=y
> +CONFIG_BLK_DEV_SD=y
> +CONFIG_CHR_DEV_SG=y
> +CONFIG_SOUND=y
> +CONFIG_SND=y
> +CONFIG_SND_HDA_INTEL=y
> +CONFIG_SATA_AHCI=y
> +CONFIG_AGP=y
> +CONFIG_PM=y
> +CONFIG_ACPI=y
> +CONFIG_BACKLIGHT_LCD_SUPPORT=y
> +CONFIG_BACKLIGHT_CLASS_DEVICE=y
> +CONFIG_INPUT=y
> +
> +# Make sure these are on, otherwise the bootup won't be fun
> +CONFIG_EXT3_FS=y
> +CONFIG_UNIX=y
> +CONFIG_INET=y
> +CONFIG_MODULES=y
> +CONFIG_SHMEM=y
> +CONFIG_TMPFS=y
> +CONFIG_PACKET=y
> +
> +CONFIG_RD_GZIP=y
> +
> +# Needed for booting (and using) CD images
> +CONFIG_BLK_DEV_SR=y
> diff --git a/meta/cfg/kernel-cache/bsp/sys940x/sys940x.scc b/meta/cfg/kernel-cache/bsp/sys940x/sys940x.scc
> new file mode 100644
> index 0000000..1eaebf2
> --- /dev/null
> +++ b/meta/cfg/kernel-cache/bsp/sys940x/sys940x.scc
> @@ -0,0 +1,17 @@
> +kconf hardware sys940x.cfg
> +
> +git merge yocto/emgd


Just want to confirm that emgd-1.10 is available, and this version
was explicitly chosen ?

No issues with the series though. Staging it once you confirm.

Cheers,

Bruce

> +
> +include features/eg20t/eg20t.scc
> +include features/drm-emgd/drm-emgd.scc
> +include features/dmaengine/dmaengine.scc
> +include features/serial/8250.scc
> +include features/framebuffer/vesafb.scc
> +include cfg/usb-mass-storage.scc
> +include cfg/boot-live.scc
> +include features/power/intel.scc
> +
> +include features/logbuf/size-normal.scc
> +
> +include features/latencytop/latencytop.scc
> +include features/profiling/profiling.scc



  reply	other threads:[~2012-02-01 19:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01 18:45 [PATCH 0/2][linux-yocto-3.0] sys940x BSP and boot-live consolidation Darren Hart
2012-02-01 18:45 ` [PATCH 1/2] meta: sys940x BSP meta data Darren Hart
2012-02-01 19:01   ` Bruce Ashfield [this message]
2012-02-01 22:15     ` Darren Hart
2012-02-01 19:54   ` Tom Zanussi
2012-02-01 22:13     ` Darren Hart
2012-02-01 18:45 ` [PATCH 2/2] Remove boot-live cfg duplication from BSPs Darren Hart
2012-02-01 19:55   ` Tom Zanussi
2012-02-02  2:23 ` [PATCH 0/2][linux-yocto-3.0] sys940x BSP and boot-live consolidation Bruce Ashfield
2012-02-02  3:42   ` Darren Hart
2012-02-02  5:48     ` 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=4F298BF9.5080807@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=dvhart@linux.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.