mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] ptxdist with iMX6
Date: Thu, 2 Mar 2017 17:31:02 +0100	[thread overview]
Message-ID: <20170302163101.GQ17911@falbala.home.lespocky.de> (raw)
In-Reply-To: <CABDcavaFGrwGxFuozM0e+V5owQ3=gUkqgSYU7bM-VzgodZauDA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1558 bytes --]

Hei hei,

On Thu, Mar 02, 2017 at 03:50:19PM +0100, Guillermo Rodriguez Garcia wrote:
> 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).

I would go with a recent vanilla kernel first. i.MX6 support is quite
mature these days. Maybe you have to write your own DTS file or adapt
another, but this should at least bring you to a running board with
serial console. That's a good start.

> > 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:

Sorry, I'm not familiar with toolchain details. As far as I can tell
ptxdist uses more or less generic toolchains which should work for a
wider range of boards. If you want to squeeze the last bit of
performance you may want to configure and build your own toolchain or
have a look at another project, but just using the above should
certainly be enough if you don't have very tight performance
requirements.

Greets
Alex

-- 
»With the first link, the chain is forged. The first speech censured, 
the first thought forbidden, the first freedom denied, chains us all 
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: C28E E6B9 0263 95CF 8FAF  08FA 34AD CD00 7221 5CC6 ***

[-- Attachment #1.2: Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 91 bytes --]

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  parent reply	other threads:[~2017-03-02 16:31 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     ` Alexander Dahl [this message]
2017-03-08 10:34     ` [ptxdist] ptxdist with iMX6 Michael Olbrich

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=20170302163101.GQ17911@falbala.home.lespocky.de \
    --to=post@lespocky.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