similar to: Debugging with Qemu

2016-01-14 23:41 UTC+01:00, Tal Lubko <tallubko at yahoo.com>: > > >> -----Original Message----- >> From: Syslinux [mailto:syslinux-bounces at zytor.com] On Behalf Of >> Celelibi via Syslinux >> Sent: Wednesday, January 13, 2016 1:34 PM >> To: Geert Stappers >> Cc: syslinux at zytor.com >> Subject: Re: [syslinux] Debugging with Qemu >>

2016-01-12 22:21 UTC+01:00, Tal Lubko via Syslinux <syslinux at zytor.com>: > On Mon, Jan 11, 2016 at 07:20:20PM -0500, Shao Miller via Syslinux wrote: >> Good day, Tal. >> >> Perhaps if you describe a little bit more about the rationale behind >> this single-file requirement, someone might be able to make an >> alternative suggestion that you haven't

From: Sylvain Gault <sylvain.gault at gmail.com> Hello there, I propose 2 patches that fix two possible stack overflows either when running a COM32 module or when loading a new config file. I didn't find a better way to do this than to use the infamous setjmp/longjmp functions to restore the stack to a previous state. This makes the logic a bit more complex, but the behavior is not

> -----Original Message----- > From: H. Peter Anvin [mailto:hpa at zytor.com] > Sent: Tuesday, January 19, 2016 9:17 PM > To: Tal Lubko; 'Celelibi' > Cc: 'For discussion of Syslinux and tftp-hpa' > Subject: Re: [syslinux] Embedding com32 modules and ldlinux.sys into > one file > > On 01/19/16 00:07, Tal Lubko via Syslinux wrote: > > > > To

> -----Original Message----- > From: H. Peter Anvin [mailto:hpa at zytor.com] > Sent: Friday, January 15, 2016 8:41 PM > To: Tal Lubko; 'Celelibi' > Cc: 'For discussion of Syslinux and tftp-hpa' > Subject: Re: [syslinux] Embedding com32 modules and ldlinux.sys into > one file > > On 01/14/2016 02:50 PM, H. Peter Anvin via Syslinux wrote: > > On

> -----Original Message----- > From: poma [mailto:pomidorabelisima at gmail.com] > Sent: Tuesday, January 19, 2016 1:30 PM > To: Tal Lubko; 'H. Peter Anvin'; 'Celelibi' > Cc: 'For discussion of Syslinux and tftp-hpa' > Subject: Re: [syslinux] Embedding com32 modules and ldlinux.sys into > one file > > On 19.01.2016 09:07, Tal Lubko via Syslinux

On Wed, Jan 20, 2016 at 2:05 AM, H. Peter Anvin via Syslinux <syslinux at zytor.com> wrote: > On January 19, 2016 12:24:50 PM PST, Tal Lubko <tallubko at yahoo.com> wrote: >> >> >>> -----Original Message----- >>> From: H. Peter Anvin [mailto:hpa at zytor.com] >>> Sent: Tuesday, January 19, 2016 9:17 PM >>> To: Tal Lubko;

From: Matt Fleming <matt.fleming at intel.com> The following patch series is available at, git://git.zytor.com/users/mfleming/syslinux.git elflink All patches are against the 'elflink' branch. This series fixes a few serious bugs and some behavioural incompatibilities with the 4.x series. Matt Fleming (19): ldlinux: Initialise 'p' before using it. ldlinux: Parse

On 01/13/16 00:13, Tal Lubko via Syslinux wrote: > > OK. I'll try that. > Any thoughts regarding the requirement to store the bootloader inside the BIOS chip? > That is fundamentally up to your BIOS. The best is to expose the bootloader in the BIOS as a (readonly) disk drive using standard BIOS or EFI interfaces. -hpa

Good day, Tal. Perhaps if you describe a little bit more about the rationale behind this single-file requirement, someone might be able to make an alternative suggestion that you haven't thought of. The BIOS- and disk-based Syslinux bootstrapping actually often has a filesystem-specific piece of code that lives in the filesystem's meta-data, as well as the primary file and COMBOOT32

