From: Angolini Daiane-b19406 <b19406@freescale.com>
To: Pierre Eliotec <pierre.eliotec@gmail.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: vpu on imx6 solo
Date: Tue, 12 Aug 2014 12:14:56 -0300 [thread overview]
Message-ID: <53EA2F70.10405@freescale.com> (raw)
In-Reply-To: <CANZO_85QLkbGw2Agbi+-V=FV4sDGQbt3cdqAvgt0CcW2T6Rb=Q@mail.gmail.com>
On 12-08-2014 12:18, Pierre Eliotec wrote:
> hello,
>
> I tried this image with the same result (Illegal instruction)
> I am on daisy, I made no change on the toolchain. Compared to the
> imx6solosabresd, i just changed the uart line to match my board:
> SERIAL_CONSOLE = "115200 ttymxc1"
I think Illegal Instruction error is more regarding binary
incompatibility than IP incompatibility
I mean, I would expect another kind of error in case it is a dts mismatch.
> Then, I made changes in the device tree to disable all the IPs I'm not
> using, enabling hdmi output only and enabling uart2.
> Are the imx6solo and imx6dl VPU completely identical?
The difference is number of cores and amount of RAM memory. And those
are covered by the machine conf files in meta-fsl-arm
However I don't have a mx6solo machine I can test, anyway
Daiane
next prev parent reply other threads:[~2014-08-12 15:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 10:15 vpu on imx6 solo Pierre Eliotec
2014-08-12 11:14 ` Angolini Daiane-b19406
2014-08-12 11:47 ` Pierre Eliotec
2014-08-12 13:00 ` Fabio Estevam
2014-08-12 13:14 ` Angolini Daiane-b19406
2014-08-12 13:33 ` Pierre Eliotec
2014-08-12 14:17 ` Angolini Daiane-b19406
2014-08-12 15:18 ` Pierre Eliotec
2014-08-12 15:14 ` Angolini Daiane-b19406 [this message]
2014-08-12 16:37 ` Angolini Daiane-b19406
2014-08-22 6:48 ` Pierre Eliotec
2014-08-22 13:00 ` Daiane Angolini
2014-08-26 12:59 ` Pierre Eliotec
2014-08-12 13:35 ` Fabio Estevam
2014-08-12 13:40 ` Angolini Daiane-b19406
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=53EA2F70.10405@freescale.com \
--to=b19406@freescale.com \
--cc=meta-freescale@yoctoproject.org \
--cc=pierre.eliotec@gmail.com \
/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.