[OE-core] [PATCH] syslinux: Upgrade to 6.02

Jonathan Liu net147 at gmail.com
Sun Nov 10 00:31:05 UTC 2013


On 10/11/2013 1:55 AM, Khem Raj wrote:
> On Fri, Nov 8, 2013 at 9:36 PM, Jonathan Liu <net147 at gmail.com> wrote:
>> On 4/11/2013 7:39 AM, Khem Raj wrote:
>>> Signed-off-by: Khem Raj <raj.khem at gmail.com>
>>> ---
>>>    .../recipes-devtools/syslinux/{syslinux_6.01.bb => syslinux_6.02.bb} | 5
>>> ++---
>>>    1 file changed, 2 insertions(+), 3 deletions(-)
>>>    rename meta/recipes-devtools/syslinux/{syslinux_6.01.bb =>
>>> syslinux_6.02.bb} (94%)
>>>
>>> diff --git a/meta/recipes-devtools/syslinux/syslinux_6.01.bb
>>> b/meta/recipes-devtools/syslinux/syslinux_6.02.bb
>>> similarity index 94%
>>> rename from meta/recipes-devtools/syslinux/syslinux_6.01.bb
>>> rename to meta/recipes-devtools/syslinux/syslinux_6.02.bb
>>> index 4438ea8..b4ba0ad 100644
>>> --- a/meta/recipes-devtools/syslinux/syslinux_6.01.bb
>>> +++ b/meta/recipes-devtools/syslinux/syslinux_6.02.bb
>>> @@ -9,9 +9,8 @@ LIC_FILES_CHKSUM =
>>> "file://COPYING;md5=0636e73ff0215e8d672dc4c32c317bb3 \
>>>    DEPENDS = "nasm-native util-linux"
>>>      SRC_URI =
>>> "${KERNELORG_MIRROR}/linux/utils/boot/syslinux/6.xx/syslinux-${PV}.tar.bz2"
>>> -
>>> -SRC_URI[md5sum] = "6945ee89e29119d459baed4937bbc534"
>>> -SRC_URI[sha256sum] =
>>> "83a04cf81e6a46b80ee5a321926eea095af3498b04317e3674b46c125c7a5b43"
>>> +SRC_URI[md5sum] = "5410b1c2614cc8375bfc92fe308ca5c8"
>>> +SRC_URI[sha256sum] =
>>> "16027cbc1a7d18a48f3d26fbea771896d892cb43860b8d2f596baef7f2789b6e"
>>>      COMPATIBLE_HOST = '(x86_64|i.86).*-(linux|freebsd.*)'
>>>    # Don't let the sanity checker trip on the 32 bit real mode BIOS
>>> binaries
>> Note that syslinux 6.02 has a known bug which corrupts the superblock when
>> used on BTRFS volumes due to ldlinux.sys exceeding 64000 bytes.
>> It fixes booting memtest86+ with pxelinux though (see
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=5501).
>
> so it fixes one and regresses 1 and then for third one we can backport a patch
> is btrfs volume issue a blocker ? if not I would say a v2 with
> http://git.kernel.org/cgit/boot/syslinux/syslinux.git/commit/?h=firmware&id=4ac63b5ac412d54462e292daf65a309775bc0448
> applied would be good.
> atleast it will give us more testing and time to find issues before
> 6.03 comes out
>
>> Regards,
>> Jonathan
I don't know of anyone using BTRFS volumes in production. It's not a 
blocker for me at least.

Regards,
Jonathan



More information about the Openembedded-core mailing list