On Saturday 07 Jun 2003 23:27, H. Peter Anvin wrote:
> Followup to: <email@example.com>
> By author: Sean Neakums <firstname.lastname@example.org>
> In newsgroup: linux.dev.kernel
> > James Stevenson <email@example.com> writes:
> > >> > > What are .s files in arch/i386/boot, are they c sources of some
> > >> > > sort? Where can I find the specifications documents they were made
> > >> > > from?
> > >> >
> > >> > There are not c files.
> > >> > They are assembler files
> > >> >
> > >> Where can I find the .c files they were made from,
> > >> and the spec sheets the .c files were made from?
> > >
> > > You would have to find the original author of the person
> > > who tweaks the assembler in the .s file chances are the .c
> > > file is long gone though.
> > If there were ever C files to begin with. It's not unheard-of for
> > people to write assembler code from scratch.
> The ones in the Linux kernel were all written from scratch.
And for a very good reason. A few things really need asm, for example getting
a CPU in protected mode, setting up the MMU and stuff. Once they are set up,
you can use C, though sometimes you must be really sure what your compiler
will make from the C.
So, why assembly ? Cause it is needed. Why in arch/i386/boot ? for if it is
well done there, it isn't needed at many other locations. A few things will
still require asm though, therefore you'll find more .s files in arch/i386.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jun 15 2003 - 22:00:19 EST