search for: isohdpfx

...syslinux-bot for Martin Str|mberg <ams at ludd.ltu.se> ----- Date: Sat, 25 Mar 2017 05:54:09 -0700 From: syslinux-bot for Martin Str|mberg <ams at ludd.ltu.se> To: Syslinux commits mailing list <syslinux-commits at zytor.com> Cc: ams at ludd.ltu.se Subject: [syslinux:master] mbr/isohdpfx.S: correct pointer for heads/sectors X-Mailer: Syslinux-git-log-daemon Commit-ID: 48e94f4fa7b3c32cbd43b6e57c64bc933f76d059 Gitweb: http://www.syslinux.org/commit/48e94f4fa7b3c32cbd43b6e57c64bc933f76d059 Author: Martin Str|mberg <ams at ludd.ltu.se> AuthorDate: Sat, 25 Mar 2017 08:15...

...ux-bot for Martin Str|mberg <ams at ludd.ltu.se> ----- Date: Sat, 15 Apr 2017 10:27:08 -0700 From: syslinux-bot for Martin Str|mberg <ams at ludd.ltu.se> To: Syslinux commits mailing list <syslinux-commits at zytor.com> Cc: ams at ludd.ltu.se Subject: [syslinux:syslinux-4.xx] mbr/isohdpfx.S: correct stack for heads/sectors; revert X-Mailer: Syslinux-git-log-daemon Commit-ID: 45af3d24578783c53781050ef2a233dc84ff5ffd Gitweb: http://www.syslinux.org/commit/45af3d24578783c53781050ef2a233dc84ff5ffd Author: Martin Str|mberg <ams at ludd.ltu.se> AuthorDate: Sun, 26 Mar 2017...

--- mbr/isohdpfx.S | 10 ++++++++++ 1 files changed, 10 insertions(+), 0 deletions(-) diff --git a/mbr/isohdpfx.S b/mbr/isohdpfx.S index 9e9d55c..bddb533 100644 --- a/mbr/isohdpfx.S +++ b/mbr/isohdpfx.S @@ -67,6 +67,7 @@ _start: movw %ax, %ss movw $stack, %sp movw %sp, %si + movw %sp, %bp /* needed later i...

...via Syslinux wrote: > It is good to see this > ----- Forwarded message from syslinux-bot for Martin Str|mberg <ams at ludd.ltu.se> ----- > Date: Sat, 25 Mar 2017 05:54:09 -0700 > From: syslinux-bot for Martin Str|mberg <ams at ludd.ltu.se> > Subject: [syslinux:master] mbr/isohdpfx.S: correct pointer for heads/sectors > Commit-ID: 48e94f4fa7b3c32cbd43b6e57c64bc933f76d059 > Gitweb: http://www.syslinux.org/commit/48e94f4fa7b3c32cbd43b6e57c64bc933f76d059 > Author: Martin Str|mberg <ams at ludd.ltu.se> ... > diff --git a/mbr/isohdpfx.S b/mbr/isohdpfx.S...

...on */ movl $0xeb42b4+((read_common-read_sector_cbios-4) << 24), \ (read_sector_cbios) jmp 1f 1: This is my interpretation: David's machine's BIOS returns no carry indicating maybe support. However it doesn't set BX to the correct value, so isohdpfx.S jumps to 1f with some flags in CX set. Or David's machine's BIOS returns carry but corrupts CX. My versions of isohdpfc just replaced the first "jc 1f" above with "jnc 1f" or with "jmp 1f", thus in the end possibly indicating EBIOS support to isolinux (assu...

Hi, given the fact that the conversion has the factor HC*SH = "secpercyl", which is invariant under swapping, there remains as suspect in read_sector_cbios only this division: divb (sectors) There is a suspicious discrepancy in the code: heads = (stack-16) sectors = (stack-18) ... /* here we computer CHS values or just do some dummy computation for EBIOS */ andw $0x3f,

Hi together, this is the second version of my cross-compilation patch serie. I'm sending it in the hope to get an honest review, and possibly see the patches integrated upstream. Those patches allow to build syslinux using a toolchain different from the host one by explicitely using the host toolchain for the utilities that are required at build-time / on the build machine. I am using the

Hi, Martin Str|mberg wrote: > And given that space in isohdpfx is very limited (432 bytes) perhaps > the right thing might be to not have that xor in there. > But then better safe than sorry, and given that there is space _now_, > why not? I still agree. But while answering Ady's questions i get to a question of my own: Do all six fixed isohdp*...

...vin to save bytes: * Use memory-mapped I/O register to read keyboard shift flags * Don't reload DX from memory; move immediate byte to register Tested using mbr.bin. TJ (3): mbr: Ctrl-key press forces load from first hard disk gptmbr: Ctrl-key press forces load from first hard disk isohdpfx: Ctrl-key press forces load from first hard disk mbr/gptmbr.S | 14 ++++++++++++-- mbr/isohdpfx.S | 10 ++++++++++ mbr/mbr.S | 10 ++++++++++ 3 files changed, 32 insertions(+), 2 deletions(-)

...cution from the MBR is obviously at http://git.zytor.com/syslinux/syslinux.git/tree/core/isolinux.asm#n186 (Do i get it right that this is the Intel syntax ? (Gronfff)) If POP yields the victim of the most recent not yet popped PUSH, then this does not look correctly coordinated with the MBR. isohdpfx.S has: pushw %cx /* -16: Save sectors on the stack */ movzbw %dh, %ax /* dh = max head */ incw %ax /* From 0-based max to count */ pushw %ax /* -18: Save heads on the stack */ mulw %cx /* Heads*sectors -> sectors per cylinder */ pushw %bx /* -20: EBIOS flag */ isolinux.asm has:...

