[no description] https://git.enea.com/cgit/linux/meta-intel.git/atom?h=1.4_M4 2013-02-18T16:23:16+00:00 2013-02-18T16:23:16+00:00 Kishore Bodke kishore.k.bodke@intel.com 2013-02-15T18:51:15+00:00 urn:sha1:150be7c8fb97ac88737f6017fdf9dd47b273bb3e Set the romley preferred kernel version to 3.4. Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> 2013-02-18T16:23:07+00:00 Kishore Bodke kishore.k.bodke@intel.com 2013-02-15T18:49:33+00:00 urn:sha1:1652742ef6e93409a6e6f4228246d905e5f7fd4c Add linux-yocto_3.4 kernel support for the romley machine. Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> 2013-02-16T16:02:00+00:00 Kishore Bodke kishore.k.bodke@intel.com 2013-02-08T22:25:11+00:00 urn:sha1:fa701ffe84741dc60c57988da84109763d336d9a Update the MAINTAINERS list after removing the cedartrail BSP from meta-intel. Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> 2013-02-16T16:01:30+00:00 Kishore Bodke kishore.k.bodke@intel.com 2013-02-08T22:18:58+00:00 urn:sha1:1d6b218a45e43441ca6299b899c4d84ec976082c Cedartrail will not be supported in the Yocto 1.4 Release. Remove it from meta-intel. Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> 2013-02-12T23:25:49+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2013-02-12T23:07:34+00:00 urn:sha1:bfa92b97a9d8e4e19d770a87b42a59c16460c1b4 RDEPENDS should be set on specific packages, not applied to everything in general (e.g. -dev, -dbg or -doc packages). This fixes up warnings in the build. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> 2013-02-12T18:17:23+00:00 Darren Hart dvhart@linux.intel.com 2013-02-12T18:17:23+00:00 urn:sha1:a75b393fd7cf6c480a92e612e1e3acc2bbf9df34 Adjust bbappend to match changes in OE-Core. Signed-off-by: Darren Hart <dvhart@linux.intel.com> 2013-02-04T16:39:06+00:00 Tom Zanussi tom.zanussi@linux.intel.com 2013-02-04T16:39:06+00:00 urn:sha1:575f93dd4ba1fb9aca8a58dc66e9066eca0a3925 Using AUTOREV turns out to cause problems with unreproducible autobuilder builds and unwanted network access. This patch removes kernel AUTOREVs and locks down SRCREVs and LINUX_VERSIONs. Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> 2013-02-01T15:52:33+00:00 Nitin A Kamble nitin.a.kamble@intel.com 2013-01-31T18:43:16+00:00 urn:sha1:706a62e662dde79bc4e7ec0f81b76890e49f4beb The recently added 1.16 version of the EMGD graphics stack also works for the FRI2 BSP. Update the BSP to use the newer EMGD version for graphics. This partly addresses: [YOCTO #3809] Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Acked-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> 2013-02-01T15:52:31+00:00 Nitin A Kamble nitin.a.kamble@intel.com 2013-01-30T06:17:30+00:00 urn:sha1:5c2feb6f9fa200bf4a7a6af3a36b78c28c078e52 Mention the use of the graphics stack based on the kernel 'gma500' driver as well as the 'modesetting' X driver for the emenlow-noemgd machine configuration. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> 2013-02-01T15:51:27+00:00 Nitin A Kamble nitin.a.kamble@intel.com 2013-01-30T05:39:51+00:00 urn:sha1:8cc90600ea083de57ebb97795e3053c72b199e7a The following was seen when booting the fri2: BUG: Bad page state in process loop0 pfn:3803 page:f6991700 count:0 mapcount:0 mapping: (null) index:0x0 page flags: 0x80400000(uncached) Modules linked in: emgd drm_kms_helper ip_tables x_tables arc4 minix cdc_acm iwlwifi led_class mac80211 cfg80211 firmware_class Pid: 448, comm: loop0 Not tainted 3.4.26-yocto-standard #1 Call Trace: [<c10cdb0f>] bad_page+0x8f/0xe0 [<c10ce0e5>] get_page_from_freelist+0x435/0x4e0 [<c10ce2c5>] __alloc_pages_nodemask+0x135/0x690 [<c10d1964>] __do_page_cache_readahead+0xe4/0x210 [<c1055a6b>] ? get_parent_ip+0xb/0x40 [<c1055a6b>] ? get_parent_ip+0xb/0x40 [<c10d1cf7>] ra_submit+0x27/0x30 [<c10d1e37>] ondemand_readahead+0x137/0x230 [<c166b061>] ? __wait_on_bit_lock+0x61/0xa0 [<c10d1fae>] page_cache_async_readahead+0x7e/0xa0 [<c112b590>] __generic_file_splice_read+0x360/0x5a0 [<c1129e90>] ? page_cache_pipe_buf_release+0x20/0x20 [<c105c56c>] ? enqueue_task_fair+0x1ac/0x620 [<c105b584>] ? check_preempt_wakeup+0x144/0x220 [<c1054b32>] ? check_preempt_curr+0x72/0x90 [<c1051f5d>] ? ttwu_stat+0x2d/0x100 [<c1055a6b>] ? get_parent_ip+0xb/0x40 [<c1055a6b>] ? get_parent_ip+0xb/0x40 [<c1670763>] ? sub_preempt_count+0x43/0xb0 [<c102573e>] ? __kunmap_atomic+0x3e/0x90 [<c13b22c0>] ? loop_make_request+0xf0/0xf0 [<c13b19b9>] ? lo_splice_actor+0x89/0xc0 [<c12c01e4>] ? security_file_permission+0x94/0xb0 [<c112b83c>] generic_file_splice_read+0x6c/0xe0 [<c112b7d0>] ? __generic_file_splice_read+0x5a0/0x5a0 [<c112a201>] vfs_splice_to+0x61/0x80 [<c112a2ca>] splice_direct_to_actor+0xaa/0x1d0 [<c13b21b0>] ? loop_thread+0x510/0x510 [<c13b1f43>] loop_thread+0x2a3/0x510 [<c13b1ca0>] ? do_lo_send_write+0xe0/0xe0 [<c1047103>] kthread+0x73/0x80 [<c1047090>] ? kthread_freezable_should_stop+0x50/0x50 [<c1673df6>] kernel_thread_helper+0x6/0x10 The fri2 has 1Gb of ram, hence the kernel sets 128Mb for the allocation of vmalloc memory. The EMGD driver needs at least 256Mb of vmalloc memory to work correctly, according to the EMGD documentation This change passes the vmalloc allocation size to the kernel via the vmalloc=256MB boot parameter. Adjusting the kernel's vmalloc allocation size fixes the kernel errors. This fixes bug: [Yocto #3810] Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Acked-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>