<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 09/14/2013 03:05 AM, Martin Jansa wrote:<br>
<span style="white-space: pre;">> On Fri, Sep 13, 2013 at
07:09:00PM -0500, Jason Wessel wrote:<br>
>> A newer version of syslinux is required for an EFI
enabled isohybrid.<br>
>> This is used for the the capability to generate 3 types
of ISO images,<br>
>> all of which can be booted off a USB device or HDD if
copied with dd.<br>
>><br>
>> 1) PC BIOS only ISO<br>
>> 2) EFI only ISO<br>
>> 3) EFI + PC BIOS ISO<br>
>><br>
>> The syslinux.bbclass required a minor tweak because
ldlinux.c32 is<br>
>> dynamically loaded and needs to be in the created media
as of syslinux<br>
>> 5 and up.<br>
><br>
> Hi Jason,<br>
><br>
> can you please look at<br>
> <a class="moz-txt-link-freetext" href="https://bugzilla.yoctoproject.org/show_bug.cgi?id=3944">https://bugzilla.yoctoproject.org/show_bug.cgi?id=3944</a><br>
> ?</span><br>
<br>
<br>
I can look at fixing the defect, but there is no description of how
to use the directdisk to see the problem. Could you provide an
example?<br>
<br>
I added the directdisk to IMAGE_FSTYPES, but didn't get a
.directdisk in the deploy directory so that is not how it works.
Also I think the right solution is to simply call
syslinux_hddimg_populate() from the directdisk class vs having
copied code for the install of the syslinux specific files (that is
how 1/2 the problem occurred in the first place).<br>
<br>
Back to this particular patch, the ldlinux.c32 change does not
affect the bootdirect class. The ldlinux.c32 is only required for
isolinux and the copy is contained with in the inherited syslinux
class.<br>
<br>
Cheers,<br>
Jason.<br>
<br>
</body>
</html>