From: Gary Thomas <gary@mlbassoc.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Matt Sartori <msartori@hanoverdisplays.com>,
eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Simple Redboot Q's
Date: Tue, 26 Jul 2005 13:08:00 -0000 [thread overview]
Message-ID: <1122383307.27647.71.camel@hermes> (raw)
In-Reply-To: <20050726110508.GZ15048@lunn.ch>
On Tue, 2005-07-26 at 13:05 +0200, Andrew Lunn wrote:
> On Tue, Jul 26, 2005 at 11:16:15AM +0100, Matt Sartori wrote:
> > Does an application that is loaded and run by Redboot have to be linked
> > against the eCos libraries?
>
> No. eg your application could be Linux, which will simply take
> complete control of the hardware.
>
> > What provisions would be necessary to make this work (e.g.. you
> > obviously don't want your app to overwrite the rom area Redboot sits in)
> > and are there any examples of this out there?
>
> Look at how Linux is booted using RedBoot.
There is also pretty good support for building programs with
newlib. In this case, newlib uses facilities (such as terminal
I/O, etc) exported by RedBoot.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2005-07-26 13:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 10:16 Matt Sartori
2005-07-26 11:05 ` Andrew Lunn
2005-07-26 13:08 ` Gary Thomas [this message]
2005-07-26 13:20 Matt Sartori
2005-07-26 13:28 ` Andrew Lunn
2005-07-26 13:28 ` Gary Thomas
2005-07-26 14:52 Matt Sartori
2005-07-26 14:59 ` Gary Thomas
2005-07-26 15:55 Matt Sartori
2005-07-26 16:30 ` Andrew Lunn
2005-07-26 17:03 Matt Sartori
2005-07-26 17:21 ` Andrew Lunn
2005-07-27 11:17 Matt Sartori
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=1122383307.27647.71.camel@hermes \
--to=gary@mlbassoc.com \
--cc=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=msartori@hanoverdisplays.com \
/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).