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 14:44:43 -0400 [thread overview]
Message-ID: <200804211444.43917.vapier@gentoo.org> (raw)
In-Reply-To: <20080421121312.5A8BF24764@gemini.denx.de>
On Monday 21 April 2008, Wolfgang Denk wrote:
> In message <200804210635.08416.vapier@gentoo.org> you wrote:
> > > go [ -cache={off,d-off,i-off,on,d-on,i-on} ] addr [ args ... ]
> >
> > cache is just an example. other arches may want to do other sort of
> > "system breakdown/cleanup" before relinquishing control. option flags to
> > commands
>
> As the situation is, other arches seem to be just fine as it. It's
> only BF which needs a pork sausage.
this is incorrect. any architecture which wants to overwrite u-boot sanely
needs to worry about causing exceptions or interrupts. i just want to make
the obvious easy since it has caused more than enough support requests.
> > really doesnt fit the style of u-boot (i expect that sort of painful
> > option parsing in redboot, not really u-boot).
>
> I don;t like it either, but just ading random new commands is even
> worse.
>
> > so we can do:
> > go [-noret] addr [args...]
>
> Ummm... "no return" programs is just an example. Other pograms may
> want to do other sort of "system breakdown/cleanup" before relin-
> quishing control.
>
> > or we can add "jump" to cmd_boot.c and merge the differences by just
> > using > a function pointer to "do_go_exec" or "do_jump_exec".
>
> Adn then we add "call" and "exec" and "do" and so oon just for other
> needed options? I say no.
then implement whatever. in the mean time i'll keep forking the Blackfin
code.
> > i never said Blackfin was the only thing that mattered. in fact, my goal
> > is to make it so that people using this facility get a more standard
> > initial environment before they start taking over the system. i guess i
> > wont point out the U-Boot policy about not using interrupts ...
>
> Are you aware that U-Boot does use interrupts here and there? That we
> actually provide functions to register interrupt handlers to
> standalone programs, etc. ?
yes i'm aware, but we arent talking about standalone applications here, so
those really dont matter.
-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/902f64c9/attachment.pgp
next prev parent reply other threads:[~2008-04-21 18:44 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
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 [this message]
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=200804211444.43917.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