Hi Rafael,

I believe that, with a little more effort, this guy would have
succeeded at adding a new floppy format. A bit later I'm going to
extend KolibriOS floppy with more cool stuff, and it could go from
1.44MB to beyond 2.88MB even with the compression is used (so wouldn't
fit even into the largest currently supported floppy). However I'm not
afraid and think it could be done easily. And you could quickly debug
it using QEMU, maybe he was trying it only at real hardware and this
was time consuming... Just make a special coreboot+SeaBIOS build for
QEMU and add a floppy there.

Best regards,
Mike Banon

On Fri, Apr 12, 2019 at 9:39 PM Rafael Send <flyingfishfinger@gmail.com> wrote:
>
> Hi,
> I'm working on stuffing a bootable Linux distro into coreboot.  In QEMU I already succeded by using coreboot's built-in kernel loading mechanism, but that's without SeaBIOS.
>
> I'd love to have it as a SeaBIOS payload so I can also boot other things, but I guess I'd have to create a custom-sized floppy image for this or figure out how to create an ELF payload out of a Linux kernel (I'm open to either, but I wasn't able to find any documentation on the ELF method).
>
> The guy who put Win 3.1 in coreboot attempted the floppy method, but according to his article he did not find success with this method due to unknown and complex issues in the floppy-side logic of SeaBIOS.
>
> So, I'm making the question explicit: What would it take to support custom-sized floppy images? In particular, I'm thinking of a 16MB device...
>
> Alternatively, would it be possible to create an ELF file out of a Linux kernel+initrd / bootable image?
>
> Cheers,
> Rafael
> _______________________________________________
> SeaBIOS mailing list -- seabios@seabios.org
> To unsubscribe send an email to seabios-leave@seabios.org