similar to: [PATCH 1/1] core: Add a check at ldlinux.sys build time.

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

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:

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

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

> 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

On Mon, Sep 16, 2013 at 11:08 AM, Matt Fleming <matt at console-pimps.org> wrote: > Peter, does this look OK to you? > > Raphael, I can't work out why ADV_SIZE is a constant in this file? Matt, ADV_SIZE is currently a constant value, but it may change in the future. So it would need some care. Regards, Raphael S. Carvalho

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

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

On Mon, 16 Sep, at 09:49:01AM, H. Peter Anvin wrote: > We probably will need to increase out to 4K because of newer drives. Raphael, is there any way we could extract the ADV_SIZE value from libinstaller/setadv.h and pass it to ldlinux_limit.pl? That would allow things to keep working in future when we do upgrade to 4K. -- Matt Fleming, Intel Open Source Technology Center

On Fri, Jul 26, 2013 at 4:58 PM, H. Peter Anvin <hpa at zytor.com> wrote: > 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> > >> --- > >>

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 files changed, 34 insertions(+), 2 deletions(-) > create mode 100644

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

It would be good to clean it up so out can be used for both. Just teach it that ) ends the parse. On June 4, 2014 2:06:22 PM PDT, Raphael S Carvalho <raphael.scarv at gmail.com> wrote: >On Wed, Jun 4, 2014 at 5:36 PM, Raphael S Carvalho ><raphael.scarv at gmail.com> wrote: >> On Wed, Jun 4, 2014 at 5:21 PM, H. Peter Anvin <hpa at zytor.com> wrote: >>> On

Previously, even non-length commands were added to history, but it shoudn't, e.g: just typing enter. For example, if you type: FOO -> (ENTER) -> (ENTER), then to get FOO from the history you would have to press the UP key twice. It also saves a bit of memory. Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> --- com32/elflink/ldlinux/cli.c | 13 ++++++++----- 1

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

Raphael, Except for the : instead of the , this looks like the grub hard disk nomenclature that's been around for a thousand years. Certainly since early GRUB1. Example: (hd0,0)/grub/splash.xpm.gz Why did you chose : instead of grub's , ? I'm guessing (like grub) that disks & partitions are 0-based? (Were the original grub authors European?) Spike #Date: Wed, 4 Jun 2014

Hi Genec, On Sun, May 25, 2014 11:27 am, Gene Cumm wrote: > Raphael/Paulo: does UFS2 have a hard 64kiB limit? I know it's not > installed to the first sector where the first superblock is located. I have no much experience with UFS2 filesystem. I've just took a quick look at its internals and I can see that UFS2 places its superblock at either 64KiB or 256KiB (depending on the

On Wed, Jun 4, 2014 at 5:21 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 06/04/2014 11:09 AM, Raphael S Carvalho wrote: >> Before proceeding with the MultiFS patchset, let's discuss the MultiFS syntax. >> >> It's currently as follows: >> (hd[disk number]:[partition number])/path/to/file >> >> Any objections? >> > > As others

eparam would only be used if EBIOS is available. If it is not, then there is no reason to allocate eparam. Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> --- com32/lib/syslinux/disk.c | 10 +++++----- 1 files changed, 5 insertions(+), 5 deletions(-) diff --git a/com32/lib/syslinux/disk.c b/com32/lib/syslinux/disk.c index 093751a..d96acbf 100644 ---