i'm trying to chose format for my kernel.which one you suggest coff or elf.
i should say for which format it is easy to write a loader.
which format(elf or coff) is supported by djgpp .
coff or elf
-
EyeScream
RE:coff or elf
I suggest COFF.
COFF is very easy to parse, so the loader will be much easier to write. ELF is quite complicated and therefore not quite good for the kernel image itself. Moreover, DJGPP support for ELF is broken. COFF support is OK.
The trouble with COFF is that you can build it only with DJGPP. UNIX gcc versions (unfortunately) don't support COFF. The kernel I'm writing now (named Lone) is in COFF format. However, I have to first build an ELF image and then convert it to COFF (using a self-written tool).
COFF is very easy to parse, so the loader will be much easier to write. ELF is quite complicated and therefore not quite good for the kernel image itself. Moreover, DJGPP support for ELF is broken. COFF support is OK.
The trouble with COFF is that you can build it only with DJGPP. UNIX gcc versions (unfortunately) don't support COFF. The kernel I'm writing now (named Lone) is in COFF format. However, I have to first build an ELF image and then convert it to COFF (using a self-written tool).
-
Moose
RE:coff or elf
If you use the multiboot standard with a bootloader such as Grub, then the format does not matter too much, you use a header which can be generated from a file thats distributed with the multiboot specs at the top of your kernel. This header specifies all the info needed to boot with a multiboot compliant bootloader, such as Grub, and thus doesnt matter what format you use.
You can change it whenever you like.
Moose.
You can change it whenever you like.
Moose.
-
iub
RE:coff or elf
so you must have written loader for coff format.can you send me your loader for coff format.
here is my email address [email protected]
here is my email address [email protected]
-
Moose
RE:coff or elf
I doubt he's going to just hand over any code because you ask him too.
And since you're asking for someone elses loader, why dont you just use grub, it supports coff.
Moose.
And since you're asking for someone elses loader, why dont you just use grub, it supports coff.
Moose.
-
EyeScream
RE:coff or elf
Currently I use GRUB, native loader is planned for later time. Multiboot rulez =)
However, I _am_ going to give away my code for free as soon as it gets to some stage when it would have some (minor) value. As of now, too few bits are written.
If you wish, I may send the loader as soon as it is completed =)
However, I _am_ going to give away my code for free as soon as it gets to some stage when it would have some (minor) value. As of now, too few bits are written.
If you wish, I may send the loader as soon as it is completed =)
-
iub
RE:coff or elf
here are steps which i'll follow to load statically linked coff kernel.
1) i'll get no.of sections from coff file header
2)then i'll read initial entry point from a.out file header
3)by using the "section offset" fields,i'll load code,data and bss sections to desired physical addresses(pointed to by "physical addresses of sections" field in section header.
4)then i'll jump to initial entry point obtained from a.out header.
are these steps correct to load a statically linked coff kernel.
1) i'll get no.of sections from coff file header
2)then i'll read initial entry point from a.out file header
3)by using the "section offset" fields,i'll load code,data and bss sections to desired physical addresses(pointed to by "physical addresses of sections" field in section header.
4)then i'll jump to initial entry point obtained from a.out header.
are these steps correct to load a statically linked coff kernel.