mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: ptxdist@pengutronix.de, Matthias Klein <matthias.klein@optimeas.de>
Subject: Re: [ptxdist] OSELAS Toolchain for i.MX 6UltraLite MCIMX6G2
Date: Wed, 11 Apr 2018 11:42:44 +0200	[thread overview]
Message-ID: <1523439764.4981.13.camel@pengutronix.de> (raw)
In-Reply-To: <em474a7e45-a474-443e-89d6-486d8c07ba4c@nb-mak>

Hi Matthias,

Am Mittwoch, den 11.04.2018, 09:26 +0000 schrieb Matthias Klein:
> Hello,
> 
> we are using the OSELAS Toolchain 2014.12.2 in the "arm-v7a-linux-
> gnueabihf" variant for the NXP i.MX6S7 and NXP i.MX6QP7.
> 
> Can we use this existing Toolchain and the PTXdist project also for
> the i.MX 6UltraLite MCIMX6G2?
> 
> 
> In other words: do we need only a different device tree (and a kernel
> which supports the CPU/Board), or do we need a different Toolchain
> (and different PTXdist project)?

Yes, both CPUs are compatible. The only difference regarding the
toolchain/platform is that the Cortex-A7 on the MX6UL supports vfp-v4,
while the Cortex-A9 on the older i.MX6 variants only supports vfp-v3.

The generic arm-v7a toolchain will not use the newer vfp version by
default, but it's something to keep in mind. Just don't add vfp-v4 to
the platform toolchain options in the BSP and you should be fine.

Regards,
Lucas

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2018-04-11  9:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-11  9:26 Matthias Klein
2018-04-11  9:42 ` Lucas Stach [this message]
2018-04-11  9:45   ` Matthias Klein

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=1523439764.4981.13.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=matthias.klein@optimeas.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