From: "Dominic Sacré" <dominic.sacre@gmx.de>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>,
Daiane Angolini <daiane.list@gmail.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: imx6dl-riotboard: Does not generate valid SD card image
Date: Tue, 9 Aug 2016 18:26:12 +0200 [thread overview]
Message-ID: <57AA0424.3060500@gmx.de> (raw)
In-Reply-To: <CAP9ODKq+p9xV0aQYEv09sdUhzTOVhc-gu7tHJeHU1uMZ8p-6mg@mail.gmail.com>
On 2016-08-09 17:55, Otavio Salvador wrote:
> On Tue, Aug 9, 2016 at 12:36 PM, Daiane Angolini <daiane.list@gmail.com> wrote:
>> On Tue, Aug 9, 2016 at 11:47 AM, Turab Iqbal <turab_@hotmail.co.uk> wrote:
>>> The solution that worked for me was to add the following to
>>> meta-fsl-arm-extra/conf/machine/imx6dl-riotboard.conf:
>>> SOC_FAMILY = "mx6:mx6dl"
>>>
>>> I don't know if this is the most appropriate fix, though, which is why I'm
>>> not submitting a patch.
>>
>> The very same happens with imx6sl-warp, but NOT with imx7s-warp
>>
>> I was not able to find time to debug the image_types_fsl class so far
>> (but it's in my endless task list)
>
> The SoC family solution works but will break other things as it will
> enable the i.MX specific patches and support.
>
> I think we need to find other alternative to fix the issue.
What kind if things would break when setting SOC_FAMILY = "mx6:mx6dl"?
Why wouldn't riotboard be "part of the family"?
I've been using a modified riotboard machine config for some time, in
which I set SOC_FAMILY so that I can run linux-fslc-imx on riotboard.
Also the board seems to get the wrong DEFAULTTUNE unless SOC_FAMILY is
set ("armv7a-neon", should be "cortexa9thf-neon").
Dominic
next prev parent reply other threads:[~2016-08-09 16:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 14:47 imx6dl-riotboard: Does not generate valid SD card image Turab Iqbal
2016-08-09 15:36 ` Daiane Angolini
2016-08-09 15:55 ` Otavio Salvador
2016-08-09 16:26 ` Dominic Sacré [this message]
2016-08-09 16:47 ` Otavio Salvador
2016-08-09 16:59 ` Fabio Estevam
2016-08-09 17:04 ` Otavio Salvador
2016-08-09 17:10 ` Fabio Estevam
2016-08-09 17:12 ` Otavio Salvador
2016-08-09 17:40 ` Fabio Estevam
2016-08-09 17:55 ` 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=57AA0424.3060500@gmx.de \
--to=dominic.sacre@gmx.de \
--cc=daiane.list@gmail.com \
--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.