From: Halil Demirezen <kernel@bilmuh.ege.edu.tr>
To: linux-newbie@vger.kernel.org
Subject: Re: FDC and compilation parameters.
Date: Sat, 22 May 2004 21:45:29 +0300 [thread overview]
Message-ID: <20040522184529.GA9545@bilmuh.ege.edu.tr> (raw)
In-Reply-To: <20040521053958.GA31128@bilmuh.ege.edu.tr>
Anyone there?
On Fri, May 21, 2004 at 08:39:58AM +0300, Halil Demirezen wrote:
> I am trying to write some test kernels to get the
> whole concept concrete. I am writing *.s and *.c
> codes all together. However, I could not find the
> exact CFLAGS to compile. Should I use -O2 or
> -fomit-frame-pointer...
>
> What do you offer me ? The kernel will be written in
> C ( some parts are asm) and there is no compression.
> I am linking it with using
>
> ld -Ttext 0x10000 -s --oformat binary -o test.bin test.o
>
> and writing it to the floppy as below:
>
> dd obs=512 seek=6 if=test.bin of=/dev/fd0
>
>
> However, there are some unexpected faults and the machine reboot.
> I am using I386 by the way ;).
>
> And can anyone tell me where I can find a good document telling
> how to program FDC. All the staff i found on net is confusing..
>
> Thanks.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2004-05-22 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-21 5:39 FDC and compilation parameters Halil Demirezen
2004-05-22 18:45 ` Halil Demirezen [this message]
2004-05-23 6:50 ` pa3gcu
2004-05-23 19:26 ` Halil Demirezen
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=20040522184529.GA9545@bilmuh.ege.edu.tr \
--to=kernel@bilmuh.ege.edu.tr \
--cc=linux-newbie@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