From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] ptxdist with iMX6
Date: Wed, 8 Mar 2017 11:34:39 +0100 [thread overview]
Message-ID: <20170308103439.bhmegjz4iq3sc25u@pengutronix.de> (raw)
In-Reply-To: <CABDcavaFGrwGxFuozM0e+V5owQ3=gUkqgSYU7bM-VzgodZauDA@mail.gmail.com>
Hi,
On Thu, Mar 02, 2017 at 03:50:19PM +0100, Guillermo Rodriguez Garcia wrote:
> 2017-03-01 22:03 GMT+01:00 Alexander Dahl <post@lespocky.de>:
> > Hei hei,
> >
> > On Wed, Mar 01, 2017 at 06:36:38PM +0100, Guillermo Rodriguez Garcia wrote:
> >> Is someone using ptxdist with iMX6 based targets? I know phytec used
> >> ptxdist in the past but now they seem to be using Yocto instead.
> >
> > We have a phytec i.MX6 dev board at work. They shipped a ptxdist based
> > BSP in the first place before they switched to ptxdist. I had
> > Distrokit working with it, I guess when Linux 3.18 was bleeding edge,
> > but did not manage to send it upstream.
> >
> > So in general i.MX6 works, I guess it's basically getting your
> > bootloader and kernel config working?
>
> Yes, indeed. Selecting the right kernel to start from is already a
> non-trivial task, given the plethora of options (we have at least:
> official Freescale/NXP kernels, community kernels, vendor kernels from
> board/SOM manufacturers, and the upstream kernel).
>
> >
> >> Re. toolchain: Any recommended version of OSELAS.Toolchain? Best
> >> settings to finetune for Cortex A9 + VFPv3 + NEON ?
> >
> > I would recommend the latest release v2016.06.1 and go with
> > arm-v7a-linux-gnueabihf_gcc-5.4.0_glibc-2.23_binutils-2.26_kernel-4.6-sanitized.ptxconfig
>
> That is a great start. Some things that draw my attention, though:
>
> - VFPv3-D16 selected whereas iMX6 can do VFPv3-D32 (or just "VFPv3")
> - NEON not enabled (supported by iMX6)
For the glibc this makes no real difference. It has neon optimizes memcpy
etc. that is selected at runtime. Maybe some math functions are slower, but
I've not heard of any issues there. For the BSP just set TARGET_EXTRA_CFLAGS
/ TARGET_EXTRA_CXXFLAGS to add the appropriate -mcpu/-mfpu.
> - Thumb mode used by default (not sure why -- wouldn't it be more
> appropriate to use arm mode by default unless there is an explicit
> intent to optimize size over speed ?)
For ARMv7 thumb means thumb2 and that is just as fast as arm mode but uses
less space. All bit distros use this as well.
Michael
--
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:[~2017-03-08 10:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 17:36 Guillermo Rodriguez Garcia
2017-03-01 21:03 ` Alexander Dahl
2017-03-02 14:50 ` Guillermo Rodriguez Garcia
2017-03-02 16:17 ` Clemens Gruber
2017-03-02 17:35 ` [ptxdist] GitHub and free software Uwe Kleine-König
2017-03-02 18:17 ` Guillermo Rodriguez Garcia
2017-03-02 18:19 ` Guillermo Rodriguez Garcia
2017-03-02 18:28 ` Clemens Gruber
2017-03-16 15:53 ` Clemens Gruber
2017-03-17 20:50 ` Roland Hieber
2017-03-18 6:01 ` Robert Schwebel
2017-03-02 16:31 ` [ptxdist] ptxdist with iMX6 Alexander Dahl
2017-03-08 10:34 ` Michael Olbrich [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=20170308103439.bhmegjz4iq3sc25u@pengutronix.de \
--to=m.olbrich@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