From: Colin Moloney <cmoloney@mtdata.com.au>
To: meta-freescale@yoctoproject.org
Subject: Re: CLOCAL bit for console ttyAMA0 on imx28evk with 3.14 kernel
Date: Fri, 2 Jan 2015 07:10:32 +0000 (UTC) [thread overview]
Message-ID: <loom.20150102T075301-151@post.gmane.org> (raw)
In-Reply-To: 5461AF84.2000700@beamcommunications.com
Craig McQueen <craig.mcqueen@...> writes:
>
> I'm doing a Yocto build of core-image-minimal for imx28evk with
> linux-fslc kernel provider (thus 3.14.19 kernel).
>
... snip
>
> Regards,
> Craig McQueen
Hi Craig,
I want to do exactly the same thing but as a newcomer to Yocto I'm lost
in the mass of configuration.
In my extract of "repo init -u
https://github.com/Freescale/fsl-community-bsp-platform -b daisy" I can only
find the imx28evk under
"sources/meta-fsl-arm/recipes-kernel/linux/linux-imx-2.6.35.3" and only the
"mxs" under other ".../linux/linux-..." directories.
The 'machine/conf' file sources/meta-fsl-arm/conf/machine/imx28evk.conf
refers to conf/machine/include/mxs-base.inc which has:
PREFERRED_PROVIDER_virtual/kernel_mx23 ?= "linux-fslc"
but I get linux-imx-2.6.35.3 when I build.
Do you know where I can find an explanation of how to change the imx28evk
to a more recent kernel (3.14 or 3.10.17) ?
Regards
Colin Moloney
next prev parent reply other threads:[~2015-01-02 7:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 6:41 CLOCAL bit for console ttyAMA0 on imx28evk with 3.14 kernel Craig McQueen
2014-11-11 7:40 ` Nikolay Dimitrov
2014-11-11 16:05 ` Fabio Estevam
2014-11-11 16:11 ` Cary O'Brien
2014-11-11 17:42 ` Otavio Salvador
2014-11-11 17:46 ` Fabio Estevam
2014-11-11 17:53 ` Otavio Salvador
2014-11-11 23:00 ` Craig McQueen
2014-11-11 23:47 ` Otavio Salvador
2014-11-12 2:06 ` Craig McQueen
2015-01-02 7:10 ` Colin Moloney [this message]
2015-01-02 11:38 ` 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=loom.20150102T075301-151@post.gmane.org \
--to=cmoloney@mtdata.com.au \
--cc=meta-freescale@yoctoproject.org \
/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.