similar to: [PATCH] chain: Fix chainloading on 6.02

Pulled common code out of these functions into new ones. The functions chs_setup and ebios_setup were created for this purpose. Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> --- com32/include/syslinux/disk.h | 7 ++ com32/lib/syslinux/disk.c | 173 +++++++++++++++++++++-------------------- 2 files changed, 97 insertions(+), 83 deletions(-) diff --git

This patch will improve the flow at disk_write_sectors and disk_read_sectors. It does that by creating a table of values respective to the operation. Besides, read and write operations are pretty similar to each other, so I redesigned the routines to avoid duplication. Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> --- com32/include/syslinux/disk.h | 18 ++++

Rework disk library to work on a firmware independent way. Each specific implementation goes through subdirs like "bios/" and "efi/" respectively. Signed-off-by: Paulo Alcantara <pcacjr at zytor.com> --- com32/include/syslinux/disk.h | 50 +++- com32/lib/Makefile | 2 + com32/lib/syslinux/disk.c | 583

This patch will improve the flow at disk_write_sectors and disk_read_sectors significantly, but it *will* introduce bugs if either of the above functions gets called before disk_get_params. --- com32/include/syslinux/disk.h | 21 +++++ com32/lib/syslinux/disk.c | 170 +++++++++++++++++++++-------------------- 2 files changed, 108 insertions(+), 83 deletions(-) diff --git

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:

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

On Tue, 17 Sep, at 04:42:24PM, Raphael S.Carvalho wrote: > 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

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

eparam will only be used if EBIOS is available on the underlying disk. If not so, then there is no reason to allocate eparam. --- com32/lib/syslinux/disk.c | 13 +++++++------ 1 files changed, 7 insertions(+), 6 deletions(-) diff --git a/com32/lib/syslinux/disk.c b/com32/lib/syslinux/disk.c index 093751a..554bed3 100644 --- a/com32/lib/syslinux/disk.c +++ b/com32/lib/syslinux/disk.c @@ -73,7

On Fri, 06 Sep, at 01:00:55AM, Raphael S.Carvalho wrote: > eparam will only be used if EBIOS is available on the underlying disk. > If not so, then there is no reason to allocate eparam. > --- > com32/lib/syslinux/disk.c | 13 +++++++------ > 1 files changed, 7 insertions(+), 6 deletions(-) > > diff --git a/com32/lib/syslinux/disk.c b/com32/lib/syslinux/disk.c > index

Fix breakage in the "hide" option support patch: - The code which initialized the global variable "dapa" was lost in commit 81c203f2, therefore EBIOS access did not work properly. Fixed by removing the global variable completely and moving all bounce buffer handling into read_sector() and write_sector(). - write_sector() copied data to the bounce buffer, but then

Hello, the following patches should get multidisk access working. The syntax accepted is the following: (hdx,y)/path/to/file where x is the disk number and start at 0 and the y is the partition number starting at 1. So (hd0,1) is the first partition of the first disk. the other accepted syntax is using MBR's 32 bits disk signature so for example: (mbr:0x12345678,2)/foo/bar would address

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 all, I use XP on my laptop PC, with 30 GB HD (single partition), and a 3.5" hard drive (not a stick), accessed through a USB encasing, partitioned as five logical drives. I have successfully set up syslinux to boot several Ubuntu versions from the primary USB hard drive partition, and no problems there. The problem is, I would like to have an entry in the menu, like "Boot from

Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- doc/comboot.txt | 12 ++++++------ 1 files changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/comboot.txt b/doc/comboot.txt index 4b4b880..04d5deb 100644 --- a/doc/comboot.txt +++ b/doc/comboot.txt @@ -986,27 +986,27 @@ AX=0024h [3.80] Cleanup, shuffle and boot, raw version ++++ 32-BIT ONLY API CALLS ++++ -void

Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- doc/comboot.txt | 12 ++++++------ 1 files changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/comboot.txt b/doc/comboot.txt index 4b4b880..04d5deb 100644 --- a/doc/comboot.txt +++ b/doc/comboot.txt @@ -986,27 +986,27 @@ AX=0024h [3.80] Cleanup, shuffle and boot, raw version ++++ 32-BIT ONLY API CALLS ++++ -void

Hi, thanks for the answer. Am Sonntag, 11. Juni 2017, 02:16:36 CEST schrieben Sie: > Have you tried building LLVM with assertions enabled? Assertions are > often a good way to catch API misuses, but they aren't on by default > for release builds. Good advice. You're right. Now an assertion triggers. The problem seems to be the argument iterator. Do you know some way to

In Solaris 10 6/06, etc. I used to do things like pid$target::malloc:entry { ustack(); } and got stack traces from my application calling malloc as expected. In Solaris 10 8/07 I only see stack traces from functions inside libc calling a function called lmalloc() but not my malloc calls: ld.so.1`lmalloc ld.so.1`tsort+0xb4

Hi, don't know if this is the right list. Please post a better place, otherwise. I'm currently writing a LLVM ModulePass and ran into strange segfaults or endless loops within LLVM. My main question is, if this is a programming error or API misuse from me or a LLVM bug? Here is some minimal code, that triggers the bug: ---------------- class DebugPass : public ModulePass { public: