search for: shufflers

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

Hi, I would like to use INT22h, function 000Dh, but I found that it is disabled in vector table: in core/comboot.inc: int22_table: [...] dw comapi_err ; 000D clean up then bootstrap [...] The code of this function is present in this file (comapi_chainboot). Why this function is disabled? Regards Piotr Romaniuk PS I am using syslinux-4.04.

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

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

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

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

Hello all, I am considering a major overhaul of the shuffle and boot functions in the Syslinux core. This means that the current API functions 0011h, 0012h, 001Ah and 001Bh will no longer be supported -- or, in fact, supportable. A new pair of functions will replace 001Ah and 001Bh; 0012h is redundant and 0011h will no longer be meaningful. The intent is to push the responsibility for

I am hitting a problem on syslinux-3.80-pre1-2-g6c0fb9e (only last label in config file is found), but don't want to "cry wolf" (again), so let's start with a question: ui.inc: ; ; Now check if it is a "virtual kernel" ; vk_check: mov esi,[HighMemSize] ; Start from top of memory .scan: cmp esi,[VKernelEnd] jbe

Greetings LLVM hackers and x86 vector shufflers! I would like to flip on another chunk of the new vector shuffling, specifically the logic to mark ~all shuffles as "legal". This can be tested today with the flag "-x86-experimental-vector-shuffle-legality". I would essentially like to make this the default (by removing the &...

...mental-vector-shuffle-legality=1. On Fri, Jan 23, 2015 at 5:19 AM, Andrea Di Biagio <andrea.dibiagio at gmail.com > wrote: > Hi Chandler, > > On Fri, Jan 23, 2015 at 8:15 AM, Chandler Carruth <chandlerc at gmail.com> > wrote: > > Greetings LLVM hackers and x86 vector shufflers! > > > > I would like to flip on another chunk of the new vector shuffling, > > specifically the logic to mark ~all shuffles as "legal". > > > > This can be tested today with the flag > > "-x86-experimental-vector-shuffle-legality". I would es...

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

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

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

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 10/01/2015 05:18 AM, Patrick Masotta via Syslinux wrote: > > 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

Background images come to mind. On October 2, 2015 5:23:18 AM PDT, Patrick Masotta <masottaus at yahoo.com> wrote: >>>> >> >> 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

Hi everyone, I have pushed out Syslinux 3.82 to the usual places. Again, special thanks to my employer, Intel, for letting me spend time working on this stuff ;) -hpa Syslinux 3.82 is a bug fix release for 3.81. Changes in 3.82: * isohybrid: fix the -partok logic for loading from a partition. * ISOLINUX: deal with systems which return from INT 13h with interrupts