meta: New Crystal Forest Machine Branch
cover meta: New Crystal Forest Machine Branch
From: Kishore Bodke <[email protected]>
Hi,
This is a revised patch set is for creating the new Crystal Forest Machine. Crystal Forest Machine is Sandybridge CPU with Cave Creek Chipset.
This machine is based on standard/default/common-pc-64.
Please create a new branch called standard/default/common-pc-64/crystalforest for linux-yocto-3.4 kernel and pull this new meta branch.
Thanks
Kishore.
The following changes since commit 459165c1dd61c4e843c36e6a1abeb30949a20ba7:
kconf: add 8250 Kconfig to hardware listing audit (2012-07-26 16:23:26 -0400)
are available in the git repository at:
git://git.pokylinux.org/linux-yocto-2.6.37-contrib kishore/meta-crystalforest
http://git.pokylinux.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=kishore/meta-crystalforest
Kishore Bodke (1):
meta: Crystal Forest Machine Created.
.../bsp/crystalforest/crystalforest-preempt-rt.scc | 9 ++++++ .../bsp/crystalforest/crystalforest-standard.scc | 8 +++++ .../bsp/crystalforest/crystalforest.cfg | 32 ++++++++++++++++++++ .../bsp/crystalforest/crystalforest.scc | 21 +++++++++++++ 4 files changed, 70 insertions(+) create mode 100644 meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt-rt.scc create mode 100644 meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-standard.scc create mode 100644 meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg create mode 100644 meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc
Signature · 1 line
1.7.9.5
PATCH 1/1 meta: Crystal Forest Machine Created.
From: Kishore Bodke <[email protected]>
Initial checkin for the new Crystal Forest Machine Branch. This Machine is based on Sandybridge CPU and Cave Creek Chipset.
--- .../bsp/crystalforest/crystalforest-preempt-rt.scc | 9 ++++++ .../bsp/crystalforest/crystalforest-standard.scc | 8 +++++ .../bsp/crystalforest/crystalforest.cfg | 32 ++++++++++++++++++++ .../bsp/crystalforest/crystalforest.scc | 21 +++++++++++++ 4 files changed, 70 insertions(+) create mode 100644 meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt-rt.scc create mode 100644 meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-standard.scc create mode 100644 meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg create mode 100644 meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc
meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt-rt.scc new file +9 -0
@@ -0,0 +1,9 @@ +define KMACHINE crystalforest +define KTYPE preempt-rt +define KARCH x86_64 + +# no new branch required, re-use the ktypes/preempt-rt branch +include ktypes/preempt-rt +include bsp/common-pc-64/common-pc-64.scc + +include crystalforest.scc
meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-standard.scc new file +8 -0
@@ -0,0 +1,8 @@ +define KMACHINE crystalforest +define KTYPE standard +define KARCH x86_64 + +include bsp/common-pc-64/common-pc-64-standard +branch crystalforest + +include crystalforest.scc
meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg new file +32 -0
@@ -0,0 +1,32 @@ +CONFIG_PRINTK=y + +# Basic hardware support for the box - network, 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_R8169=y +CONFIG_PATA_SCH=y +CONFIG_MMC_SDHCI_PCI=y +CONFIG_PCIEPORTBUS=y +CONFIG_NET=y +CONFIG_CHR_DEV_SG=y +CONFIG_SOUND=y +CONFIG_SND=y +CONFIG_SND_HDA_INTEL=y + +# Make sure these are on, otherwise the bootup won't be fun +CONFIG_UNIX=y +CONFIG_INET=y +CONFIG_MODULES=y +CONFIG_SHMEM=y +CONFIG_TMPFS=y +CONFIG_PACKET=y + +CONFIG_I2C=y +CONFIG_AGP=y +CONFIG_PM=y +CONFIG_INPUT=y
meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc new file +21 -0
@@ -0,0 +1,21 @@ +kconf hardware crystalforest.cfg + +include cfg/x86_64.scc +include cfg/8250.scc + +include features/power/intel.scc + +#These are required features for Intel DPDK Support +include features/uio/uio.scc +include features/hugetlb/hugetlb.scc +include features/ixgbe/ixgbe.scc +include features/igb/igb.scc + + +include features/latencytop/latencytop.scc +include features/profiling/profiling.scc +include features/usb/xhci-hcd.scc +include features/usb/ehci-hcd.scc +include features/usb/ohci-hcd.scc +include cfg/usb-mass-storage.scc +include cfg/boot-live.scc
Signature · 1 line
1.7.9.5
Re: [PATCH 1/1] [KERNEL] meta: Crystal Forest Machine Created.
Quoted 17 lines · On 08/08/2012 10:56 AM, [email protected] wrote:
From: Kishore Bodke <[email protected]>
+++ b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc
meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc new file +11
-0@@ -0,0 +1,21 @@ +kconf hardware crystalforest.cfg + +include cfg/x86_64.scc +include cfg/8250.scc + +include features/power/intel.scc + +#These are required features for Intel DPDK Support +include features/uio/uio.scc +include features/hugetlb/hugetlb.scc +include features/ixgbe/ixgbe.scc
meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc line 21
Quoted 10 lines
meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc new file +10
-0+include features/igb/igb.scc + + +include features/latencytop/latencytop.scc +include features/profiling/profiling.scc +include features/usb/xhci-hcd.scc +include features/usb/ehci-hcd.scc +include features/usb/ohci-hcd.scc +include cfg/usb-mass-storage.scc +include cfg/boot-live.scc
These last two should be in the standard and preempt-rt scc files and not in the base crystalforest.scc. The reason being, the kernel type should define policy - and whether or not we support mass storage and live boot is a matter of policy, not hardware enablement. The tiny kernel should not be required to pull in usb mass storage, fat support, etc to boot this machine.
Thanks,
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Technical Lead - Linux Kernel
Quoted 7 lines · n 08/08/2012 10:56 AM, [email protected] wrote:
From: Kishore Bodke <[email protected]>
Hi,
This is a revised patch set is for creating the new Crystal Forest Machine. Crystal Forest Machine is Sandybridge CPU with Cave Creek Chipset.
Quoted 7 lines
This machine is based on standard/default/common-pc-64.
Please create a new branch called standard/default/common-pc-64/crystalforest for linux-yocto-3.4 kernel and pull this new meta branch.
Thanks
Kishore.
Hi Kishore, please note that as these patches are for the linux-yocto sources, they should be sent to the linux-yocto mailing list:
https://lists.yoctoproject.org/listinfo/linux-yocto
This is a relatively new list, please keep it in mind for the future.
Thanks,
Darren
Quoted 23 lines
The following changes since commit
459165c1dd61c4e843c36e6a1abeb30949a20ba7:kconf: add 8250
Kconfigto hardware listing audit (2012-07-26 16:23:26 -0400)are available in the git repository at:
git://git.pokylinux.org/linux-yocto-2.6.37-contribkishore/meta-crystalforest
http://git.pokylinux.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=kishore/meta-crystalforestKishore Bodke (1):
meta: Crystal Forest Machine Created..../bsp/crystalforest/crystalforest-preempt-rt.scc | 9 ++++++ .../bsp/crystalforest/crystalforest-standard.scc | 8 +++++ .../bsp/crystalforest/crystalforest.cfg | 32 ++++++++++++++++++++ .../bsp/crystalforest/crystalforest.scc | 21 +++++++++++++ 4 files changed, 70 insertions(+) create mode 100644 meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt-rt.scc create mode 100644 meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-standard.scc create mode 100644 meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg create mode 100644 meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Technical Lead - Linux Kernel
Quoted 26 lines
-----Original Message-----
From: Darren Hart [mailto:[email protected]]
Sent: Wednesday, August 08, 2012 11:14 AM
To: Bodke, Kishore K
Cc: [email protected]; [email protected]
Subject: Re: [PATCH 0/1] [KERNEL] meta: New Crystal Forest Machine BranchQuoted 10 lines · n 08/08/2012 10:56 AM, [email protected] wrote:
From: Kishore Bodke <[email protected]>
Hi,
This is a revised patch set is for creating the new Crystal Forest Machine. Crystal Forest Machine is Sandybridge CPU with Cave Creek Chipset.
This machine is based on standard/default/common-pc-64.
Please create a new branch called standard/default/common-pc-
64/crystalforest
Quoted 4 lines
for linux-yocto-3.4 kernel and pull this new meta branch.
Thanks
Kishore.
Quoted 6 lines
Hi Kishore, please note that as these patches are for the linux-yocto sources, they should be sent to the linux-yocto mailing list:
https://lists.yoctoproject.org/listinfo/linux-yocto
This is a relatively new list, please keep it in mind for the future.
Hi Darren,
Thanks for letting me know this.
A quick question.
Do we need to send all the kernel related patches only to Linux-yocto mailing list or to both Linux-yocto and Yocto mailing list too?
Thanks
Kishore.
Quoted 31 lines · Kishore K
Quoted 31 lines
-----Original Message-----
From: Darren Hart [mailto:[email protected]]
Sent: Wednesday, August 08, 2012 11:14 AM
To: Bodke, Kishore K
Cc: [email protected]; [email protected]
Subject: Re: [PATCH 0/1] [KERNEL] meta: New Crystal Forest Machine BranchQuoted 10 lines · n 08/08/2012 10:56 AM, [email protected] wrote:
From: Kishore Bodke <[email protected]>
Hi,
This is a revised patch set is for creating the new Crystal Forest Machine. Crystal Forest Machine is Sandybridge CPU with Cave Creek Chipset.
This machine is based on standard/default/common-pc-64.
Please create a new branch called standard/default/common-pc-
64/crystalforest
Quoted 4 lines
for linux-yocto-3.4 kernel and pull this new meta branch.
Thanks
Kishore.Hi Kishore, please note that as these patches are for the linux-yocto sources, they should be sent to the linux-yocto mailing list:
Quoted 7 lines
Quoted 1 line
This is a relatively new list, please keep it in mind for the future.
Hi Darren,
Thanks for letting me know this.
A quick question.
Do we need to send all the kernel related patches only to Linux-yocto mailing list or to both Linux-yocto and Yocto mailing list too?
If the patches are against a linux-yocto*.git repository, they go to linux-yocto. If they are against the oe-core meta-data, they should go to the openembedded-core mailing list. If they are to meta-yocto, they should go to the poky mailing list (this one is rather confusing unfortunately). The only patches that should go to the "yocto" mailing list are for related projects, such as meta-intel, that are not part of oe-core, poky, linux-yocto, and do not have their own lists (such as bitbake-devel).
For the work you are doing:
Patches to meta-intel go here, to the yocto mailing list. Patches to linux-yocto*git go to the linux-yocto mailing list. Patches to poky/meta/recipes-kernel/linux/* should go to the openembedded-core mailing list.
Clear as mud? :-)
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Technical Lead - Linux Kernel