similar to: [PATCH] meminfo.c32: Remove unneeded 'x' characters from output

Hello. Use <inttypes.h> PRIx64 instead of llx to get rid of gcc warning format ?%llx? expects type ?long long unsigned int?, but argument 2 has type ?uint64_t? -- MartinS diff --git a/com32/gpllib/acpi/xsdt.c b/com32/gpllib/acpi/xsdt.c index 208abc6..228b6c3 100644 --- a/com32/gpllib/acpi/xsdt.c +++ b/com32/gpllib/acpi/xsdt.c @@ -63,7 +63,7 @@ int parse_xsdt(s_acpi * acpi) /*

Hi, I just pushed out changes that fix pretty much all the compiler build warnings on the elflink branch. Also, I've added "auto extension" support so that if the user doesn't type the file name extension it will automatically be looked up, e.g. now typing "ls" will execute "ls.c32". The following changes since commit

I agree. This line was removed during testing because it didn't make big sense (EFLAGS_CF, ebx, and ecx are checked after int 0x13). But it's better to leave it in code to make sure that BIOS conforms standards and clears CF flag on successful call. Adjusted patch is given below. Andy Alex Signed-off-by: Andy Alex <andy at r-tt.com> --- diff -uprN

DL register is not set to drive number when detecting EDD for drive, so detection may fail. Signed-off-by: Andy Alex<andy at r-tt.com> --- diff -uprN syslinux-6.02.orig/core/fs/diskio_bios.c syslinux-6.02/core/fs/diskio_bios.c --- syslinux-6.02.orig/core/fs/diskio_bios.c 2013-10-13 21:59:03.000000000 +0400 +++ syslinux-6.02/core/fs/diskio_bios.c 2014-02-20 12:15:08.000000000 +0400 @@ -337,7

Op 2014-02-20 om 13:23 schreef Andy Alex: > DL register is not set to drive number when detecting EDD for drive, so detection may fail. > > Signed-off-by: Andy Alex<andy at r-tt.com> > --- > diff -uprN syslinux-6.02.orig/core/fs/diskio_bios.c syslinux-6.02/core/fs/diskio_bios.c > --- syslinux-6.02.orig/core/fs/diskio_bios.c 2013-10-13 21:59:03.000000000 +0400 > +++

Hi Peter, The main part of this pull request includes commits that try to replace as many __intcall() invocations as possible. Some remain, but not many (and eventually they'll be gone too). There's also a patch to make better use of ld's --as-needed option and various other bug fixes/cleanups. The following changes since commit ff7334a2ce536b7f4b1f6d6f93ff4e285a3bd45a: Only

Hi Peter, Please pull the following changes. Paulo, I had to revert your "pxe: resolve names via DNS from protected-mode code" change because dns_resolv() is only implemented for PXELINUX and causes undefined symbol references for ISOLINUX, etc. Feel free to make the change again on top of the revert. The following changes since commit e7bd19def830e8341b1a100956345f1028740b9e:

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

On Mon, Jan 21, 2019 at 3:37 AM Victor Sologoubov via Syslinux <syslinux at zytor.com> wrote: > > diff --git a/core/localboot.c b/core/localboot.c > index 0b8769e4..30bfb272 100644 > --- a/core/localboot.c > +++ b/core/localboot.c > @@ -63,7 +63,6 @@ __export void local_boot(int16_t ax) > ireg.eax.w[0] = 0; /* Reset drive */ > __intcall(0x13,

diff --git a/core/localboot.c b/core/localboot.c index 0b8769e4..30bfb272 100644 --- a/core/localboot.c +++ b/core/localboot.c @@ -63,7 +63,6 @@ __export void local_boot(int16_t ax) ireg.eax.w[0] = 0; /* Reset drive */ __intcall(0x13, &ireg, NULL); - memset(&ireg, 0, sizeof(ireg)); ireg.eax.w[0] = 0x0201; /* Read one sector */ ireg.ecx.w[0] = 0x0001; /* C/H/S = 0/0/1 (first

I was having a display problem with memtest86 and dos via a memdisk image not displaying properly when launched using vesamenu.c32 and using a PNG background image. Instead of proper text output the display mode is not changed and the existing menu image is corrupted by the outputted text. This seems to be similar or identical to a problem describe in a previous mailing:

getnybble() needs to return four bits at a time from every byte. During rle decode, rows are rounded to an integer number of bytes. The rle length needs to be able to hold values > 255. Signed-off-by: Chas Williams <3chas3 at gmail.com> --- core/graphics.c | 35 +++++++++++++++++++++-------------- 1 file changed, 21 insertions(+), 14 deletions(-) diff --git a/core/graphics.c

Im trying to use newer simple-menu features, and have found that the following config-file (closely based on wiki pxelinux example) - fails for 3.62-pre11, - works for 3.62-pre10 where 'working' is successive reloads such that re-edits of file are seen on next reload and broken is issuing this error: Initial menu has no LABEL entries! boot: #>

On 03/23/2016 12:10 PM, Peter Steele wrote: > Has anyone seen this issue? We're running containers under CentOS 7.2 and some > of these containers are reporting incorrect memory allocation in > /proc/meminfo. The output below comes from a system with 32G of memory and > 84GB of swap. The values reported are completely wrong. > There was a meminfo bug here:

Several of these messages we coded using line continuation within a string literal. This is generally not recommended and also lead to odd sequences of many blanks in the middle of the messages. The message indicating a discarded write due to MSI-X already being enabled doesn''t need to be issued when a write doesn''t actually modify the current value. Adjust the surrounding logic

On 03/23/2016 01:41 PM, Peter Steele wrote: > On 03/23/2016 09:19 AM, Cole Robinson wrote: >> On 03/23/2016 12:10 PM, Peter Steele wrote: >>> Has anyone seen this issue? We're running containers under CentOS 7.2 and some >>> of these containers are reporting incorrect memory allocation in >>> /proc/meminfo. The output below comes from a system with 32G of

On 03/23/2016 09:19 AM, Cole Robinson wrote: > On 03/23/2016 12:10 PM, Peter Steele wrote: >> Has anyone seen this issue? We're running containers under CentOS 7.2 and some >> of these containers are reporting incorrect memory allocation in >> /proc/meminfo. The output below comes from a system with 32G of memory and >> 84GB of swap. The values reported are

From: Matt Fleming <matt.fleming at linux.intel.com> This series fixes some bugs and switches the elflink branch to be entirely ELF modules. It applies on top of, http://syslinux.zytor.com/archives/2011-April/016369.html The deletions in the diff stat below are mainly from deleting com32/elflink/modules (finally!). Now there should be no duplicate code because we don't need COM32 and

Now reporduced with 100% 1) create contrainer with memory limit 1Gb 2) run inside simple memory test allocator: #include <malloc.h> #include <unistd.h> #include <memory.h> #define MB 1024 * 1024 int main() { int total = 0; while (1) { void *p = malloc( 100*MB ); memset(p,0, 100*MB ); total = total + 100; printf("Alloc %d Mb\n",total); sleep(1);

Hi, These patches contain support for some features that are already in Syslinux 4 but weren't working properly on the elflink branch. It's another step closer to feature parity with Syslinux 4. Having to jump through the comboot API for localboot support is less than ideal and I'll eventually fix that, probably when we move a big chunk of code from asm to C. Also, there's a