Hi, This series targets automatic boot menu generation, but most of it is the Lua upgrade, because I got tired reading deprecated API docs. It's mostly a straightforward forward port of the earlier Syslinux specific changes to Lua 5.1, except that: * I chose the add a stub getenv() implementation to the COM32 API instead of #ifdefing out all the references in Lua, and * I kept oslib

On 3/31/2016 00:35, Shao Miller wrote: > Good day, Tal. > > I doubt that threads exist or that they're very warranted in a pre-OS > environment. (Co-operative threads, maybe.) > > Having typed that, there is Lua support in lua.c32 and Lua has > co-routines... But I'm wrong, from time to time: http://git.zytor.com/syslinux/syslinux.git/commit/?id=884e5778 > -

Op 2014-02-13 om 04:04 schreef Sylvain Gault: > 2014-02-13 3:20 UTC+01:00, celelibi at gmail.com <celelibi at gmail.com>: > > From: Sylvain Gault <sylvain.gault at gmail.com> > > > > It looks like git-send-email messed the headers when changing the sender. And there was no actual patch ( no unified diff output ) in that e-mail. Please rerun providing

> -----Original Message----- > From: Celelibi [mailto:celelibi at gmail.com] > Sent: Wednesday, January 13, 2016 2:22 AM > To: Tal Lubko > Cc: Shao Miller; For discussion of Syslinux and tftp-hpa > Subject: Re: [syslinux] Embedding com32 modules and ldlinux.sys into > one file > > 2016-01-12 22:21 UTC+01:00, Tal Lubko via Syslinux > <syslinux at zytor.com>:

On Thu, Nov 28, 2013 at 10:24 PM, Celelibi <celelibi at gmail.com> wrote: > 2013/11/29, Gene Cumm <gene.cumm at gmail.com>: >> On Thu, Nov 28, 2013 at 9:47 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >>> On Thu, Nov 28, 2013 at 9:34 PM, Celelibi <celelibi at gmail.com> wrote: >>>> Without an assigned source port, Transmit function assign a

On Sat, Aug 01, 2015 at 12:58:40PM +0000, Tal Lubko via Syslinux wrote: > Hi > > I would like SYSLINUX to get input from UART and act accordingly. > For example, I want to choose what rootfs to load according to the sequence received from UART. > So I'd like to know if SYSLINUX a the infrastructure for doing this Yes, Syslinux supports serial ports a.k.a. UARTS. Since the very

On Mon, Sep 28, 2015 at 06:36:24PM +0200, Celelibi via Syslinux wrote: > 2015-09-28 12:50 UTC+02:00, Gene Cumm > > On Fri, Sep 25, 2015 at 6:40 PM, Celelibi via Syslinux > >> 2015-09-25 21:27 UTC+02:00, Geert Stappers via Syslinux > >>> On Tue, Sep 15, 2015 at 05:22:40AM -0400, Gene Cumm via Syslinux wrote: > >>>> On Sep 10, 2015 1:32 AM,

Hi Some time ago I wrote this mailing list about some extra time that it takes for my system to boot and I don't know where it came from.I'm using a custom BIOS which loads at 1 second and now I've found out that it takes for the bootloader and OS an extra 1 second to load when keyboard is disconnected.I got from the BIOS engineer the following explanation and steps to take: In

On Fri, Sep 25, 2015 at 6:40 PM, Celelibi via Syslinux <syslinux at zytor.com> wrote: > 2015-09-25 21:27 UTC+02:00, Geert Stappers via Syslinux <syslinux at zytor.com>: >> On Tue, Sep 15, 2015 at 05:22:40AM -0400, Gene Cumm via Syslinux wrote: >>> On Sep 10, 2015 1:32 AM, "celelibi--- via Syslinux" <syslinux at zytor.com> >>> wrote:

From: Sylvain Gault <sylvain.gault at gmail.com> I found something suspicious while hunting another bug a while ago. The conditions for that bug to occur seems quite hard to meet, but it's still code quality improvement. See the commit message for details. Sylvain Gault (1): efi: Suspicious size reduction in emalloc efi/main.c | 4 +--- 1 file changed, 1 insertion(+), 3