From: Steve Brueggeman <xioborg@yahoo.com>
To: "Lars Unin" <lars_unin@linuxmail.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What are .s files in arch/i386/boot
Date: Mon, 09 Jun 2003 16:06:01 -0500 [thread overview]
Message-ID: <mkt9evc8eossmephq3675ep0u0e73h690l@4ax.com> (raw)
In-Reply-To: <20030609153039.1427.qmail@linuxmail.org>
Not sure, but I think this is what you want.
http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/Linux-Init-HOWTO.html
Steve Brueggeman
On Mon, 09 Jun 2003 23:30:38 +0800, you wrote:
>From: Mark Hahn <hahn@physics.mcmaster.ca>
> > > > What are .s files in arch/i386/boot, are they c sources of some sort?
>>
>> no. is there some reason you can't just look at them?
>>
>> > > > Where can I find the specifications documents they were made from?
>> > >
>> > > There are not c files.
>> > > They are assembler files
>>
>> .s files are versions of .S files that have been run through cpp (gcc -E).
>> you can know this simply by looking at the makefiles or watching a build,
>> or by looking at the .s file and noticing the #line directives.
>>
>> > > Try running gcc on a c file with the -S option
>> > > it will generate the same then you can tweak the
>> > > assembler produced to make it faster.
>>
>> that's useful advice, but irrelevant in this case.
>>
>> > Where can I find the .c files they were made from,
>>
>> they aren't.
>>
>> > and the spec sheets the .c files were made from?
>>
>> what the heck is a "spec sheet"?
>
>I mean where can I find the information from which
>
>"* It then loads 'setup' directly after itself (0x90200), and the system
> * at 0x10000, using BIOS interrupts. "
>-- bootsect.S
>
>The ability to know how to get the BIOS to do that comes from, e.g. a
>book that can tell me how to do that without taking another degree...
>Where the information can be found, that says what BIOS memory
>area 0x90200 is for etc.
next prev parent reply other threads:[~2003-06-09 20:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 15:30 Lars Unin
2003-06-09 21:06 ` Steve Brueggeman [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-09 15:37 Lars Unin
2003-06-07 18:54 Lars Unin
2003-06-07 20:05 ` James Stevenson
2003-06-07 19:32 ` Sean Neakums
2003-06-07 21:27 ` H. Peter Anvin
2003-06-08 20:04 ` Jos Hulzink
2003-06-08 21:41 ` Shawn
2003-06-09 1:38 ` Horst von Brand
2003-06-07 18:36 Lars Unin
2003-06-07 19:50 ` James Stevenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mkt9evc8eossmephq3675ep0u0e73h690l@4ax.com \
--to=xioborg@yahoo.com \
--cc=lars_unin@linuxmail.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®