All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/3] pru-sample: add sample PRU application
Date: Sun, 27 Nov 2016 14:47:31 +0100	[thread overview]
Message-ID: <20161127144731.18bd30cb@free-electrons.com> (raw)
In-Reply-To: <CAK8F28mHwYonzL1Wx052TXCzd3U4TjvfQiMPuqxuQmRBLv-2zg@mail.gmail.com>

Hello,

On Sun, 27 Nov 2016 07:41:23 -0500, Ash Charles wrote:

> >  The intention here was not to create a new package, but rather to allow the
> > installation of the examples provided in pru-software-support. I.e. add a config
> > option "PRU_SOFTWARE_SUPPORT_INSTALL_EXAMPLES". Or rather, add a
> > pru-software-support target package for the examples (the firmware files are to
> > be installed on the target so it has to be a target package).  
> Okay.  How best to implement this?  Currently, I have
> PRU_SOFTWARE_SUPPORT as a host package (Config.in.host) as previously
> discussed. 

Why is pru-software-support a host package? It really builds/installs
things for the target, even if the target is the PRU and not the ARM.

Was it made a host tool after a discussion with Arnout?

> In the same directory, I can add a PRU_SOFTWARE_EXAMPLES
> Config.in for a target package that depends on the host package i.e. a
> user will select PRU support and then, if they wish, can choose to
> include the examples pack for their target.  Then, I just need to add
> some steps to the existing makefile to build out the examples too.

I would say pru-software-support should be a target package, with the
main option installing the "libraries", and a sub-option to enable the
examples.

> >  Obviously, only 1 firmware binary can be installed. So you have the following
> > options:
> > - Support only one example.
> > - Add config options for all the examples and let the user select it.
> > - Install examples, but not as am335x-pru0-fw, but in a pru-examples
> > subdirectory, leaving it up to the user to copy/link it to the correct name for
> > firmware loading. Mention in the help text how to do that.  
> What is the best place for the examples directory tree to be installed
> /opt/pru-examples?

/usr/share/pru-software-support/ I'd say.

> Is it reasonable to support users who wish to select their desired
> example firmware before filesystem creation (firmware can be loaded
> directly on boot & maybe they have a read-only rootfs) rather than on
> first boot?  I think this means they'd have to make the copy in the
> output/target directory and then rerun make to finalize the rootfs.
> What is the best way to give a user instructions? (Sorry for all the
> questions...buildroot neophyte)

You can give some details by writing a readme.txt in
package/pru-software-support/.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-11-27 13:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-16 19:24 [Buildroot] [PATCH 1/2] ti-cgt-pru: add package for PRU Host toolchain Ash Charles
2016-11-16 19:24 ` [Buildroot] [PATCH 2/2] ti-pru-support: add staging files for PRU firmware Ash Charles
2016-11-24 15:48   ` Thomas Petazzoni
2016-11-24 20:25   ` Arnout Vandecappelle
2016-11-21 23:51 ` [Buildroot] [PATCH 1/2] ti-cgt-pru: add package for PRU Host toolchain Ash Charles
2016-11-24 15:44 ` Thomas Petazzoni
2016-11-24 20:16   ` Arnout Vandecappelle
2016-11-24 20:07 ` Arnout Vandecappelle
2016-11-25 17:49 ` [Buildroot] [PATCH v2 1/3] " Ash Charles
2016-11-25 17:49   ` [Buildroot] [PATCH v2 2/3] pru-software-support: add library for PRU firmware Ash Charles
2016-11-26 11:27     ` Arnout Vandecappelle
2016-11-26 14:05       ` Thomas Petazzoni
2016-11-26 14:34         ` Ash Charles
2016-11-25 17:50   ` [Buildroot] [PATCH v2 3/3] pru-sample: add sample PRU application Ash Charles
2016-11-25 20:30     ` Thomas Petazzoni
2016-11-26 11:22     ` Arnout Vandecappelle
2016-11-26 14:06       ` Thomas Petazzoni
2016-11-27 12:41       ` Ash Charles
2016-11-27 13:47         ` Thomas Petazzoni [this message]
2016-11-28 11:34           ` Ash Charles
2016-11-29 23:41             ` Arnout Vandecappelle
2016-11-30  1:12               ` Ash Charles
2016-11-26 11:07   ` [Buildroot] [PATCH v2 1/3] ti-cgt-pru: add package for PRU Host toolchain Arnout Vandecappelle
2016-11-26 14:51     ` Ash Charles

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=20161127144731.18bd30cb@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.