From: Martin Jansa <martin.jansa@gmail.com>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: dvhart@linux.intel.com, Openembedded-core@lists.openembedded.org
Subject: Re: [v2 PATCH 4/7] syslinux.bbclass, syslinux: Update to syslinux 6.01
Date: Sat, 14 Sep 2013 15:16:45 +0200 [thread overview]
Message-ID: <20130914131645.GD30637@jama> (raw)
In-Reply-To: <5234545F.70706@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1840 bytes --]
On Sat, Sep 14, 2013 at 07:19:43AM -0500, Jason Wessel wrote:
> On 09/14/2013 03:05 AM, Martin Jansa wrote:
> > On Fri, Sep 13, 2013 at 07:09:00PM -0500, Jason Wessel wrote:
> >> A newer version of syslinux is required for an EFI enabled isohybrid.
> >> This is used for the the capability to generate 3 types of ISO images,
> >> all of which can be booted off a USB device or HDD if copied with dd.
> >>
> >> 1) PC BIOS only ISO
> >> 2) EFI only ISO
> >> 3) EFI + PC BIOS ISO
> >>
> >> The syslinux.bbclass required a minor tweak because ldlinux.c32 is
> >> dynamically loaded and needs to be in the created media as of syslinux
> >> 5 and up.
> >
> > Hi Jason,
> >
> > can you please look at
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=3944
> > ?
>
>
> 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?
>
> 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).
>
> 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.
You can reproduce it by adding vmdk to IMAGE_FSTYPES and building e.g.
qemux86 and trying to boot it in VirtualBox.
It will always enable tty0 and only way to disable it now is to enable
menu, but that doesn't work with vmdk images because of missing
vesamenu.c32
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-09-14 13:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-14 0:08 [v2 PATCH 0/7] Improved EFI boot support Jason Wessel
2013-09-14 0:08 ` [v2 PATCH 1/7] bootimage.bbclass: Move fat image creation into a function Jason Wessel
2013-09-16 17:12 ` Darren Hart
2013-09-14 0:08 ` [v2 PATCH 2/7] cdrtools-native: Update from 3.00 to 3.01a17 Jason Wessel
2013-09-16 17:21 ` Darren Hart
2013-09-14 0:08 ` [v2 PATCH 3/7] grub-efi-native: Add support for EFI ISO images Jason Wessel
2013-09-16 17:24 ` Darren Hart
2013-09-14 0:09 ` [v2 PATCH 4/7] syslinux.bbclass, syslinux: Update to syslinux 6.01 Jason Wessel
2013-09-14 8:05 ` Martin Jansa
2013-09-14 12:19 ` Jason Wessel
2013-09-14 13:16 ` Martin Jansa [this message]
2013-09-16 18:10 ` Darren Hart
2013-09-16 19:31 ` Martin Jansa
2013-09-14 0:09 ` [v2 PATCH 5/7] bootimage.bbclass, grub-efi.bbclass: Improve EFI & PCBIOS+EFI ISO support Jason Wessel
2013-09-16 17:30 ` Darren Hart
2013-09-17 11:08 ` Jason Wessel
2013-09-14 0:09 ` [v2 PATCH 6/7] grub-efi.bbclass: Add serial and graphics menu options Jason Wessel
2013-09-16 17:50 ` Darren Hart
2013-09-14 0:09 ` [v2 PATCH 7/7] bootimage.bbclass, zisofs-tools-native: add ability to compress ISO images Jason Wessel
2013-09-16 17:57 ` Darren Hart
2013-09-17 11:13 ` Jason Wessel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130914131645.GD30637@jama \
--to=martin.jansa@gmail.com \
--cc=Openembedded-core@lists.openembedded.org \
--cc=dvhart@linux.intel.com \
--cc=jason.wessel@windriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox