From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Need help booting an unsupported OS on ARM
Date: Sun, 13 Feb 2005 01:15:12 +0100 [thread overview]
Message-ID: <20050213001517.0AF6EC1430@atlas.denx.de> (raw)
In-Reply-To: Your message of "Sat, 12 Feb 2005 17:45:45 CST." <2da76b6505021215452596cc8a@mail.gmail.com>
In message <2da76b6505021215452596cc8a@mail.gmail.com> you wrote:
> I am trying to use U-Boot to start up a home grown OS. How can I make
> my OS a little more U-Boot friendly, or visa-versa? The specific
You can do both, but in general you don't have to.
The most trivial thing is to start your OS using the "go" command -
assuming that the OS does not require to receive any information from
the boot loader. Or, assuming the OS uses ELF files, you can use the
"bootelf" copmmand, too.
> problem I'm having is that when I issue a SWI on the arm, the U-Boot
> interrupt routines get used instead of mine.
Your OS is expected to install it's own interrupt handlers, of
course.
> I can see why that is happening because the vectors in the flash
> address point to the U-Boot routines, but I'm wondering if there is a
This is only before relocation.
> way to set a secondary jump so that my routines are used.
You may want to peek for example at the Linux kernel code how to
install your own interrupt handlers.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
In accord with UNIX philosophy, Perl gives you enough rope to hang
yourself. - L. Wall & R. L. Schwartz, _Programming Perl_
next prev parent reply other threads:[~2005-02-13 0:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-12 23:45 [U-Boot-Users] Need help booting an unsupported OS on ARM Rod Landers
2005-02-13 0:15 ` Wolfgang Denk [this message]
2005-02-13 18:36 ` Rod Landers
2005-02-14 22:44 ` Roger Larsson
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=20050213001517.0AF6EC1430@atlas.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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