...mon-read_sector_cbios-4) << 24), \ > (read_sector_cbios) > jmp 1f > 1: > > > This is my interpretation: > > David's machine's BIOS returns no carry indicating maybe > support. However it doesn't set BX to the correct value, so isohdpfx.S > jumps to 1f with some flags in CX set. > > Or David's machine's BIOS returns carry but corrupts CX. > > My versions of isohdpfc just replaced the first "jc 1f" above with > "jnc 1f" or with "jmp 1f", thus in the end possibly indicating EBI...

Thomas Schmitt wrote: > I have some problems understanding the details of the program's flow. > > - The code inside PARTITION_SUPPORT is supposed to be inactive with > MBR isohdpfx.bin. It belongs to isohybrid --partok which is equivalent > to MBRs isohdppx*.bin. Debian uses isohdpfx.bin. Yes. isohdpfx.bin is generated from isohdpfx.S in which PARTITION_SUPPORT is not defined. isohdppx.bin us generated from isohdppx.S which #defines PARTITION_SUPPORT to 1 and #include...

...allowing a third El Torito image in HFS+ format to be made available to the firmware. This requires padding the MBR images slightly in order to leave space for the Apple header, but should have no functional impact. Signed-off-by: Matthew Garrett <mjg at redhat.com> --- diff --git a/mbr/isohdpfx.S b/mbr/isohdpfx.S index 2784fb8..65ab75a 100644 --- a/mbr/isohdpfx.S +++ b/mbr/isohdpfx.S @@ -65,6 +65,38 @@ bootsec: .text .globl _start _start: + nop + nop + nop + nop + nop + nop + nop + nop + nop + nop + nop + nop + nop + nop + nop + nop + nop + nop + nop + nop + nop + nop + nop + nop + n...

...; tree before running these commands. With this in mind, here are my remarks: _Unde PC-BIOS you write: The ISO 9660 production program xorriso can enhance its results by isohybrid, if an MBR template file from the local SYSLINUX installation is provided. The names of these files match the pattern isohdpfx*.bin and are to find in SYSLINUX directory ./mbr or installed as e.g. /usr/lib/syslinux/isohdpfx.bin. But in ./mbr (Syslinnux-407) I find three files isohdpfx{,_c,_f}f.bin so whare are their respective differences and/or use cases? _When you write just before the UEFI title: The result needs no f...

...or MBR partition is detected. Signed-off-by: MartinS <ams at ludd.ltu.se> --- Comments? diff --git a/mbr/Makefile b/mbr/Makefile index be2bded..7095396 100644 --- a/mbr/Makefile +++ b/mbr/Makefile @@ -21,7 +21,8 @@ include $(MAKEDIR)/embedded.mk all: mbr.bin altmbr.bin gptmbr.bin isohdpfx.bin isohdppx.bin \ mbr_c.bin altmbr_c.bin gptmbr_c.bin isohdpfx_c.bin isohdppx_c.bin \ - mbr_f.bin altmbr_f.bin gptmbr_f.bin isohdpfx_f.bin isohdppx_f.bin + mbr_f.bin altmbr_f.bin gptmbr_f.bin isohdpfx_f.bin isohdppx_f.bin \ + isohdpfv.bin isohdppv.bin %.o: %.S $(CC) $(MAKEDEPS) $(SFLAGS)...

Hello all, Past few days I was working on porting the isohybrid perl script to c. (-> https://fedorahosted.org/fedora-engineering-services/ticket/15) The first patch towards the same is attached with this mail. And the same could also be accessed from: http://pjp.dgplug.org/tools/syslinux-3.86-isohybrid.patch I would really appreciate it if somebody could have a look at it and let me know

..., > > which can potentially deal with a different situation than the first > > part of the patch, and, if for some reason additional space is needed > > in the future, it could be considered on its own for future edition. > > > > Essentially the approach I took on the isohdpfx branch on my personal repos. And meanwhile at the more central git repository. Thank you Gene. @Martin: I think `git rebase master` might need minor manual labour. Groeten Geert Stappers -- Leven en laten leven

...> How large is the binary currently ? > Would there be room to print the (Cylinder, Head, Sector) address in > case of CBIOS ? Yes. It becoming very tight now, so I shortened the error messages. First though I want to say I've managed to simulate David's error in qemu by forcing isohdpfx.bin to fail the EBIOS test. /* Check to see if we have EBIOS */ pushw %dx /* drive number */ movb $0x41, %ah /* %al == 0 already */ movw $0x55aa, %bx xorw %cx, %cx xorb %dh, %dh stc int $0x13 //X...

...ath of fresh air". And yeah much appreciation to Thomas for this. > /usr/compat.static/bin/xorriso -as mkisofs -joliet -graft-points -c > boot/isolinux/boot.cat -b boot/isolinux/isolinux.bin -no-emul-boot > -boot-info-table -boot-load-size 4 -isohybrid-mbr > /usr/share/syslinux/isohdpfx.bin --modification-date=2014020113222000 -V > XPMOVER -o xpmover-erebos-20140201-132220.iso -r cdmaster --sort-weight 0 > / --sort-weight 1 /boot --sort-weight 3 /boot/kernel --sort-weight 5 > /boot/isolinux --sort-weight 6 /boot/isolinux/isolinux.bin > This look like perhaps exactly...

Thomas Schmitt wrote: > So if we had a MBR which prints the content of the first 512 read bytes > we could tell whether they are block aligned and from which block they > come. Ok. I'll try. Is it the isohdppx or isohdpfx (or both) that is relevant? Meanwhile I have a hacked isohdppx.bin that prints: G if GPT M if MBR <nothing> if no partition info E if EBIOS C if not EBIOS (from "CHS"). For isohdpfx.bin it will print: E if EBIOS C if not EBIOS (from "CHS"). Is that interesting for you/...