similar to: INT22h/000Dh

This is missing since "shuffler: comboot interface to the new shuffler". Signed-off-by: Sebastian Herbszt <herbszt at gmx.de> --- core/comboot.inc | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/core/comboot.inc b/core/comboot.inc index d6f670c..ef69c49 100644 --- a/core/comboot.inc +++ b/core/comboot.inc @@ -950,7 +950,7 @@ int22_table: dw

I have a Dell 1435 system that will not respond correctly to a com32 call to Local boot Int 22h AX=14h DX = 0 This call should not return. It should unload the PXE+UNDI stacks and continue the boot process with the next boot device. This call is working fine for me on an HP DL360G2 and on a Dell PE 850. But, on this Dell 1435 the call is returning from the Int 22h. I am using syslinux 3.51

From: Gene Cumm <gene.cumm at gmail.com> COMBOOT API: Add calls for directory functions; Implement most only for FAT (SYSLINUX). Uses INT 22h AX= 001Fh, 0020h, 0021h and 0022h to prepare for the COM32 C functions getcwd(), opendir(), readdir(), and closedir(), respectively. INT22h, AX=001Fh will return a valid value for all variants. INT22h, AX= 0020h, 0021h, and 0022h are only

From: Gene Cumm <gene.cumm at gmail.com> COMBOOT API: Add calls for directory functions; Implement most only for FAT (SYSLINUX). Uses INT 22h AX= 001Eh, 001Fh, 0020h and 0021h to prepare for the COM32 C functions getcwd(), opendir(), readdir(), and closedir(), respectively. INT22h, AX=001Eh will return a valid value for all variants. INT22h, AX= 001Fh, 0020h, and 0021h are only

Op 2014-02-28 om 15:51 schreef syslinux-bot for H. Peter Anvin: > Commit-ID: a06818de2a4c49bd64a024dd4f4a09a0caf1f0ac > Gitweb: http://www.syslinux.org/commit/a06818de2a4c49bd64a024dd4f4a09a0caf1f0ac > Author: H. Peter Anvin <hpa at linux.intel.com> > AuthorDate: Fri, 28 Feb 2014 15:48:53 -0800 > Committer: H. Peter Anvin <hpa at linux.intel.com> >

3.80 is a bug fix and internal restructuring release. In particular, the entire shuffler subsystem has been rewritten largely from scratch, as has the Multiboot module. Changes in 3.80: * New shuffler mechanism and API. * Rewritten mboot.c32 module. * The syslinux_boot_linux() function has been simplified. * Don't hang trying to boot a "menu

> On Hexagon, the slot assignment is determined by the layout of the > instructions in memory. The order of the instructions in the packet does > not matter either in the IR, nor in the .s file, but it does when the > packet is encoded into the actual machine code. In LLVM, the Hexagon > shuffler orders the instructions just prior to encoding. > > Specifically, the

Another week, *another* -pre. I'm really planning on this being the last one. The shortlog is appended below. Apart from a better fix for the "disabled menu entry" bug it's only documentation updates. Testing from the last -pre's has been pretty quiet, so as soon as Ady and Matt have tested this one and confirmed that the disabled entry bug is finally gone I'll do the

I have just pushed out Syslinux 3.80-pre7. I am slightly concerned about putting this into the release tree at this point: I was working with some of the shuffler code, and found that the memory map handling was actually severely buggy on some of my test cases. Resolving that problem took rewriting most of syslinux_add_memmap(). However, against better judgement :) I decided to check in the

Hello! I work for O.S. Systems with Otavio Salvador. We are trying to build a module for syslinux to boot a Windows CE 6.0 image. The basic stuff is: we need to load a Windows CE image and jump to its entry point. The Windows CE image file (nk.bin) has its entry point is stored on a variable location. The first 15 bytes of the file are the image header. The following bytes are a contiguous list

>>> > > Aside from potentially needing smaller buffers for config files before > parsing (which seems trivial and unnecessary), what other benefits are > there to this strategy? > At the core, is that Syslinux is a general bootloader which gives access to a virtual filesystem.? It supports multiple open files, but not seeking or writing. <<< Please correct me if

I'm curious how does hexagon hardware decide which slot to use for a given instruction? Is there special hardware to make that decision? I'm asking because I didn't see any information about which slot to use for a given packet. Is it even possible to pass this kind of information through assembly? Say hardware sees a packet and the packet tells it which slot to use. I would greatly

HAS_LOCALBOOT is set unconditionally in config.inc. Signed-off-by: Sebastian Herbszt <herbszt at gmx.de> diff --git a/core/comboot.inc b/core/comboot.inc index 59db7ec..d6f670c 100644 --- a/core/comboot.inc +++ b/core/comboot.inc @@ -723,13 +723,9 @@ comapi_idle: ; ; INT 22h AX=0014h Local boot ; -%if HAS_LOCALBOOT comapi_localboot: mov ax,P_DX jmp local_boot -%else

From: Gene Cumm <gene.cumm at gmail.com> COMBOOT API: Add get config full file name to SYSLINUX Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- Returns the full configuration file name. Int 22h AX 001Eh for now as it appears that the COMBOOT API is designed to be strictly sequential. The API gets extended but only implemented (for now) for SYSLINUX in ldlinux.asm.

Hi everyone, I have pushed out Syslinux 3.81 to the usual places. Again, special thanks to my employer, Intel, for letting me spend time working on this stuff ;) -hpa Syslinux 3.81 is primarily a bug fix release. The main new features are halt-on-idle support and some features to isohybrid, including the ability to boot from an image written to a partition. Changes in 3.81: *

Hello, This is my first post to this list. After searching through the archives and google searches I could not find a solution for my memtest problem. In previous versions of pxelinux/gpxelinux (4.04 and 4.06) I could successfully start the memtest utility. But using pxelinux/gpxelinux versions 5.01 and 5.02 the memtest utility does not boot and I get an error message: boot: Loading

>>>>>I do not understand.Are we parsing a configuration file and potentially >>starting new TFTP transfers while downloading it? How can we do this on >>a single thread?We cannot stop/resume a TFTP transfer then I cannot >>imagine how to detect an INCLUDE during TFTP transfer N to launch TFTP >>transfer N+1 if TFTP transfer N is not finished yet, all in a

The following is the current change-log for Syslinux 6.03. The final stable version might include additional items. Before the final release, it would be helpful to receive feedback about: _ Any item that should be added or eliminated. _ Any item that should be edited in any way (rewording, technical details...). _ Any item that should not be included. _ Any credit that should be added /

On Mon, 24 Jun, at 10:27:52AM, Thomas B?chler wrote: > Am 24.06.2013 04:10, schrieb Gene Cumm: > > In trying Syslinux-6.00 bios/core/pxelinux.0 with a 3.0.21 kernel, I got" > > > > "No linux boot function registered for firmware > > Booting kernel failed: Bad file number" > > > > Using Syslinux-5.10, the same kernel/initrd succeeds. > >

Hi everyone, I have released Syslinux 6.03. It is by and large identical to 6.03-pre20. I would like to do a short cycle for 6.04, because 64-bit support for ext4 has come up as a very high priority. Therefore I do not want to stuff too many things into the 6.04 release but hold them for 6.05. Thanks to Ady for most of the changelog. Changes in 6.03: * chain: Fix chainloading on 6.02