From: Nikita Yushchenko <nyushchenko@dev.rtsoft.ru>
To: Otavio Salvador <otavio@ossystems.com.br>,
Fabio Estevam <fabio.estevam@freescale.com>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
Gennady Kuznetsov <kuznetsovg@dev.rtsoft.ru>
Subject: Re: smarc-samx6i board support
Date: Fri, 12 Dec 2014 11:22:10 +0300 [thread overview]
Message-ID: <548AA5B2.1020209@dev.rtsoft.ru> (raw)
In-Reply-To: <CAP9ODKpQAYFoDVznr=N3v8o0zZK8yOj7OYrJh=ouUeZXyqNLjQ@mail.gmail.com>
Hello Otavio
Thanks for you replies.
I'm taking a time out to port my code to yocto master / 3.10.31 kernel,
to prepare u-boot recipe and to address issues discussed in the mail.
> Did you try to coordinate this effort with the vendor itself?
Yes, we work with Kontron on "official" BSP.
>> *) Support for hardware variations.
> ...
> If you ask me what would be the ideal solution I'd say it'd be to use
> the recently added U-Boot SPL support (in U-Boot 2014.10 it has
> support, use master from DENX for now work) as it would allow you to
> use a single image and boot the Quad, Dual, DualLite and Solo variants
> in a single image.
Hmm... could you provide a bit more details on this?
Does SPL stand for "secondary program loader"? How does this relate to
having single image for different hw configs?
>> *) Display selection
>> ...
> Take a look at how Boundary Devices has solved this. Their solution is
> the most user-friendly one IMO.
Do you mean what is described here -
http://boundarydevices.com/configuring-i-mx6-machines-different-screens-nitrogen6x-sabre-lite/
?
I still do not understand how this correlates with configuring displays
in device tree (just overrides it? then, what for to have display
configuration in device tree at all?)...
Nikita
next prev parent reply other threads:[~2014-12-12 8:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 13:00 smarc-samx6i board support Nikita Yushchenko
2014-12-08 13:33 ` Otavio Salvador
2014-12-12 8:22 ` Nikita Yushchenko [this message]
2014-12-12 12:58 ` Otavio Salvador
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=548AA5B2.1020209@dev.rtsoft.ru \
--to=nyushchenko@dev.rtsoft.ru \
--cc=fabio.estevam@freescale.com \
--cc=kuznetsovg@dev.rtsoft.ru \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@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.