All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikita Yushchenko <nyushchenko@dev.rtsoft.ru>
To: otavio.salvador@ossystems.com.br
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: Qt 5.4 on Kontron SMARC sAMX6i
Date: Wed, 9 Dec 2015 10:21:15 +0300	[thread overview]
Message-ID: <5667D66B.30004@dev.rtsoft.ru> (raw)
In-Reply-To: <CAP9ODKpXnJBDN1jbYZZZbjisNaKu2-TAUmQt96jWJM9MaHay9w@mail.gmail.com>

>> I have successfully got Qt 5.2.1 version running on Kontron SMARC sAMX6i
>> using the official Kontron Yocto patch. However, in order to use the newer
>> WebEngine component I need to upgrade to version 5.4. Anyone has some
>> experience building a newer version of Qt using SMARC?
> 
> Kontron I don't. It would be nice if you could push them to send the
> modules for merging on meta-fsl-arm.

Upstreaming smx6 support was blocked about a year ago by u-boot
question. Smx6 u-boot is separate project inside Kontron, with unclear
status, probably with non-public code inside. It is not part of linux
BSP; I actually had only binary while working on BSP.

As far as I got from year-old discussion in list, target without u-boot
can't be added to meta-fsl-arm-extra.


  reply	other threads:[~2015-12-09  7:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08 14:17 Qt 5.4 on Kontron SMARC sAMX6i Andreas Enbacka
2015-12-08 15:26 ` Otavio Salvador
2015-12-09  7:21   ` Nikita Yushchenko [this message]
2015-12-09 21:23     ` Fabio Estevam
2015-12-10  6:41       ` Nikita Yushchenko
2015-12-09  7:15 ` Nikita Yushchenko
2015-12-09  7:17 ` Nikita Yushchenko
     [not found] <mailman.7.1449604802.21095.meta-freescale@yoctoproject.org>
2015-12-09  7:37 ` marko.kenttala
2015-12-16 19:06   ` Andreas Enbacka

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=5667D66B.30004@dev.rtsoft.ru \
    --to=nyushchenko@dev.rtsoft.ru \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio.salvador@ossystems.com.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.