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 16:58:43 -0400 [thread overview]
Message-ID: <200804211658.44036.vapier@gentoo.org> (raw)
In-Reply-To: <20080421194514.A886224764@gemini.denx.de>
On Monday 21 April 2008, Wolfgang Denk wrote:
> In message <200804211444.43917.vapier@gentoo.org> you wrote:
> > > 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.
>
> OK. I offered you a way out. It's your decision.
>
> I tried understanding what you are trying to do, and even though I
> feel it's not exactly an important or frequently used feature for
> most of the users I tried to come up with a compromize that allows
> you to do what you want to do without hurting others and without
> polluting the command name space.
i consider the cache one aspect of it. the users shouldnt have to know "oh i
gotta turn off cache", they just have to know "i'm loading up my code and
it's going to take over the system". that is why a "-noret" flags makes
sense instead of trying to break down specific aspects. also adding a myriad
of cache options to one function achieves the same thing as doing:
dcache off; icache off; go <address>
> > > 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.
>
> You have a really, really funny way of deciding what matters and what
> not. All the things you have in mind do matter (even if they are
> documented to be unsupported), while other existing and legal ways of
> doing things don't matter. That doesn't make working with you an easy
> task.
it's really quite simple. the need is to jump to an address to execute a blob
and never return to u-boot. what features are available to standalone u-boot
applications (while useful) dont really matter. such applications rely on
u-boot remaining resident which is the opposite of what i'm talking about.
-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/46d3f3e1/attachment.pgp
next prev parent reply other threads:[~2008-04-21 20:58 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
2008-04-21 19:45 ` Wolfgang Denk
2008-04-21 20:58 ` Mike Frysinger [this message]
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=200804211658.44036.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