delta/syslinux.git/core/comboot.inc, branch lua git.kernel.org: pub/scm/boot/syslinux/syslinux.git Export the 64-bit partition offset and use it in chain.c 2010-06-27T19:02:48+00:00 H. Peter Anvin hpa@zytor.com 2010-06-27T19:02:48+00:00 b775b0040fe57ef71ec9cd98f9c124a3d116269b When used with the "fs" option to chain.c32, we need to know our own filesystem offset. That means knowing if we used the MBR vs GPT partition information, as well as if we ended up using the passed-in information or not. Resolve this by providing an explicit pointer to the current partition offset. Eventually this should be replaced by some kind of statfs() call. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
When used with the "fs" option to chain.c32, we need to know our own
filesystem offset.  That means knowing if we used the MBR vs GPT
partition information, as well as if we ended up using the passed-in
information or not.

Resolve this by providing an explicit pointer to the current partition
offset.  Eventually this should be replaced by some kind of statfs()
call.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
comboot: allow the read disk API call to specify a 64-bit LBA 2010-06-21T22:16:33+00:00 H. Peter Anvin hpa@linux.intel.com 2010-06-21T22:12:48+00:00 2f712545dd82f5906ec930b643d44e8b12295682 We already had two MBZ fields reserved, so use one of them to expand into a 64-bit LBA. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com> 
We already had two MBZ fields reserved, so use one of them to expand
into a 64-bit LBA.

Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
pxe: centralize all the IP information and export it to modules 2010-06-19T01:19:37+00:00 H. Peter Anvin hpa@linux.intel.com 2010-06-19T01:16:48+00:00 42615d2c7eb2aeaea280891b80f1e76ac670fbf2 It appears that there still are PXE stacks in the field which needs the crutch of being pointed to the default gateway. As such, put all the IP information into a single memory structure and allow modules to see it. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com> 
It appears that there still are PXE stacks in the field which needs
the crutch of being pointed to the default gateway.  As such, put all
the IP information into a single memory structure and allow modules to
see it.

Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Restore skip CR and LF in the comboot API copies of the banner strings 2010-05-17T21:14:21+00:00 H. Peter Anvin hpa@linux.intel.com 2010-05-17T21:14:21+00:00 d3e40e850f62da372296e98db701c2dfb202bffc The comboot API should not report leading CR and LF in the banner strings. This was done in 3.86, but apparently was lost due to mismerge (52c9d5ba2af4e1f77aa2486a2af2bcab0b0af52c) in the 4.00 branch. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com> 
The comboot API should not report leading CR and LF in the banner
strings.  This was done in 3.86, but apparently was lost due to
mismerge (52c9d5ba2af4e1f77aa2486a2af2bcab0b0af52c) in the 4.00 branch.

Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
core: fix "sector size" confusion 2010-05-14T22:22:00+00:00 H. Peter Anvin hpa@linux.intel.com 2010-05-14T22:22:00+00:00 4f2568ba84172915df94995df4ad358d2f09cc0e Fix the case where the "sector size" used by the pm filesystem driver isn't the same thing as the SECTOR_SIZE/SECTOR_SHIFT macros used in the assembly code. This is a per-device property, and in the particular case of isolinux hybrid, they are not even currently the same (for all others, they are the same for now, but not necessarily in the future.) Signed-off-by: H. Peter Anvin <hpa@linux.intel.com> 
Fix the case where the "sector size" used by the pm filesystem driver
isn't the same thing as the SECTOR_SIZE/SECTOR_SHIFT macros used in
the assembly code.  This is a per-device property, and in the
particular case of isolinux hybrid, they are not even currently the
same (for all others, they are the same for now, but not necessarily
in the future.)

Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
comboot: fix comapi_open 2010-05-14T17:01:54+00:00 Sebastian Herbszt herbszt@gmx.de 2010-05-01T13:28:49+00:00 7d7b2bc2cdb8d99eee9ef41c21612a60728a7713 Fix breakage introduced by commit e375515ddc712f1f69ee21337db2a3267caa5d49 (Add 32-bit versions of open file/close file). Signed-off-by: Sebastian Herbszt <herbszt@gmx.de> Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
Fix breakage introduced by commit e375515ddc712f1f69ee21337db2a3267caa5d49
(Add 32-bit versions of open file/close file).

Signed-off-by: Sebastian Herbszt <herbszt@gmx.de>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
Add 32-bit versions of open file/close file 2010-03-06T19:55:57+00:00 H. Peter Anvin hpa@zytor.com 2010-03-06T19:55:57+00:00 e375515ddc712f1f69ee21337db2a3267caa5d49 Add 32-bit API calls for open file and close file. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
Add 32-bit API calls for open file and close file.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
readdir: replace opendir/readdir/closedir API with a 32-bit API 2010-03-05T06:54:07+00:00 H. Peter Anvin hpa@zytor.com 2010-03-05T06:54:07+00:00 b4da45a8a0a7c7e6f66850dee1f1733100767c30 The 16-bit API to opendir/readdir/closedir was confused, had a memory leak, and was incompatible with Syslinux 3.x anyway. Replace it with a pure 32-bit API. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
The 16-bit API to opendir/readdir/closedir was confused, had a memory
leak, and was incompatible with Syslinux 3.x anyway.  Replace it with
a pure 32-bit API.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
core: get rid of unmangle_name completely 2010-03-01T05:12:46+00:00 H. Peter Anvin hpa@zytor.com 2010-03-01T05:12:46+00:00 0fba01f4009b29ec9f2cdadafa33fd4699675542 The notion of "mangle name" is now restricted to producing a canonical representation, e.g. changing \ -> / for FAT filesystems. However, the resulting mangled name is now always human-readable, so there never is any reason to unmangle a name. Get rid of not just the mangling, but of the resulting unmangled-name buffers and so on. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
The notion of "mangle name" is now restricted to producing a canonical
representation, e.g. changing \ -> / for FAT filesystems.  However,
the resulting mangled name is now always human-readable, so there
never is any reason to unmangle a name.

Get rid of not just the mangling, but of the resulting unmangled-name
buffers and so on.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
opendir: remove unnecessary buffer pointer 2010-02-25T06:16:24+00:00 H. Peter Anvin hpa@zytor.com 2010-02-25T06:16:24+00:00 e2e05937cbd35a072934919853b3a3e0aadb5c49 We don't need to abuse the InitRD buffer anymore. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
We don't need to abuse the InitRD buffer anymore.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>