similar to: unify core printf()/dprintf(): thoughts?

If I understand correctly, the Linux kernel has a function printk() designed for most printing functions where a string prefix determines where the message is seen. Would something like this be useful in Syslinux? As I see it, there's essentially 3 separate printing methods with an additional variation. Goals: - To keep data size smaller, avoid 2+ identical static strings (akin to {

From: Raphael S. Carvalho <raphael.scarv at gmail.com> MULTIFS SYNTAX: (hd[disk number]:[partition number])/path/to/file The meaning of this_fs was changed to improve the flexibility of the support. Now, this_fs means the file system being currently used. root_fs was created to save the context of the main file system (where ldlinux.sys lives in). get_fs_info is a function pointer that

This patch adds support for serial output functions. It may be useful for debugging purposes since you can separate ordinary outputs from debugging dumps. Just add "serial.h", and use either serial_print or serial_puts as you would use printf and puts respectivelly. For QEMU, you only need to specify the option -serial stdio. If you use another VM, find how you can redirect the serial

> On Fri, Feb 6, 2015 at 6:55 AM, Martin Str|mberg <ams at ludd.ltu.se> wrote: > > On Sun, Jan 25, 2015 at 06:13:13PM -0200, Raphael S Carvalho wrote: > >> On Sat, Nov 22, 2014 at 10:39 AM, Martin Str|mberg <ams at ludd.ltu.se> wrote: > >> > Hello. > >> > > >> > Use the z size specifier to printf-ing size_t variables to get rid of

From: Raphael S. Carvalho <raphael.scarv at gmail.com> v2: Extract ADV_SIZE automatically from libinstaller/setadv.h. Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds the limit. ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary. Thus, the size of ldlinux.sys can be at most: 65536 - 2 * ADV_SIZE - 512 (limit). Certain file systems

On May 25, 2014 3:39 AM, "Geert Stappers" <stappers at stappers.nl> wrote: > > > While going throug old posts found: > > Op 2013-08-31 om 17:01 schreef Raphael S.Carvalho: > > Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds the limit. > > ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary. >

Check if ldlinux.sys is larger than 64k at build time. Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> --- core/Makefile | 5 +++-- core/ldlinux_limit.pl | 31 +++++++++++++++++++++++++++++++ 2 files changed, 34 insertions(+), 2 deletions(-) create mode 100644 core/ldlinux_limit.pl diff --git a/core/Makefile b/core/Makefile index f795a5c..00de331 100644 ---

Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds the limit. ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary. Thus, the size of ldlinux.sys (limit) can be at most: 65536 - 2 * ADV_SIZE - 512. Certain file systems (such as BTRFS and UFS2) will rely on ldlinux.sys being installed on the 0-64k range, thus it can't exceed the limit,

From: Raphael S. Carvalho <raphael.scarv at gmail.com> It's already loading modules successfully, booting Linux, and both UFS version 1 and 2 seem to be working correctly. Signed-off-by: Raphael S. Carvalho <raphael.scarv at gmail.com> --- core/fs/ufs/bmap.c | 202 ++++++++++++++++++++++++++ core/fs/ufs/ufs.c | 404 ++++++++++++++++++++++++++++++++++++++++++++++++++++

On 07/26/2013 08:10 AM, Matt Fleming wrote: > On Wed, 24 Jul, at 08:05:16AM, Raphael S.Carvalho wrote: >> Check if ldlinux.sys is larger than 64k at build time. >> >> Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> >> --- >> core/Makefile | 5 +++-- >> core/ldlinux_limit.pl | 31 +++++++++++++++++++++++++++++++ >> 2

It's already loading modules successfully, and both UFS version 1 and 2 seems to be working correctly. Special thanks to Paulo Alcantara and Matt Fleming for being always ready to help me and give feedback. Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> --- core/fs/ufs/bmap.c | 202 ++++++++++++++++++++++++++ core/fs/ufs/ufs.c | 404

On Mon, 30 Sep, at 02:14:34AM, Raphael S.Carvalho wrote: > From: Raphael S. Carvalho <raphael.scarv at gmail.com> > > v2: Extract ADV_SIZE automatically from libinstaller/setadv.h. > > Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds the limit. > ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary. > Thus, the

From: Raphael S. Carvalho <raphael.scarv at gmail.com> My commit 09f4ac33 broke 'com32/lib/syslinux/disk.c' __lowmem doesn't work for declarations outside the core. Using __lowmem outside the core wouldn't have the desired effect, then lmalloc must be used instead to store dapa into the correct section (".lowmem"). Reported-by: Dark Raven <drdarkraven at

Peter, does this look OK to you? Raphael, I can't work out why ADV_SIZE is a constant in this file? On Sat, 31 Aug, at 05:01:20PM, Raphael S.Carvalho wrote: > Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds the limit. > ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary. > Thus, the size of ldlinux.sys (limit) can be at most:

On Tue, Sep 01, 2015 at 11:40:14PM -0300, Raphael S Carvalho via Syslinux wrote: > On Tue, Sep 1, 2015 at 8:58 PM, Paulo Alcantara via Syslinux < > syslinux at zytor.com> wrote: > > > Hi, > > > > My name is Paulo Alcantara. I've been working on BIOS/UEFI firmware and > > file systems development for a long time already. For those does not > > know,

While going throug old posts found: Op 2013-08-31 om 17:01 schreef Raphael S.Carvalho: > Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds the limit. > ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary. > Thus, the size of ldlinux.sys (limit) can be at most: 65536 - 2 * ADV_SIZE - 512. > > Certain file systems (such as BTRFS

From: Raphael S. Carvalho <raphael.scarv at gmail.com> This patch finishes the MultiFS support. init_multifs gets called in the main (startup) function of ldlinux.c32, so MultiFS will be initialized automatically. init_multifs calls enable_multifs (lives in the core) to hook get_fs_info. Subsequent accesses will callback the get_fs_info living in ldlinux.c32. Signed-off-by: Raphael S.

On Fri, Jul 12, 2013 at 2:21 AM, H. Peter Anvin <hpa at zytor.com> wrote: > On 07/11/2013 10:16 PM, Raphael S.Carvalho wrote: >> This patch adds support for serial output functions. >> It may be useful for debugging purposes since you can separate ordinary outputs from debugging dumps. >> Just add "serial.h", and use either serial_print or serial_puts as you

Hi, My name is Paulo Alcantara. I've been working on BIOS/UEFI firmware and file systems development for a long time already. For those does not know, in the past few years I used to be an active Syslinux contributor and added support to NTFS and XFS file systems, GSoC mentor for Syslinux in 2012, did some bugfixes and some code refactoring (e.g. x86 assembly to pure C) and currently working

[PATCH 001/001 v2] core/serial: Add support for serial output functions. Second version fixes an initialization issue. ----- This patch adds support for serial output functions. It may be useful for debugging purposes since you can separate ordinary outputs from debugging dumps. Just add "serial.h", and use either serial_print or serial_puts as you would use printf and puts