On 12/14/07, Dieter <[EMAIL PROTECTED]> wrote: > > nasm uses intel style iirc. gas(gnu assembler) uses at&t > > either way is ok with me. mostly just what order you put the args and > > a few minor punctuation differences iirc.
> I haven't messed with asm code for many years, but if it is just a syntax > difference, perhaps a utility could be written to convert from one to the > other? I think just going with nasm is the right answer even if it used order that some don't like. It's 6 of one; half a dozen of another. Not really worth futzing over. The real different between nasm and gas would be the directives. Also I think gas might be geared pretty heavy for being 32/64bit flat and outputing elf or other object files and not raw binaries. nasm might be a bit more flexible for what we'd need to do. and I haven't really used asm outside of gcc extended asm statements for awhile myself. 8 years ago -- custom boot sector that loaded a program that fit within first track of a floppy disk -- under 9k . > > Also what we really need is enough to boot linux, dos, and windows for > > the most part. > I think you misspelled BSD, OS-X and Plan-9. Pesky typos. Sure, solaris, (free|net|open)bsd, os x aka darwin aka YAbsd, linux, windows (xp|vista), hurd, qnx, plan-9, reactos. Frankly if you just test for windows and linux you already did more than some hardware vendors. so fedora, ubuntu, netbsd, solaris, darwin, windows xp, windows vista, centos, suse should cover it well enough. I think that they shouldn't be all that radically different anyway. hurd, qnx, plan-9, freedos, and reactos don't really need correcting for if the others work -- unless they point out a genuine bug or it's not too much of a problem to account for. Also first priority would be to get boot working. After it's up and running most of them will want to ignore the 32k midget driver anyway. Second priority would be to fill the 32k will whatever features that are part of the spec that we can. Also probably needs to be tested on more than one bios -- Award, American Megatrends (AMI) and Phoenix etc etc. They all would call both the setup code and the int 0x10 interface. For example someone mentioned that a bios generated logo was done by changing the fonts, so that needs to work. _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
