<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/scripts, branch uninative-2.2</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=uninative-2.2</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=uninative-2.2'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2018-07-25T15:46:56+00:00</updated>
<entry>
<title>Revert "relocate_sdk.py: remove hardcoded SDK path"</title>
<updated>2018-07-25T15:46:56+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2018-07-25T15:45:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=d8762a1ea74bbd9a9ee1510fe5ffa8db1b7d0d61'/>
<id>urn:sha1:d8762a1ea74bbd9a9ee1510fe5ffa8db1b7d0d61</id>
<content type='text'>
This reverts commit 6671a4d980c8bef8f402780a308f6c43a25044aa.

This breaks uninative tarball since the call of relocate_sdk.py from uninative.bbclass
wasn't updated to account for this change. It isn't clear what value that code could
pass in and this isn't simple to fix so revert until a better fix can be found
that doesn't break uninative.

(From OE-Core rev: b247392b4ced57cfe694656032f6a6723740a9e8)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>scripts/contrib/mkefidisk.sh: Remove</title>
<updated>2018-07-24T10:52:27+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2018-07-20T08:17:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=4c67ffef2e50b6e0be1530ea332e69afa025574c'/>
<id>urn:sha1:4c67ffef2e50b6e0be1530ea332e69afa025574c</id>
<content type='text'>
This has been printing a deprecation warning for a while, now remove it
in favour of wic's efi functionality.

(From OE-Core rev: 1f279cf1ad2f0a20495780b210a987416650f40f)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>relocate_sdk.py: remove hardcoded SDK path</title>
<updated>2018-07-24T10:52:27+00:00</updated>
<author>
<name>Ruslan Bilovol</name>
<email>rbilovol@cisco.com</email>
</author>
<published>2017-11-22T11:20:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=bf5b43495a99bb8d002e02c688746e78c9430c21'/>
<id>urn:sha1:bf5b43495a99bb8d002e02c688746e78c9430c21</id>
<content type='text'>
This patch removes hardcodes added to relocate_sdk.py
during SDK build, making it flexible and reusable.
Now default SDK path is passed to the script as
parameter rather then harcoded inside it.

This allows to reuse this script for multiple
relocations, and adds possibility to relocate
SDK multiple times

(From OE-Core rev: 6671a4d980c8bef8f402780a308f6c43a25044aa)

Signed-off-by: Ruslan Bilovol &lt;rbilovol@cisco.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>oe-find-native-sysroot: drop message if pseudo is not found</title>
<updated>2018-07-24T10:52:26+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2018-07-17T12:34:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=2019f782604a554412cc2ceb0f46760a83984487'/>
<id>urn:sha1:2019f782604a554412cc2ceb0f46760a83984487</id>
<content type='text'>
pseudo won't always be in the native sysroot for a recipe, so we
shouldn't be complaining if it isn't there.

(From OE-Core rev: 11efc94742088ec6fbf2a86000e98286b0b529ef)

Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>oe-run-native: ensure arguments get quoted</title>
<updated>2018-07-24T10:52:26+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2018-07-17T12:34:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=9c20b0df5f4b962d1a5212d3a2fe815fee8fee4e'/>
<id>urn:sha1:9c20b0df5f4b962d1a5212d3a2fe815fee8fee4e</id>
<content type='text'>
If you pass quoted arguments to oe-run-native, they need to be passed
as-is to the underlying tool. Putting quotes around $@ ensures each
argument is quoted individually.

(From OE-Core rev: a8758653500a2458cd91bf1aa5eb666ad2b45df4)

Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>wic/engine: use up all free space when expanding partitions</title>
<updated>2018-07-18T09:18:42+00:00</updated>
<author>
<name>Anuj Mittal</name>
<email>anuj.mittal@intel.com</email>
</author>
<published>2018-07-12T02:05:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=bf7ed1d046b0636116ab52ef6ea0e8adb9ef55a8'/>
<id>urn:sha1:bf7ed1d046b0636116ab52ef6ea0e8adb9ef55a8</id>
<content type='text'>
Currently we just divide up the free space by the number of partitions
that need to be re-sized. This leads to problems when a user has
explicitly specified a subset of partitions (but not all) that need
to re-sized along with the sizes. As an example, for an image with 3
partitions, if we use:

wic write image.wic /dev/sdb --expand 1:10G

This would lead to paritions 2 and 3 each being re-sized to one thirds
of the free space instead of half.

Change the behavior to use up all the free space.

(From OE-Core rev: a88f1b5d88dbc5fb28be24b9787d73b9e0cdf183)

Signed-off-by: Anuj Mittal &lt;anuj.mittal@intel.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>wic/engine: fix errors when expanding partitions</title>
<updated>2018-07-18T09:18:42+00:00</updated>
<author>
<name>Anuj Mittal</name>
<email>anuj.mittal@intel.com</email>
</author>
<published>2018-07-12T02:05:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=82756dcac05f7494805c339bb7ffe193afe536db'/>
<id>urn:sha1:82756dcac05f7494805c339bb7ffe193afe536db</id>
<content type='text'>
The UEFI spec implies that GPT partitions should be assumed to be on a 2048
sector boundary (for a 512 byte sector) and the current logic just
divides the free sectors available by the number of partitions that need
re-sizing, which may or may not align and the final result might
overshoot the limits imposed after alignment.

Since we are expanding already aligned partitions, just divide up the
free space in multiples of 2048. Also use the exec_cmd wrapper instead
of the subprocess call directly.

Fixes [YOCTO #12840]

(From OE-Core rev: 5eef63f5afdfbab8e30748cb1bf42bf2e6524759)

Signed-off-by: Anuj Mittal &lt;anuj.mittal@intel.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>scripts/runqemu: fix qemumips qemumips64 memory detection kernel panic</title>
<updated>2018-07-10T16:33:00+00:00</updated>
<author>
<name>He Zhe</name>
<email>zhe.he@windriver.com</email>
</author>
<published>2018-07-09T03:14:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=c68e4c6e3eb612bb7afd9d7f1e9a6dc295d44346'/>
<id>urn:sha1:c68e4c6e3eb612bb7afd9d7f1e9a6dc295d44346</id>
<content type='text'>
$ runqemu qemumips64 core-image-minimal nographic qemuparams="-m 512"
...
[    0.000000] Call Trace:
[    0.000000] [&lt;ffffffff801268c0&gt;] clear_page+0x0/0x128
[    0.000000] [&lt;ffffffff80238158&gt;] get_page_from_freelist+0xab8/0xc00
[    0.000000] [&lt;ffffffff80238964&gt;] __alloc_pages_nodemask+0xdc/0xf68
[    0.000000] [&lt;ffffffff80239808&gt;] __get_free_pages+0x18/0x70
[    0.000000] [&lt;ffffffff80122a4c&gt;] setup_zero_pages+0x1c/0xb8
[    0.000000] [&lt;ffffffff80c7c998&gt;] mem_init+0x54/0xa0
[    0.000000] [&lt;ffffffff80c74904&gt;] start_kernel+0x204/0x4d8
[    0.000000] [&lt;ffffffff8091dfb0&gt;] kernel_entry+0x0/0x40
[    0.000000] Code: 02002025  1000f8d9  8e634d7c &lt;34860f80&gt; cc9e0000
cc9e0020  cc9e0040  cc9e0060  cc9e0080
[    0.000000]
[    0.000000] ---[ end trace 0000000000000000 ]---
[    0.000000] Kernel panic - not syncing: Attempted to kill the idle task!
[    0.000000] ---[ end Kernel panic - not syncing: Attempted to kill the idle task!
...

OE uses qemumips to simulate a Malta board by default.

As upstream qemu introduced:
https://git.qemu.org/?p=qemu.git;a=commit;h=94c2b6aff43cdfcfdfb552773a6b6b973a72ef0b

The Malta board can support up to 2GiB of RAM which should
be able to boot a Linux kernel built with CONFIG_HIGHMEM
enabled and passing "-m 2048" to QEMU and appending the
following kernel parameters:
...
mem=256M@0x0 mem=256M@0x90000000 mem=1536M@0x20000000
...

But the following commit in kernel broke above mem=X@Y setting
which added the memory as reserved memory area.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=73fbc1eba7ffa3bf0ad12486232a8a1edb4e4411
...
commit 73fbc1eba7ffa3bf0ad12486232a8a1edb4e4411
Author: Marcin Nowakowski &lt;marcin.nowakowski@imgtec.com&gt;
Date:   Wed Nov 23 14:43:49 2016 +0100

    MIPS: fix mem=X@Y commandline processing
...

So remove `mem=*' to disable user-defined physical RAM map
which let kernel itself caculates memory ranges.

Author: Hongxu Jia &lt;hongxu.jia@windriver.com&gt;
[ Merge the two fixes for qemumips32 and qemumips64 into one patch,
  and make it support all mips cases ]
(From OE-Core rev: 0220cb34a91658ecc3782ec1a4700dcb5ece37d8)

Signed-off-by: He Zhe &lt;zhe.he@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>send-error-report: Fix test for name &gt; 50 chars</title>
<updated>2018-07-04T11:19:13+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2018-07-04T09:40:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f2c04b450fcbd5e9aa4d18ba047fa70f6becdb9c'/>
<id>urn:sha1:f2c04b450fcbd5e9aa4d18ba047fa70f6becdb9c</id>
<content type='text'>
A name &gt; 50 chars causes a 500 internal server error and should be warned
to the user but the code to do so currently doesn't work. Fix the logic.

(From OE-Core rev: 844f8d46f522a994dbff00245c4ffb07452577a8)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>send-error-report: Fix dubious error reporting</title>
<updated>2018-07-04T11:19:13+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2018-07-04T09:35:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=83b01091499e047b004f16f4716f098741e66634'/>
<id>urn:sha1:83b01091499e047b004f16f4716f098741e66634</id>
<content type='text'>
Currently this code prints things like:

ERROR: OK

which is unhelpful at best. After this change it would print:

ERROR: HTTP Error 500

which at least gives us something to work on.

(From OE-Core rev: 06079240e4eb0a3e1f528f6c8d6f3ea20754afee)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
