Displaying 10 results from an estimated 10 matches for "core_xfer_buf".
2012 Aug 02
0
[PATCH 3/3] ALPHA: implement and use rdwr_bytes
...shift, count >> shift, is_write) << shift);
+ }
+
+ /* do the hard work */
+ done = 0;
+ if ((lba & mask) != 0) {
+ /* align start sector */
+ before = lba & mask;
+ len = disk->sector_size - before;
+ if (len > count) len = count;
+ res = rdwr_sectors0(core_xfer_buf, lba >> shift, 1, 0);
+ if (!res) return done;
+ if (is_write) {
+ memcpy(core_xfer_buf + before, buf, len);
+ res = rdwr_sectors0(core_xfer_buf, lba >> shift, 1, 1);
+ if (!res) return done;
+ } else {
+ memcpy(buf, core_xfer_buf + before, le...
2012 Sep 10
19
Initial support for sector size >512
This set of patches add some support for sector size >512.
Currently it fixes extlinux, MBR for GPT and ext partitions.
Other code is unaffected.
This set of patches has been tested on a read Dell machine running a beta
firmware.
2015 Oct 05
7
[PATCH 0/4] Improve linker scripts
From: Sylvain Gault <sylvain.gault at gmail.com>
These patches basically remove unused linker scripts and port a change that was
made to an unused script.
Those are to be applied on top of the gcc 5 bug fixes as they would conflict
otherwise.
Sylvain Gault (4):
diag/mbr: fix dependency to linker script
Remove unused linker scripts
core: Make symbols defined in linker script HIDDEN
2014 Jun 21
4
testing out 6.03 network booting...
...n.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; /* LBA of primary volume descriptor */
--
1.9.0
--
Matt Fleming, Intel Open Source Technology Center
2009 May 31
2
Calling between real mode and protected mode on the core32 branch
...apart into a seg:off pair, use the SEG() and
OFFS() macros:
regs.es = SEG(ptr);
regs.ebx.w[0] = OFFS(ptr);
BUT, this is where things get tricky: this can only be done for a
pointer that is below the 1 MB real-mode limit. The way one usually
deals with this is to pass data through the 64K core_xfer_buf, which is
located below the megabyte limit (for com32 modules, this is known as
__com32.cs_bounce).
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
2015 Oct 05
0
[PATCH 2/4] Remove unused linker scripts
...6 <= 0x10000, "64K overflow"));
-
- /*
- * Special 16-bit segments
- */
-
- . = ALIGN(65536);
- .real_mode (NOLOAD) : {
- *(.real_mode)
- }
- HIDDEN(real_mode_seg = core_real_mode >> 4);
-
- . = ALIGN(65536);
- .xfer_buf (NOLOAD) : {
- *(.xfer_buf)
- }
- HIDDEN(xfer_buf_seg = core_xfer_buf >> 4);
-
- /*
- * Used to allocate lowmem buffers from 32-bit code
- */
- .lowmem (NOLOAD) : {
- HIDDEN(__lowmem_start = .);
- *(.lowmem)
- HIDDEN(__lowmem_end = .);
- }
- HIDDEN(__lowmem_len = ABSOLUTE(__lowmem_end) - ABSOLUTE(__lowmem_start));
- HIDDEN(__lowmem_dwords = (__lowmem_len +...
2016 Jun 04
0
[PATCH] Wedding gift, removing double l from auxilliary
...+ /* Add auxiliary information */
mboot_make_memmap();
mboot_apm();
mboot_syslinux_info();
diff --git a/core/i386/syslinux.ld b/core/i386/syslinux.ld
index 36b1a69..e8d32dd 100644
--- a/core/i386/syslinux.ld
+++ b/core/i386/syslinux.ld
@@ -207,7 +207,7 @@ SECTIONS
xfer_buf_seg = core_xfer_buf >> 4;
/*
- * The auxilliary data segment is used by the 16-bit code
+ * The auxiliary data segment is used by the 16-bit code
* for items that don't need to live in the bottom 64K.
*/
diff --git a/doc/extlinux.txt b/doc/extlinux.txt
index d8cbb5d..f0cac8d 100644
--- a/doc/ex...
2014 Jun 19
5
testing out 6.03 network booting...
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
2012 Mar 23
19
[PATCH 00/19][elflink] Improve compatibility with 4.x
From: Matt Fleming <matt.fleming at intel.com>
The following patch series is available at,
git://git.zytor.com/users/mfleming/syslinux.git elflink
All patches are against the 'elflink' branch.
This series fixes a few serious bugs and some behavioural
incompatibilities with the 4.x series.
Matt Fleming (19):
ldlinux: Initialise 'p' before using it.
ldlinux: Parse
2015 Jul 22
13
[PULL 0/8] MultiFS suppport for BIOS and EFI
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