public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Blackfin: implement go/boote wrappers
Date: Mon, 21 Apr 2008 05:41:40 -0400	[thread overview]
Message-ID: <200804210541.41085.vapier@gentoo.org> (raw)
In-Reply-To: <20080421090325.6C85D24764@gemini.denx.de>

On Monday 21 April 2008, Wolfgang Denk wrote:
> In message <200804210349.27495.vapier@gentoo.org> you wrote:
> > > That makes no sense to me. If you want to boot some OS, use a "boot*"
> > > commands, not "go" or the like.
> >
> > i'm not talking about operating system code, i'm talking about flat
> > binary applications that run bare metal.  something like "u-boot.bin"
> > where it's just a binary blob that gets loaded and u-boot jumps to it and
> > never returns. since "go" isnt appropriate according to you (and seeing
> > as how none of the> boot commands are appropriate), then the only next
> > step is to implement a "jump" command that is exactly like "go" except it
> > doesnt return.
>
> This makes no sense. If it is ``exactly like "go"'' it doesn't matter
> if the code returns or not (and actually this is what I'm  trying  to
> point out all the time).

the obvious implication is that i would add the cache disabling hooks to the 
jump command instead of the go command since you wont allow the hook around 
go.

> It's just that "go" shall retain the standard U-Boot environment for
> application it runs, and that the applications need to take care if
> they need to meddle with interrupts, exception handlers, etc.

U-Boot sets up no interrupts and the only exceptions that occur on the 
Blackfin are for cache handling.  disabling the caches forces a sane 
environment where applications dont have to deal with a chicken/egg of having 
to setup exception handlers before taking an exception.  we've seen it 
already with customers.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20080421/1f91120b/attachment.pgp 

  reply	other threads:[~2008-04-21  9:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-19  5:45 [U-Boot-Users] [PATCH] Blackfin: implement go/boote wrappers Mike Frysinger
2008-04-20 23:38 ` Wolfgang Denk
2008-04-21  0:31   ` Mike Frysinger
2008-04-21  5:00     ` Wolfgang Denk
2008-04-21  5:25       ` Mike Frysinger
2008-04-21  7:26         ` Wolfgang Denk
2008-04-21  7:49           ` Mike Frysinger
2008-04-21  9:03             ` Wolfgang Denk
2008-04-21  9:41               ` Mike Frysinger [this message]
2008-04-21 10:07                 ` Wolfgang Denk
2008-04-21 10:35                   ` Mike Frysinger
2008-04-21 10:59                     ` Mike Frysinger
2008-04-21 12:14                       ` Wolfgang Denk
2008-04-21 12:13                     ` Wolfgang Denk
2008-04-21 18:44                       ` Mike Frysinger
2008-04-21 19:45                         ` Wolfgang Denk
2008-04-21 20:58                           ` Mike Frysinger
2008-04-21 22:19                             ` Wolfgang Denk
2008-04-21 23:08                               ` Mike Frysinger

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=200804210541.41085.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --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