From: Robert Schwebel <r.schwebel@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Difference between DIstroKit and OSELAS.BSP-Pengutronix-Generic
Date: Thu, 10 Dec 2015 07:18:19 +0100 [thread overview]
Message-ID: <20151210061819.GP30206@pengutronix.de> (raw)
In-Reply-To: <5668B211.2010806@gmail.com>
On Wed, Dec 09, 2015 at 11:58:25PM +0100, Alan Martinovic wrote:
> I'm trying to figure how DistroKit came to be and whats its relation
> with OSELAS.BSP-Pengutronix-Generic.
>
> Can you please comment/confirm if this is right (that is my current
> perspective):
>
> OSELAS.BSP-Pengutronix-Generic is the generic "directory structure"/"BSP
> project strucure" in which through the use of ptxdist the BSP is
> configured and built.
>
> DistroKit is OSELAS.BSP-Pengutronix-Generic which has a set of suggested
> platform configuration files for the popular boards (BeagleBone,
> VersatilePB, RaspberryPi, VExpress).
The "Generic" BSP is pretty old, while DistroKit is more or less a good
example for a fairly recent example BSP to start with.
> And an off topic question:
> Is the "How to become a PTXdist Guru - Pengutronix" available for public
> contribution, and if so, how?
Not yet; we have started to add Sphinx documentation support to PTXdist,
as we made good experiences with it for barebox; if you want to improve
the documentation, start there.
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2015-12-10 6:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 22:58 Alan Martinovic
2015-12-10 6:18 ` Robert Schwebel [this message]
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=20151210061819.GP30206@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=ptxdist@pengutronix.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