public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dennis Ruffer <daruffer@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Standalone API
Date: Sun, 7 Nov 2010 13:36:02 -0800	[thread overview]
Message-ID: <000601cb7ec3$c82ff620$588fe260$@com> (raw)
In-Reply-To: <3E0B820A-7A5F-41F9-B7CD-EA4B502A87C0@electrans.com>

Replies inline below...

> -----Original Message-----
> From: Andrew Holt (SE) [mailto:andrew.holt at electrans.com]
> Sent: Sunday, November 07, 2010 12:44 PM
> To: Dennis Ruffer
> Cc: 'U-Boot List'
> Subject: Re: [U-Boot] Standalone API
> 
> Hi,
> 
> I hadn't, but I will, Thanks.
> 
> I did find include/exports.h

That's where the document points you to anyway.

> Another question would be, I guess exports.h holds a subset of routines
> that 'could' be called by a standalone.  Is there a list of potential
> candidates ?

If it's not in exports.h you can't call it, but you can add anything that
follows the rules.

> Can you give me any guidance with regard to implementing the U-Boot API
> on SuperH ?

Not really.  I'm working on ARM and I haven't even written a standalone
program myself yet.  I've simply looked at it enough to have a good idea how
to do it and I was working with a standalone program that someone else had
written which didn't use any calls into uboot.  So, I know it's possible.

> What are the licences implications of a standalone calling these things
> ?

I'm not a lawyer, but I imagine that if you call u-boot routines, you still
have to comply with their license.

> Thanks for your help, it's good to know there is somebody out there :)

My impression is that most are in the far east, so I suspected you might not
get many replies until tomorrow.

I'm not really one of the official maintainers, but they might be able to
help you on a SuperH.

DaR

> Regards,
> Andrew
> 
> On 7 Nov 2010, at 15:53, Dennis Ruffer wrote:
> 
> >> From: u-boot-bounces at lists.denx.de [mailto:u-boot-
> >> bounces at lists.denx.de] On Behalf Of Andrew Holt (SE)
> >> Is there a list, or header file containing prototypes of the U-Boot
> >> facilities that a standalone can make use of ? If so can somebody
> >> please direct me to it
> >>
> >> Regards,
> >> Andrew
> >> P.S. Also can somebody just responds anyway as a test.  I'm not sure
> >> that my messages are getting out there.
> >
> > Did you read doc/README.standalone?
> >
> > DaR
> >
> >
> 
> =============================
> Andrew Holt
> Senior Software Engineer
> 
> Email: andrew.holt at electrans.com
> 
> Questions are a burden to others; answers a prison for oneself.
> =============================
> 
> 

  reply	other threads:[~2010-11-07 21:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-07 15:42 [U-Boot] Standalone API Andrew Holt
2010-11-07 15:53 ` Dennis Ruffer
2010-11-07 20:44   ` Andrew Holt
2010-11-07 21:36     ` Dennis Ruffer [this message]
2010-11-07 22:17     ` Peter Tyser

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='000601cb7ec3$c82ff620$588fe260$@com' \
    --to=daruffer@gmail.com \
    --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