similar to: Syslinux fwrite support

> -----Original Message----- > From: Gene Cumm [mailto:gene.cumm at gmail.com] > Sent: Tuesday, May 17, 2016 1:07 PM > To: Tal Lubko > Cc: syslinux at zytor.com > Subject: Re: [syslinux] Syslinux fwrite support > > On Tue, May 17, 2016 at 2:39 AM, Tal Lubko via Syslinux > <syslinux at zytor.com> wrote: > > Hi > > Does Syslinux support fwrite for fat

> -----Original Message----- > From: Gene Cumm [mailto:gene.cumm at gmail.com] > Sent: Saturday, May 21, 2016 4:44 PM > To: Tal Lubko > Cc: For discussion of Syslinux and tftp-hpa > Subject: Re: [syslinux] Syslinux fwrite support > > On Fri, May 20, 2016 at 11:14 PM, Tal Lubko <tallubko at yahoo.com> wrote: > > > > > >> -----Original Message-----

On Fri, May 20, 2016 at 11:14 PM, Tal Lubko <tallubko at yahoo.com> wrote: > > >> -----Original Message----- >> From: Gene Cumm [mailto:gene.cumm at gmail.com] >> Sent: Tuesday, May 17, 2016 1:07 PM >> To: Tal Lubko >> Cc: syslinux at zytor.com >> Subject: Re: [syslinux] Syslinux fwrite support >> >> On Tue, May 17, 2016 at 2:39 AM, Tal

On Tue, May 17, 2016 at 2:39 AM, Tal Lubko via Syslinux <syslinux at zytor.com> wrote: > Hi > Does Syslinux support fwrite for fat filesystem?Is it supported for other filesystem?As far as I understand the function exist but isn't fully implemented.Is that correct? > I also found this thread that says about the samehttp://www.syslinux.org/archives/2011-August/017093.html >

Hi Gene It took me some time to check all the things you've asked. Hope you still remember the case... 1) Compiling SYSLINUX with -j1 didn't help. The first error message I get is about missing header file. I'll try to play a little bit with it to make it compile. 2) The 3-character mode that the version/copyright banner displays is EDD. What determines the it? BIOS? What affect

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;

> -----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

Hi Gene Thanks again for your help. I'm using SYSLINUX 4.05 distributed by Ubuntu. For debugging I'm using SYSLINUX 6.03 because for some reason if I build SYSLINUX 4.05 from sources I get many compilation errors. SYSLINUX is installed on eMMC storage (along with Linux). I don't see the 3-character mode banner display. How can I check it? So I've added some timing prints to

Hi Gene Thanks for your reply.I'm trying to breakdown overall system boot time and to understand each component duration. My linux image is a ~10 MB bzImage file with the rootfs cpio'ed inside. I also have 2 BIOS images:- some general purpose BIOS - a custom BIOS which loads real quick I'm using TSC to measure time. I'm not sure it's the best way (I've read about CPU's

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

Hello Everyone I'd like to know what's the best way to measure syslinux functions duration.I know how to measure overall time (from syslinux start), but is there an easy way to break it down? Thanks,Tal

On Wed, Jan 13, 2016 at 01:22:17AM +0100, Celelibi wrote: > 2016-01-12 22:21 UTC+01:00, Tal Lubko: > > On Mon, Jan 11, 2016 at 07:20:20PM -0500, Shao Miller wrote: > >> > >> Yes, you can print debug-output from custom builds. > >> > > > > Regarding my other question (debugging). > > I know it is possible to use prints for debugging. > > I

Tal Lubko via Syslinux <syslinux at zytor.com> writes: > What I'm planning to do is to write COM32 image that will open UART > channel and wait for input (until timeout arrives). In case input > arrives, it will parse and validate it and act accordingly. > My solution doesn't involve user interaction. This is exactly what the Syslinux command interpreter does, if

> -----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 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

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 > -

> -----Original Message----- > From: Sergii Kolisnyk [mailto:kolkmail at gmail.com] > Sent: Tuesday, January 19, 2016 2:35 PM > To: Syslinux > Cc: Tal Lubko > Subject: Re: [syslinux] Embedding com32 modules and ldlinux.sys into > one file > > Hi, Tal, > > could you answer to 2 questions: > - what is amount of ROM you're intending to use? > (actually 8

Hello Everyone Sometime ago there was some discussion about Syslinux multifs support. I've tested it for some time using qemu and it seems to be working. Lately I've started testing it with my real hardware and for some reason it doesn't work. I don't really know how to debug Syslinux (aside from using printf), so what I've succeeded to discover with is that the

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