search for: core_farcall

...return to real mode. 16-bit pointers in a seg:off pair can be converted to a 32-bit pointer via: ptr = MK_PTR(seg, off); for example: ptr = MK_PTR(regs->es, regs->ebx.w[0]); /* ES:BX */ *** Calls from protected mode (32-bit) to real mode (16-bit): This is done via the core_intcall(), core_farcall() and core_cfarcall() functions, which are the direct versions of the analogous instructions in the com32 world. They are defined in <core.h>: void __cdecl core_intcall(uint8_t, const com32sys_t *, com32sys_t *); void __cdecl core_farcall(uint32_t, const com32sys_t *, com32sys_t *); int __c...

...inux.0) 3. The PXE client downloads pxelinux.0 file. 4. When it starts to load the system crashes and reboots. I was able to pin down the issue with stalls (sleep() function). I suspect that the addresses of the PXE API are not correct or corrupted somehow. When I call this function (core_farcall((size_t)func, &xreg, oreg); in file core/call16.c), the system crashes??? Do you have any suggestions? Thanks, wissam

On May 29, 2014 5:25 AM, "Wissam Shoukair" <wissams at mellanox.com> wrote: > > Hi Gene, > > I was wondering how I can set the ?printf? output to be visible on the screen? (I?m using syslinux-6.03-pre02) printf () or dprintf ()? You need to watch what functions are available at the time you want to print. For example, printf isn't available until ldlinux.c32 is

...ULT 16 __syslinux_adv_ptr Signed-off-by: Matt Fleming <matt.fleming at intel.com> --- efi/main.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/efi/main.c b/efi/main.c index 1cc2456..208fee4 100644 --- a/efi/main.c +++ b/efi/main.c @@ -141,8 +141,8 @@ void __cdecl core_farcall(uint32_t c, const com32sys_t *a, com32sys_t *b) } __export struct firmware *firmware = NULL; -void *__syslinux_adv_ptr; -size_t __syslinux_adv_size; +__export void *__syslinux_adv_ptr; +__export size_t __syslinux_adv_size; char core_xfer_buf[65536]; struct iso_boot_info { uint32_t pvd;...

...eem to be always up to date. The patch i am working on is only for PXELINUX because of different vkernel structure: diff --git a/core/com32.inc b/core/com32.inc index 111590c..f19df7c 100644 --- a/core/com32.inc +++ b/core/com32.inc @@ -135,6 +135,7 @@ __com32: dd 0 ; 64K bounce buffer dd core_farcall ; Farcall entry point dd core_cfarcall ; Cfarcall entry point +global HighMemSize HighMemSize dd 0 ; End of memory pointer (bytes) dd 0 ; No module name dd pm_api_vector ; Protected mode functions diff --git a/core/display_labels.c b/core/display_labels.c new file mode 100644 in...

...xtern void print_sysappend(void); extern const char *sysappend_strings[SYSAPPEND_MAX]; extern uint32_t SysAppends; extern void sysappend_set_uuid(const uint8_t *uuid); +extern void sysappend_set_fs_uuid(void); void __cdecl core_intcall(uint8_t, const com32sys_t *, com32sys_t *); void __cdecl core_farcall(uint32_t, const com32sys_t *, com32sys_t *); diff --git a/core/include/fs.h b/core/include/fs.h index 31ef315..22fd6bf 100644 --- a/core/include/fs.h +++ b/core/include/fs.h @@ -73,6 +73,9 @@ struct fs_ops { int (*next_extent)(struct inode *, uint32_t); int (*copy_super)(void...

Hi all, wasnt sure whether this was the best place to put this information; but something seems to have gone 'backwards' in the later pre-releases of 6.03 regarding network booting. below are results of me testing - i did each a few times to make sure they are valid results. hope it helps identify something that's gone awry ? so far, 6.03 pre11 and pre13 (excluding efi32) seem most

So last week I was wondering if XFS was still working -- even with its last on-disk structure changes -- and it _suprisingly_ worked as expected. Right, now I can finally get rid of GRUB and use Syslinux to boot my Linux on EFI from a rootfs with xfs. Shit, I have two partitions (the first one being the required ESP) so there is no way to access the other partitions since because Syslinux does not