From: "Littlefield, tyler" <compgeek13@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: slightly o-t, looking for os help
Date: Wed, 7 Feb 2007 06:34:13 -0700 [thread overview]
Message-ID: <001601c74abc$a88bf4c0$6401a8c0@development> (raw)
In-Reply-To: <45C94881.6090904@proficio.ca>
Hello,
I tried Chris's idea, and I see a port where power should probably be on the
floppy drive.
Only thing, is I can't find a chord that goes to the power on the floppy.
Thanks,
Tyler Littlefield
Unlimited horizons head coder.
check out our website:
tysplace.homelinux.net
msn: compgeek134@hotmail.com
aim: st8amnd2005
skype: st8amnd127
----- Original Message -----
From: Doug Sutherland <doug@proficio.ca>
To: Speakup is a screen review system for Linux. <speakup@braille.uwo.ca>
Sent: Tuesday, February 06, 2007 8:33 PM
Subject: Re: slightly o-t, looking for os help
> If you are building an os for fun, it might be good to use
> an emulator rather than physical hardware. There are
> many around for example bochs will emulate the x86
> hardware, and there are others for ARM and countless
> other architectures.
>
> On x86 the BIOS will expect a bootloader in a the first
> sector of the first fixed drive. Then it does a bootloader
> chain from there to other bootloaders (ie linux lilo can
> boot initially then point to ntloader which loads windows).
> You have source available for various x86 bootloaders
> like lilo, grub, etc to peruse.
>
> On embedded systems there is fixed flash hardware
> and you can look at the source for u-boot, redboot,
> and many others.
>
> If you have not tried the linuxfromscratch exercise,
> that is very interesting, especially to understand how
> linux and the whole GNU toolchain works.
>
> http://www.linuxfromscratch.org/
>
> The way toolchains work for embedded is very much
> like the linuxfromscratch, except building smaller
> using tiny libraries (uclibc, newlib etc) and tiny
> executables (busybox and the like) and building for
> a different target architecture. There is something
> called crosstool to assist in building toolchains for
> different architectures. If its all for fun you could
> for example build an ARM toolchain and load onto
> virtual hardware (emulator) and it would be just
> like loading onto a PDA or phone.
>
> Just playing with linuxfromscratch can keep one busy
> for some time, getting into cross development tools
> can keep one busy for a very long time. Building your
> own OS from scratch, perhaps you should get someone
> to slide pizza under the door every once in a while :)
>
> -- Doug
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
Littlefield, tyler
` Doug Sutherland
` Littlefield, tyler
` Doug Sutherland
` Littlefield, tyler
` Littlefield, tyler [this message]
` Doug Sutherland
` Doug Sutherland
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='001601c74abc$a88bf4c0$6401a8c0@development' \
--to=compgeek13@gmail.com \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).