similar to: can't get write_sectors to work...

Here is a partial patch that I'm using to illustrate a few questions that I have. Looking at the gpllib write_sectors (com32/gpllib/disk/write.c) it looks like the allocated size is wrong; size is in sectors so we should adjust the alloc/memcpy by size*SECTOR. Also, comparing core/diskio.c it looks like the registers aren't even setup right. In the patch below I put an #if 0 around the

Based on syslinux 6.03 Memory allocation and copy length should be SECTOR * size for sectors operation. Signed-off-by: Robert <luyao-c at 360.cn> diff --git a/com32/gpllib/disk/write.c b/com32/gpllib/disk/write.c index d183ade..3c9edff 100644 --- a/com32/gpllib/disk/write.c +++ b/com32/gpllib/disk/write.c @@ -40,7 +40,7 @@ int write_sectors(const struct driveinfo *drive_info, const

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:

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

ldisk.c32 is a Lua module that provides information about disks to Lua scripts The example script com32/lua/test/detect_disks.lua uses it to implement some- thing akin to 'disk.c32'. The name 'ldisk.c32' was chosen to avoid a name-clash with 'disk.c32'. --- com32/lua/src/Makefile | 1 + com32/lua/src/ldisk.c | 103

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

The speed value is available since version 2.3 of the SMBIOS specification. Set the default speed string to "Unknown" for older versions. - Sebastian Index: syslinux-3.74-20-g3b80c26/com32/gpllib/dmi/dmi.c =================================================================== --- syslinux-3.74-20-g3b80c26.orig/com32/gpllib/dmi/dmi.c +++ syslinux-3.74-20-g3b80c26/com32/gpllib/dmi/dmi.c @@

From: Matt Fleming <matt.fleming at intel.com> The first two patches in this series are fixes for bugs reported by someone in #syslinux. The third makes dmitest.c32 actually wait for user input. If no one has any objections/concerns, I'll pull this into the official elflink branch. Matt Fleming (3): core: Print error message if we don't load ldlinux.c32 Clean up $(GPLLIB) leak

> 3. The only evidence of any problem from the vampire command is the > events logged on the PDC, and the invalid passwords. I tried > deleting the trust account on the PDC and rejoining several times, > with Samba on, off, and nmbd on and off. The result is always the > same. The bad password hashes are always the same for each account. > If I change a password on the PDC

I'm seeing some sporadic build failures with 'make -j4'. The failures are: make[4]: *** No rule to make target 'hello.c32', needed by 'all'. Stop. I've only seen the failures with com32/samples/hello.c32 and com32/rosh/rosh.c32. I'm not a make expert, but I think it's due to missing dependencies. This patch seems to fix my failures, but I'm

Background: Chengdu Haiguang IC Design Co., Ltd (Hygon) is a Joint Venture between AMD and Haiguang Information Technology Co.,Ltd., aims at providing high performance x86 processor for China server market. Its first generation processor codename is Dhyana, which originates from AMD technology and shares most of the architecture with AMD's family 17h, but with different

Fixed: cp -r syslinux-6.01/com32/libupload/*.h image/usr/share/syslinux/com32/include/ [snip] rm -rf image/usr/share/syslinux/com32/include [snip] cp: cannot create regular file `image/usr/share/syslinux/com32/include/serial.h': No such file or directory The cp is happened in the "libupload" dir, while "rm -fr" is happend in "lib" dir, let "libupload"

Hello Erwan, You will find below a pull request for the bug reported by Robert Jordan in the disk library. The first patch is the one he tested (see http://syslinux.zytor.com/archives/2010-September/015341.html) and the second one is a sanity check for the number of sectors written by call ( see http://syslinux.zytor.com/archives/2010-September/015342.html). Thanks, The following changes

Hi, Matt Fleming wrote: > ld: libpng/pngrtran.o: warning: relocation against `png_do_read_filler' in readonly section `.text'. > ld: warning: creating a DT_TEXTREL in object. > > Looks like your files aren't position-independent. What does, > > file com32/gpllib/dmi/dmi.o > > say? # file com32/gpllib/dmi/dmi.o com32/gpllib/dmi/dmi.o: ELF 32-bit LSB

> On Jul 10, 2015 5:29 PM, "poma via Syslinux" <syslinux at zytor.com> wrote: > > > The same as with the ISOLINUX, stable and git. > > Only this time has nothing to do with the menu. > > 1) EXTLINUX is no longer a discrete variant. The installer extlinux now > installs SYSLINUX. > 2) William Kensington already saw a similar behavior wherein an

Hi, well, I was finally able to build syslinux-5.11-pre8 from git, but the system doesn't boot with the self-compiled version. All I see is: http://666kb.com/i/cfplluqpcy6owptq3.jpg Build log can be found in http://www.syslinux.org/archives/2013-July/020452.html After I installed the self-compiled syslinux version, I run this commands: # cd /boot/extlinux # rm -rf *.c32 # extlinux

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) /*

This is part of some patches to support sectors > 512. Currently I'm able to boot a Ubuntu kernel but seems that mboot is not working for some reason. This patch add a rdwr_bytes functions which remove the assumption in some places that sector is 512. This function is quite helpful if you are going to read/write a range of bytes to/from the stack without creating stack overflows for free.

Hello, Would com32 modules be considered the same as an ordinary Linux executable with respect to LGPL? That is, as long as you released any changes to syslinux/com32 libs would you also have to release the source to the com32 module? Thanks for your time.