[meta-intel] [meta-fri2][PATCH][ 1/2] fri2: Add kernel modules to MACHINE_EXTRA_RRECOMMENDS
Signed-off-by: Andrei Gherzan and...@gherzan.ro --- meta-fri2/conf/machine/fri2-noemgd.conf | 2 +- meta-fri2/conf/machine/fri2.conf| 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/meta-fri2/conf/machine/fri2-noemgd.conf b/meta-fri2/conf/machine/fri2-noemgd.conf index 29aa601..777d02b 100644 --- a/meta-fri2/conf/machine/fri2-noemgd.conf +++ b/meta-fri2/conf/machine/fri2-noemgd.conf @@ -9,7 +9,7 @@ require conf/machine/include/tune-atom.inc require conf/machine/include/ia32-base.inc MACHINE_FEATURES += wifi 3g pcbios efi -MACHINE_EXTRA_RRECOMMENDS += linux-firmware-iwlwifi-6000g2a-5 +MACHINE_EXTRA_RRECOMMENDS += kernel-modules linux-firmware-iwlwifi-6000g2a-5 PREFERRED_PROVIDER_virtual/kernel ?= linux-yocto PREFERRED_VERSION_linux-yocto = 3.10% diff --git a/meta-fri2/conf/machine/fri2.conf b/meta-fri2/conf/machine/fri2.conf index 4ffdc4e..c074752 100644 --- a/meta-fri2/conf/machine/fri2.conf +++ b/meta-fri2/conf/machine/fri2.conf @@ -15,7 +15,7 @@ XSERVERCODECS ?= emgd-driver-video emgd-gst-plugins-va \ emgd-gst-plugins-mixvideo gst-va-intel MACHINE_FEATURES += wifi 3g pcbios efi va-impl-mixvideo -MACHINE_EXTRA_RRECOMMENDS += linux-firmware-iwlwifi-6000g2a-5 +MACHINE_EXTRA_RRECOMMENDS += kernel-modules linux-firmware-iwlwifi-6000g2a-5 PREFERRED_PROVIDER_virtual/kernel ?= linux-yocto PREFERRED_VERSION_linux-yocto = 3.10% -- 1.8.1.4 ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [meta-fri] Graphics broken?
It seems like there are some issues on current master related to graphics. emgd kernel mode loads with a kernel dump and all glx demos die with stuff like: root@fri2:~# glxdemo glxdemo[694]: segfault at 84 ip 080488a3 sp bf81cbe0 error 4 in glxdemo[8048000+1000] Obviously X fails too: ... Succeed for msvdx_pvr_init()X: symbol lookup error: /usr/lib/xorg/modules/drivers/emgd_drv.so: undefined symbol: DRI2ScreenInit VGA arbiter detected; disabling legacy VGA decoding on SDVO device GMMADR(region 0) start: 0x9000 (256M). GTTADR(region 3) start: 0xa03c (can map 256M RAM), and actual RAM base 0x3ffc. Stolen memory information base in RAM: 0x3f80 size: 7932K, calculated by (GTT RAM base) - (Stolen base) size: 8M (dvmt mode=3) Set up 1983 stolen pages starting at 0x0003f800, GTT offset 0K Anybody hitting this in the past? Maybe is a side effect of the kernel update to 3.10? I will try to investigate more on this. -- *ag* ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [fri2] A lot of garbage over serial
I have a very annoying problem with serial communication on my fri2 board. When plugging in the board the first boot gets a lot of garbage over serial (it even boots in grub without timeout or inputs user/password). After a couple of resets things get back to normal. If I unplug the board the behavior is reproducible. Any hints? Anybody seeing this too? -- *ag* ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [meta-fri] Graphics broken?
Hello, On Thu, Dec 5, 2013 at 1:17 PM, Burton, Ross ross.bur...@intel.com wrote: On 5 December 2013 10:15, Andrei Gherzan and...@gherzan.ro wrote: Succeed for msvdx_pvr_init()X: symbol lookup error: /usr/lib/xorg/modules/drivers/emgd_drv.so: undefined symbol: DRI2ScreenInit So your X server is missing the dri2 module. Can you verify that xserver-xorg-extension-dri2 is installed? Ross Right. I managed to make it work but still - there are crushes at start-up and low performance: --- CPU: 1 PID: 718 Comm: modprobe Not tainted 3.10.17-yocto-standard #2 Hardware name: Intel Corp. Fish River Island II, BIOS Tiano-TunnelCreek 11/19/2010 ec901cc0 c16872c4 ec901ce8 c1032a6f c1845140 c18395d4 0066 c102a628 c102a628 0020 0001 0001 ec901cf8 c1032b33 0009 ec901d4c c102a628 0002 c1957284 ec901d24 c1547571 Call Trace: [c16872c4] dump_stack+0x16/0x18 [c1032a6f] warn_slowpath_common+0x5f/0x80 [c102a628] ? __ioremap_caller+0x2b8/0x2e0 [c102a628] ? __ioremap_caller+0x2b8/0x2e0 [c1032b33] warn_slowpath_null+0x23/0x30 [c102a628] __ioremap_caller+0x2b8/0x2e0 [c1547571] ? pci_read+0x31/0x40 [c168b6b7] ? _raw_spin_unlock_irqrestore+0x17/0x40 [c102a66c] ioremap_nocache+0x1c/0x20 [efe2332d] ? os_map_io_to_mem_nocache+0xd/0x10 [emgd] [efe2332d] os_map_io_to_mem_nocache+0xd/0x10 [emgd] [efe054d3] full_config_tnc+0x2d3/0x390 [emgd] [efe23107] ? os_pci_find_device+0x77/0x90 [emgd] [efe048b6] config_tnc+0x16/0x560 [emgd] [c110df9f] ? kmem_cache_alloc_trace+0x9f/0x200 [efe042a8] ? igd_driver_init+0x1a8/0x210 [emgd] [efde3cdb] ? emgd_driver_load+0xdb/0x350 [emgd] [efde3cdb] ? emgd_driver_load+0xdb/0x350 [emgd] [efe04327] igd_driver_config+0x17/0x30 [emgd] [efde3d5b] emgd_driver_load+0x15b/0x350 [emgd] [efce334b] drm_get_pci_dev+0x13b/0x250 [drm] [efce3533] drm_pci_init+0xd3/0x110 [drm] [efe6c000] ? 0xefe6bfff [efe6c085] emgd_init+0x85/0x99 [emgd] [efe6c000] ? 0xefe6bfff [c10001aa] do_one_initcall+0xda/0x130 [c1058245] ? __blocking_notifier_call_chain+0x45/0x60 [c108870e] load_module+0x166e/0x1e80 [c1088f9b] SyS_init_module+0x7b/0xb0 [c168bd4c] syscall_call+0x7/0xb ---[ end trace 662b0c079ad2bc8c ]--- GMMADR(region 0) start: 0x9000 (256M). GTTADR(region 3) start: 0xa03c (can map 256M RAM), and actual RAM base 0x3ffc. Stolen memory information base in RAM: 0x3f80 size: 7932K, calculated by (GTT RAM base) - (Stolen base) size: 8M (dvmt mode=3) Set up 1983 stolen pages starting at 0x0003f800, GTT offset 0K Initializing PVR Services. [drm] Initialized emgd 1.18.3398 20131204 for :00:02.0 on minor 0 [EMGD] Driver Initialized. --- Testing xbmc on this, seems like hw accel is not working. Videos are very slow and I get this output: libva: Trying to open /usr/lib/dri/emgd_drv_video.so libva: va_openDriver() returns -1 -- *ag* ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [meta-fri] Graphics broken?
On 5 December 2013 11:31, Andrei Gherzan and...@gherzan.ro wrote: Testing xbmc on this, seems like hw accel is not working. Videos are very slow and I get this output: libva: Trying to open /usr/lib/dri/emgd_drv_video.so libva: va_openDriver() returns -1 Try using low-level tools such as vainfo, might give more useful information. Ross ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [meta-fri] Graphics broken?
On Thu, Dec 5, 2013 at 1:47 PM, Burton, Ross ross.bur...@intel.com wrote: On 5 December 2013 11:31, Andrei Gherzan and...@gherzan.ro wrote: Testing xbmc on this, seems like hw accel is not working. Videos are very slow and I get this output: libva: Trying to open /usr/lib/dri/emgd_drv_video.so libva: va_openDriver() returns -1 Try using low-level tools such as vainfo, might give more useful information. Ross Yes. I used that too. Nothing more than: libva: VA-API version 0.32.1 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/dri/emgd_drv_video.so libva: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit -- *ag* ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [meta-fri] Graphics broken?
On 5 December 2013 12:51, Andrei Gherzan and...@gherzan.ro wrote: Yes. I used that too. Nothing more than: libva: VA-API version 0.32.1 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/dri/emgd_drv_video.so libva: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit Useful. :/ Unless you fancy testing selected reverts I'm out of ideas, maybe Nitin on Darren have some thoughts. Ross ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [meta-fri2] Reboot hangs
Hello, On a master, core-image-minimal I get a very strange behavior while rebooting the board: 1. If board is booted without eth cable, reboot works as expected. 2. If board is booted with eth cable, reboot hangs at The system is going down for reboot NOW! on serial console and at Sending all preocesses the TERM signal... on console. 3. If board is booted without eth cable and I plug in the cable before reboot, the board hangs with: The system is going down for reboot NOW! root@fri2:~# irq 23: nobody cared (try booting with the irqpoll option) CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.10.17-yocto-standard #2 Hardware name: Intel Corp. Fish River Island II, BIOS Tiano-TunnelCreek 11/19/2010 ed9ef3c0 ed9ef3c0 ed809ec4 c16872c4 ed809ee4 c10a1d8a c1841650 0017 f8128522 ed9ef3c0 0017 ed809f08 c10a214d 07eef203 0017 c103a341 ed9ef3c0 ed9ef410 ed809f4c c10a00a9 ed809f50 Call Trace: [c16872c4] dump_stack+0x16/0x18 [c10a1d8a] __report_bad_irq+0x2a/0xd0 [c10a214d] note_interrupt+0xfd/0x1a0 [c103a341] ? __do_softirq+0x81/0x210 [c10a00a9] handle_irq_event_percpu+0xf9/0x230 [c13d6a5f] ? credit_entropy_bits.part.11+0xef/0x1e0 [c10a0211] handle_irq_event+0x31/0x50 [c10a2b90] handle_fasteoi_irq+0x50/0xe0 [c109f844] generic_handle_irq+0x24/0x40 [c135533e] pch_gpio_handler+0x4e/0x70 [c10a0005] handle_irq_event_percpu+0x55/0x230 [c168eadc] ? add_preempt_count+0xc/0xb0 [c168eb8c] ? sub_preempt_count+0xc/0xb0 [c168b6b7] ? _raw_spin_unlock_irqrestore+0x17/0x40 [c10a0211] handle_irq_event+0x31/0x50 [c10a2b40] ? unmask_irq+0x30/0x30 [c10a2b90] handle_fasteoi_irq+0x50/0xe0 IRQ [c169250d] ? do_IRQ+0x3d/0xb0 [c103a5d8] ? irq_exit+0x58/0x90 [c16925da] ? smp_apic_timer_interrupt+0x5a/0x8b [c16923ec] ? common_interrupt+0x2c/0x34 [c104007b] ? ftrace_raw_output_timer_class+0x1b/0x50 [c103a341] ? __do_softirq+0x81/0x210 [c103a2c0] ? __tasklet_hrtimer_trampoline+0x40/0x40 IRQ [c103a5ee] ? irq_exit+0x6e/0x90 [c16925da] ? smp_apic_timer_interrupt+0x5a/0x8b [c168c001] ? apic_timer_interrupt+0x2d/0x34 [c107007b] ? print_cfs_rq+0x4cb/0x1870 [c14d8f10] ? cpuidle_enter_state+0x40/0xc0 [c14d9033] ? cpuidle_idle_call+0xa3/0x220 [c1008a8d] ? arch_cpu_idle+0xd/0x30 [c10755d6] ? cpu_startup_entry+0x106/0x1f0 [c1676591] ? rest_init+0x71/0x80 [c1970a18] ? start_kernel+0x338/0x33f [c1970514] ? repair_env_string+0x51/0x51 [c1970358] ? i386_start_kernel+0x12e/0x131 handlers: [c1541910] azx_interrupt Disabling IRQ #23 All these three use-cases seem to be 100% reproducible on my board. Any hints on this? -- *ag* ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [meta-fri2][PATCH][ 1/2] fri2: Add kernel modules to MACHINE_EXTRA_RRECOMMENDS
Signed-off-by: Andrei Gherzan and...@gherzan.ro --- meta-fri2/conf/machine/fri2-noemgd.conf | 2 +- meta-fri2/conf/machine/fri2.conf| 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/meta-fri2/conf/machine/fri2-noemgd.conf b/meta-fri2/conf/machine/fri2-noemgd.conf index 29aa601..777d02b 100644 --- a/meta-fri2/conf/machine/fri2-noemgd.conf +++ b/meta-fri2/conf/machine/fri2-noemgd.conf @@ -9,7 +9,7 @@ require conf/machine/include/tune-atom.inc require conf/machine/include/ia32-base.inc MACHINE_FEATURES += wifi 3g pcbios efi -MACHINE_EXTRA_RRECOMMENDS += linux-firmware-iwlwifi-6000g2a-5 +MACHINE_EXTRA_RRECOMMENDS += kernel-modules linux-firmware-iwlwifi-6000g2a-5 PREFERRED_PROVIDER_virtual/kernel ?= linux-yocto PREFERRED_VERSION_linux-yocto = 3.10% diff --git a/meta-fri2/conf/machine/fri2.conf b/meta-fri2/conf/machine/fri2.conf index 4ffdc4e..c074752 100644 --- a/meta-fri2/conf/machine/fri2.conf +++ b/meta-fri2/conf/machine/fri2.conf @@ -15,7 +15,7 @@ XSERVERCODECS ?= emgd-driver-video emgd-gst-plugins-va \ emgd-gst-plugins-mixvideo gst-va-intel MACHINE_FEATURES += wifi 3g pcbios efi va-impl-mixvideo -MACHINE_EXTRA_RRECOMMENDS += linux-firmware-iwlwifi-6000g2a-5 +MACHINE_EXTRA_RRECOMMENDS += kernel-modules linux-firmware-iwlwifi-6000g2a-5 PREFERRED_PROVIDER_virtual/kernel ?= linux-yocto PREFERRED_VERSION_linux-yocto = 3.10% -- 1.8.1.4 ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [meta-fri2][PATCH][ 2/2] README: Use the symlink to the actual image when dd
Signed-off-by: Andrei Gherzan and...@gherzan.ro --- meta-fri2/README | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-fri2/README b/meta-fri2/README index be38ba4..7aac8aa 100644 --- a/meta-fri2/README +++ b/meta-fri2/README @@ -171,7 +171,7 @@ Under Linux, insert a USB flash drive. Assuming the USB flash drive takes device /dev/sdf, use dd to copy the live image to it. For example: -# dd if=core-image-sato-fri2-20101207053738.hddimg of=/dev/sdf +# dd if=core-image-sato-fri2.hddimg of=/dev/sdf # sync # eject /dev/sdf -- 1.8.1.4 ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [meta-fri] Graphics broken?
On Thu, 2013-12-05 at 12:55 +, Burton, Ross wrote: On 5 December 2013 12:51, Andrei Gherzan and...@gherzan.ro wrote: Yes. I used that too. Nothing more than: libva: VA-API version 0.32.1 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/dri/emgd_drv_video.so libva: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit Useful. :/ Unless you fancy testing selected reverts I'm out of ideas, maybe Nitin on Darren have some thoughts. All the problems you're seeing seem to be due to using master - I'd suggest going back and starting with dylan. All the graphics tests worked fine with dora, and video was tested and accelerated as well. That was all with the emgd-1.18 port to the 3.10 kernel - the OOPs you mentioned is from emgd but it's just a warning from a longstanding bug in emgd that became apparent with a change in 3.10 - we're working with the emgd team to get a correct fix there, but it shouldn't affect the graphics functionality. Tom Ross ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [meta-fri] Graphics broken?
On Thu, 2013-12-05 at 08:01 -0600, Tom Zanussi wrote: On Thu, 2013-12-05 at 12:55 +, Burton, Ross wrote: On 5 December 2013 12:51, Andrei Gherzan and...@gherzan.ro wrote: Yes. I used that too. Nothing more than: libva: VA-API version 0.32.1 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/dri/emgd_drv_video.so libva: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit Useful. :/ Unless you fancy testing selected reverts I'm out of ideas, maybe Nitin on Darren have some thoughts. All the problems you're seeing seem to be due to using master - I'd suggest going back and starting with dylan. All the graphics tests Oop, sorry, I meant dora here obviously. Tom worked fine with dora, and video was tested and accelerated as well. That was all with the emgd-1.18 port to the 3.10 kernel - the OOPs you mentioned is from emgd but it's just a warning from a longstanding bug in emgd that became apparent with a change in 3.10 - we're working with the emgd team to get a correct fix there, but it shouldn't affect the graphics functionality. Tom Ross ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [PATCH 2/5 v2] meta-mohonpeak: provide machine configuration for mohonpeak
From: Ong Boon Leong boon.leong@intel.com
Create new machines named 'mohonpeak32' and 'mohonpeak64'
for this platform.
Signed-off-by: Ong Boon Leong boon.leong@intel.com
---
meta-mohonpeak/conf/machine/mohonpeak32.conf | 22 ++
meta-mohonpeak/conf/machine/mohonpeak64.conf | 24
2 files changed, 46 insertions(+)
create mode 100644 meta-mohonpeak/conf/machine/mohonpeak32.conf
create mode 100644 meta-mohonpeak/conf/machine/mohonpeak64.conf
diff --git a/meta-mohonpeak/conf/machine/mohonpeak32.conf
b/meta-mohonpeak/conf/machine/mohonpeak32.conf
new file mode 100644
index 000..0f2ea41
--- /dev/null
+++ b/meta-mohonpeak/conf/machine/mohonpeak32.conf
@@ -0,0 +1,22 @@
+#@TYPE: Machine
+#@NAME: mohonpeak 32bit
+
+#@DESCRIPTION: Machine configuration for Mohon Peak systems
+
+PREFERRED_PROVIDER_virtual/kernel ?= linux-yocto
+PREFERRED_VERSION_linux-yocto ?= 3.4%
+
+require conf/machine/include/tune-atom.inc
+require conf/machine/include/ia32-base.inc
+require conf/machine/include/meta-intel.inc
+
+XSERVER ?= ${XSERVER_IA32_BASE} \
+ ${XSERVER_IA32_EXT} \
+ ${XSERVER_IA32_ASPEED_AST} \
+
+
+MACHINE_FEATURES += pcbios efi
+
+SYSLINUX_OPTS = serial 1 115200
+SERIAL_CONSOLE = 115200 ttyS1
+APPEND += console=ttyS1,115200 console=tty1
diff --git a/meta-mohonpeak/conf/machine/mohonpeak64.conf
b/meta-mohonpeak/conf/machine/mohonpeak64.conf
new file mode 100644
index 000..ad4d814
--- /dev/null
+++ b/meta-mohonpeak/conf/machine/mohonpeak64.conf
@@ -0,0 +1,24 @@
+#@TYPE: Machine
+#@NAME: mohonpeak 64 bit
+
+#@DESCRIPTION: Machine configuration for Mohon Peak systems
+
+PREFERRED_PROVIDER_virtual/kernel ?= linux-yocto
+PREFERRED_VERSION_linux-yocto ?= 3.4%
+
+DEFAULTTUNE ?= core2-64
+
+require conf/machine/include/tune-atom.inc
+require conf/machine/include/ia32-base.inc
+require conf/machine/include/meta-intel.inc
+
+XSERVER ?= ${XSERVER_IA32_BASE} \
+ ${XSERVER_IA32_EXT} \
+ ${XSERVER_IA32_ASPEED_AST} \
+
+
+MACHINE_FEATURES += pcbios efi
+
+SYSLINUX_OPTS = serial 1 115200
+SERIAL_CONSOLE = 115200 ttyS1
+APPEND += console=ttyS1,115200 console=tty1
--
1.7.10.4
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [PATCH 1/5 v2] meta-mohonpeak: new BSP layer for Intel Atom Processor C2000
From: Ong Boon Leong boon.leong@intel.com This layer provides support for Intel Atom Processor C2000 product line. Signed-off-by: Ong Boon Leong boon.leong@intel.com --- meta-mohonpeak/COPYING.MIT | 17 + meta-mohonpeak/README | 145 meta-mohonpeak/README.sources | 18 + meta-mohonpeak/conf/layer.conf | 12 4 files changed, 192 insertions(+) create mode 100644 meta-mohonpeak/COPYING.MIT create mode 100644 meta-mohonpeak/README create mode 100644 meta-mohonpeak/README.sources create mode 100644 meta-mohonpeak/conf/layer.conf diff --git a/meta-mohonpeak/COPYING.MIT b/meta-mohonpeak/COPYING.MIT new file mode 100644 index 000..89de354 --- /dev/null +++ b/meta-mohonpeak/COPYING.MIT @@ -0,0 +1,17 @@ +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the Software), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in +all copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN +THE SOFTWARE. diff --git a/meta-mohonpeak/README b/meta-mohonpeak/README new file mode 100644 index 000..9c95a67 --- /dev/null +++ b/meta-mohonpeak/README @@ -0,0 +1,145 @@ +This README file contains information on building the meta-mohonpeak +BSP layer, and booting the images contained in the /binary directory. +Please see the corresponding sections below for details. + +The mohonpeak platform consists of two versions: +1. 32-bit Mohon Peak +2. 64-bit Mohon Peak + +The Mohon Peak platform consists of the Intel Atom Processor C2000 +Product Family (Formerly Rangeley) + +This BSP assumes ASPEED Technology graphics card is being used. + +Further information about the platforms supported by this BSP can be +found here: + + http://www.intel.com/content/www/us/en/intelligent-systems/rangeley/ +atom-c2000-product-family-based-platforms-overview.html + +Information on all Intel® embedded platforms can be found here: + + http://www.intel.com/p/en_US/embedded/hwsw/hardware + + +Yocto Project Compatible + + +This BSP is compatible with the Yocto Project as per the requirements +listed here: + + https://www.yoctoproject.org/webform/yocto-project-compatible-registration + + +Dependencies + + +This layer depends on: + + URI: git://git.openembedded.org/bitbake + branch: master + + URI: git://git.openembedded.org/openembedded-core + layers: meta + branch: master + + URI: git://git.yoctoproject.org/meta-intel + layers: intel + branch: master + + +Patches +=== + +Please submit any patches against this BSP to the Yocto mailing list +(yo...@yoctoproject.org) and cc: the maintainer: + +Maintainer: Ong Boon Leong boon.leong@intel.com + +Please see the meta-intel/MAINTAINERS file for more details. + + +Table of Contents += + + I. Building the meta-mohonpeak BSP layer + II. Booting the images in /binary + +I. Building the meta-mohonpeak BSP layer +=== + +In order to build an image with BSP support for a given release, you +need to download the corresponding BSP tarball from the 'Board Support +Package (BSP) Downloads' page of the Yocto Project website. + +Having done that, and assuming you extracted the BSP tarball contents +at the top-level of your yocto build tree, you can build a mohonpeak +image by adding the location of the meta-mohonpeak layer to +bblayers.conf, along with the meta-intel layer itself (to access +common metadata shared between BSPs) e.g.: + + yocto/meta-intel \ + yocto/meta-intel/meta-mohonpeak \ + +To enable the 32-bit Mohon Peak layer, add the mohonpeak32 MACHINE to local.conf: + + MACHINE ?= mohonpeak32 + +To enable the 64-bit Mohon Peak layer, add the mohonpeak64 MACHINE to local.conf: + + MACHINE ?= mohonpeak64 + +You should then be able to build a mohonpeak image as such: + + $ source oe-init-build-env + $ bitbake core-image-sato + +At the end of a successful build, you should have a live image that +you can boot from a USB flash drive (see instructions on how to do +that below, in the section 'Booting the images from /binary'). + +As an alternative to downloading the BSP tarball, you can also
