similar to: Anyone interested in taking over the newlib-com32 effort?

Hello, I have noticed that Peter wanted to port newlib to syslinux project some time ago. It seems that the porting was not finished. Peter mentioned (http://syslinux.zytor.com/archives/2004-February/003168.html) that sucj job would require a lot of efforts. At the same time newlib is usually regarded as a "highly portable C-library". I am wondering what are the major

Does anyone on this list have experience with newlib? I'm thinking of porting newlib to the COM32 environment, rather than trying to hack my own mini-libc. I just wondered if anyone had any idea of how well that would be likely to work, and/or how well newlib works from a code size standpoint... -hpa

> -----Original Message----- > From: Gene Cumm [mailto:gene.cumm at gmail.com] > Sent: Wednesday, January 20, 2016 1:14 PM > To: Tal Lubko > Cc: H. Peter Anvin; For discussion of Syslinux and tftp-hpa > Subject: Re: [syslinux] Embedding com32 modules and ldlinux.sys into > one file > > On Wed, Jan 20, 2016 at 2:05 AM, H. Peter Anvin via Syslinux > <syslinux at

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;

Hi, Tal, could you answer to 2 questions: - what is amount of ROM you're intending to use? (actually 8 MB SPI or parallel NOR flash chip can contain some minimalist Linux distribution) - which chip do you plan to flash to, motherboard BIOS or option ROM? Also, ROMOS comes without a license, so you'll have to contact the author for commercial usage. On other hand, ROMDSK is GPLed, and you

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

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; 'Celelibi' >> Cc: 'For discussion of Syslinux and tftp-hpa' >> Subject: Re: [syslinux] Embedding com32 modules

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

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

It's time again to apply to be a mentoring organization for Google Summer of Code. This means we need to refresh the list of suggested projects at: http://syslinux.zytor.com/wiki/index.php/Google_Summer_of_Code_Ideas I'm running even more ragged than usual, so any help in this would be appreciated. I'd also like to know who'd be willing to mentor this year. -hpa -- H. Peter

Since a while, I've been contributing some code to syslinux to improve the hardware detection. Most of that code have been revamped from other project like dmidecode or the linux kernel itself. The com32 api is really a nice play for developing new features. All of that work is only available in libraries or sample code. During his fosdem presentation

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

Well, I'm porting Cygnus' newlib libc to the COM32 environment, and got it to printf() Hello, World! yesterday. The binary was 24K; 14K if I used iprintf() [printf sans floating-point support] instead of printf(). There is still a lot of work to do, obviously, but I was rather excited over having gotten it this far :) This should make it a lot easier to support all kinds of odd UI

On Mon, 25 Jan 2016 22:50:24 +0200 Tal Lubko via Syslinux <syslinux at zytor.com> wrote: > > -----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:

Google search freedos rom found two source-available implementations: https://web.archive.org/web/20050104085311/http://rayer.wz.cz/romos/romose.htm https://web.archive.org/web/20040806022202/http://linux.tu-varna.acad.bg/~lig/romdsk/ On 15 January 2016 at 13:43, Sergii Kolisnyk <kolkmail at gmail.com> wrote: > As for BIOS, there are single-sector base memory (real mode) memdisk >

On 08/09/2013 08:24 AM, Bernd Blaauw wrote: > H. Peter Anvin schreef op 9-8-2013 7:37: > >> Sorry. If you are substituting any files you should substitute them all. > > I assume it's not possible to store a copy of the LDLINUX.SYS binary at > the end or inside of either ISOLINUX.BIN or LDLINUX.C32 then? Then at > least it could be extracted, for those distributions

On 08/10/2013 08:02 AM, Pete Batard wrote: > On 2013.08.10 04:07, H. Peter Anvin wrote: >>> My application already its own version of the Syslinux installer [1], >>> and simply requires the relevant ldlinux.sys file to be provided. >> >> But that, too, is version-specific. > > I think there may be a misunderstanding here. > > Are you saying that when

As for BIOS, there are single-sector base memory (real mode) memdisk implementations, which should be ROM-compatible. I do remember Lanworks one. It's possible to make a compile option for syslinux memdisk resident code to work with base memory. On 15 January 2016 at 00:50, H. Peter Anvin via Syslinux <syslinux at zytor.com> wrote: > On 01/13/16 00:13, Tal Lubko via Syslinux wrote:

On 01/14/2016 02:50 PM, H. Peter Anvin via Syslinux wrote: > 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