From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] Ptxdist BSP for STM32MP15x SoC
Date: Mon, 2 Sep 2019 19:35:25 +0200 [thread overview]
Message-ID: <CABDcavZ94Maqb9mA3B3Z_B1Ky20uvXTYrs99WA1ujrh-2x54zQ@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 363 bytes --]
Hi all,
Is someone using ptxdist with STM32MP15x based targets? ST only supports
Yocto for this SoC.
Re. toolchain: Any recommended version of OSELAS.Toolchain? Any hints on
settings to finetune for this CPU? This is a single or dual Cortex A7
(depending on the actual p/n), and has NEON + VFPv4.
Thanks,
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com
[-- Attachment #1.2: Type: text/html, Size: 722 bytes --]
[-- Attachment #2: Type: text/plain, Size: 92 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2019-09-02 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 17:35 Guillermo Rodriguez Garcia [this message]
2019-09-02 21:25 ` Robert Schwebel
2019-09-03 8:39 ` Guillermo Rodriguez Garcia
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=CABDcavZ94Maqb9mA3B3Z_B1Ky20uvXTYrs99WA1ujrh-2x54zQ@mail.gmail.com \
--to=guille.rodriguez@gmail.com \
--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