Tal Lubko
2016-Jan-25 20:50 UTC
[syslinux] Embedding com32 modules and ldlinux.sys into one file
> -----Original Message----- > From: poma [mailto:pomidorabelisima at gmail.com] > Sent: Tuesday, January 19, 2016 1:30 PM > To: Tal Lubko; 'H. Peter Anvin'; 'Celelibi' > Cc: 'For discussion of Syslinux and tftp-hpa' > Subject: Re: [syslinux] Embedding com32 modules and ldlinux.sys into > one file > > On 19.01.2016 09:07, Tal Lubko via Syslinux wrote: > ... > > > 1) Exposing the bootloader in the BIOS as a (readonly) disk drive > using standard BIOS or EFI interfaces (hpa suggestion). > > This suggestion looks very promising. It probably requires some > changes in the BIOS. I'm not sure if it requires changes in the > bootloader. > > There is one potential problem I see: the bootloader is stored on > some flashrom chip and the Linux image is stored on a different storage > device. > > I think that right now the bootloader assumes they are stored on the > same storage device. Am I wrong? > > If I'm wrong, how do I tell the bootloader to load the Linux image > from a different storage device? > > > > MultiFS pro tempore with QEMU/SeaBIOS only > http://bugzilla.syslinux.org/show_bug.cgi?id=67 >Hi Poma I'm trying to test MultiFS support but not sure how to do it. How do I apply the MultiFS patch? I've seen some e-mails talking about integrating it some branches but I'm not sure it we done. Thanks, Tal
Paulo Alcantara
2016-Jan-25 21:29 UTC
[syslinux] Embedding com32 modules and ldlinux.sys into one file
On Mon, 25 Jan 2016 22:50:24 +0200 Tal Lubko via Syslinux <syslinux at zytor.com> wrote:> > -----Original Message----- > > From: poma [mailto:pomidorabelisima at gmail.com] > > Sent: Tuesday, January 19, 2016 1:30 PM > > To: Tal Lubko; 'H. Peter Anvin'; 'Celelibi' > > Cc: 'For discussion of Syslinux and tftp-hpa' > > Subject: Re: [syslinux] Embedding com32 modules and ldlinux.sys into > > one file > > > > On 19.01.2016 09:07, Tal Lubko via Syslinux wrote: > > ... > > > > > 1) Exposing the bootloader in the BIOS as a (readonly) disk > > > drive > > using standard BIOS or EFI interfaces (hpa suggestion). > > > This suggestion looks very promising. It probably requires some > > changes in the BIOS. I'm not sure if it requires changes in the > > bootloader. > > > There is one potential problem I see: the bootloader is stored > > > on > > some flashrom chip and the Linux image is stored on a different > > storage device. > > > I think that right now the bootloader assumes they are stored on > > > the > > same storage device. Am I wrong? > > > If I'm wrong, how do I tell the bootloader to load the Linux > > > image > > from a different storage device? > > > > > > > MultiFS pro tempore with QEMU/SeaBIOS only > > http://bugzilla.syslinux.org/show_bug.cgi?id=67 > > > > Hi Poma > > I'm trying to test MultiFS support but not sure how to do it. > How do I apply the MultiFS patch? > > I've seen some e-mails talking about integrating it some branches but > I'm not sure it we done.The patchset can be found at my repo: git://git.zytor.com/users/pcacjr/syslinux.git multifs-for-upstream I should push it out to a separate branch on the official repo soon as it was proposed before. Thanks, Paulo -- Paulo Alcantara, HP Inc. Speaking for myself only.
Tal Lubko
2016-Jan-26 11:05 UTC
[syslinux] Embedding com32 modules and ldlinux.sys into one file
> -----Original Message----- > From: Syslinux [mailto:syslinux-bounces at zytor.com] On Behalf Of Paulo > Alcantara via Syslinux > Sent: Monday, January 25, 2016 11:30 PM > To: Tal Lubko via Syslinux > Cc: 'H. Peter Anvin' > Subject: Re: [syslinux] Embedding com32 modules and ldlinux.sys into > one file > > On Mon, 25 Jan 2016 22:50:24 +0200 > Tal Lubko via Syslinux <syslinux at zytor.com> wrote: > > > > -----Original Message----- > > > From: poma [mailto:pomidorabelisima at gmail.com] > > > Sent: Tuesday, January 19, 2016 1:30 PM > > > To: Tal Lubko; 'H. Peter Anvin'; 'Celelibi' > > > Cc: 'For discussion of Syslinux and tftp-hpa' > > > Subject: Re: [syslinux] Embedding com32 modules and ldlinux.sys > into > > > one file > > > > > > On 19.01.2016 09:07, Tal Lubko via Syslinux wrote: > > > ... > > > > > > > 1) Exposing the bootloader in the BIOS as a (readonly) disk drive > > > using standard BIOS or EFI interfaces (hpa suggestion). > > > > This suggestion looks very promising. It probably requires some > > > changes in the BIOS. I'm not sure if it requires changes in the > > > bootloader. > > > > There is one potential problem I see: the bootloader is stored on > > > some flashrom chip and the Linux image is stored on a different > > > storage device. > > > > I think that right now the bootloader assumes they are stored on > > > > the > > > same storage device. Am I wrong? > > > > If I'm wrong, how do I tell the bootloader to load the Linux > image > > > from a different storage device? > > > > > > > > > > MultiFS pro tempore with QEMU/SeaBIOS only > > > http://bugzilla.syslinux.org/show_bug.cgi?id=67 > > > > > > > Hi Poma > > > > I'm trying to test MultiFS support but not sure how to do it. > > How do I apply the MultiFS patch? > > > > I've seen some e-mails talking about integrating it some branches but > > I'm not sure it we done. > > The patchset can be found at my repo: > > git://git.zytor.com/users/pcacjr/syslinux.git multifs-for-upstream > > I should push it out to a separate branch on the official repo soon as > it was proposed before. > > Thanks, > > Paulo > > -- > Paulo Alcantara, HP Inc. > Speaking for myself only. > _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinuxHi I got it this way: git clone git://git.zytor.com/users/pcacjr/syslinux.git git checkout origin/multifs-for-upstream I've built it for BIOS system (make bios) and it seems to be working !!! If I understand the syntax correct, it is: (hdX,Y)/path/to/file", where X is disk number and Y is partition number. As far as I understand X and Y are zero based. I've tested it with qemu and 2 disks: - the first with bootloader - the second with kernel+rootfs I've used the following configuration file label: label MULTIFS KERNEL (hd1,1)/mfs/bzImage APPEND root=/dev/ram0 initrd=(hd1,1)/mfs/rootfs.ext2 ramdisk_size=65536 quiet I've also tried to load kernel from one disk and rootfs from another disk and it also seems to be working. Thanks for the help, Tal
Possibly Parallel Threads
- Embedding com32 modules and ldlinux.sys into one file
- Embedding com32 modules and ldlinux.sys into one file
- Embedding com32 modules and ldlinux.sys into one file
- Embedding com32 modules and ldlinux.sys into one file
- Embedding com32 modules and ldlinux.sys into one file