Hi, Are you still interested in getting this merged? If you are, please let us know. We'd need you to submit a patch to the list in that case (external URLs are problematic). Don't worry if it's not up-to-date, for initial review it should be OK.
On Sun, Nov 25, 2007 at 09:10:29PM +0200, UrJiZ wrote: > Hi, > > On Nov 20, 2007 9:14 AM, Bean <bean12...@gmail.com> wrote: > > Hi, > > > 1, use gas syntax, it's not that much source, just convert it. > > 2, don't embed core.img, instead compile header seperately, and create > > the rom image by catenating the header and core.img > > 3, Use romchk to zero-pad the rom to 64K, and fix the checksum. It can > > be quite useful if it can also configure runtime variables like the > > hotkey and timeout. > > > > Here's some list on what i've done: > - converted the code to gas syntax... (I don't really get why, NASM is > so much better in bootloader-like things...) > - modified grub-mkrom to be able to compile it (dunno whether the > current cpp + as + ld is the correct way, but it works) > - added static offsets in image for the runtime variables... > - modified romchk to be able to modify 'em > - added grub-mkrom to be able to pass the variables to romchk (also > has --help now) > - added a tiny clean-binaries script ... it's just replacing "make > clean" for now. > > And here's the new archive: > http://88.193.31.35:8080/urjaman/romboot2.tar.gz (or > http://rapidshare.com/files/72238464/romboot2.tar.gz.html ). > > Any comments are welcomed, good or bad. -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel