From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Ashwin Kirpalani <akcooper8@gmail.com>
Cc: meta-freescale@yoctoproject.org
Subject: Re: Pulling down linux imx kernel in yocto
Date: Tue, 12 Mar 2013 15:12:09 -0700 [thread overview]
Message-ID: <513FA839.2030703@boundarydevices.com> (raw)
In-Reply-To: <CALmQvZS5rRhuj_q5HwBOMrnUDFp6uzQSFmpT8yRMgkTyQdjwsw@mail.gmail.com>
On 03/12/2013 01:39 PM, Ashwin Kirpalani wrote:
> This is sort of a beginner question but I need clarification. I have
> successfully build the fsl-image-gui using steps from
> https://community.freescale.com/docs/DOC-94024 for the sabrelite imx6
> board and would like to add a device driver for a camera and/or lcd.
>
> How do I pull down the linux-imx kernel source such that I can add my
> driver, run menuconfig and build the kernel using bitbake.
>
> Much appreciate the help!
>
Hi Ashwin,
This should be a simple matter of grabbing the sources (using git),
setting your toolchain PATH, and running the compile.
Note that you might want to grab the kernel configuration from a
device running Yocto as a starting point. There are some bits
included in the Yocto configuration that will be useful
(including single-touch selection for Hannstar display and
I believe some udev-related updates from Fabio).
You can grab the kernel configuration out of /proc/config.gz on
a running system, and gunzip it into your kernel source tree as
file name ".config" to get an identical starting point.
There must be an easier way to access the Yocto-built cross compiler,
but it appears on my system under:
~/yocto/build/tmp/sysroots/x86_64-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc
Regards,
Eric
next prev parent reply other threads:[~2013-03-12 22:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 20:39 Pulling down linux imx kernel in yocto Ashwin Kirpalani
2013-03-12 22:12 ` Eric Nelson [this message]
2013-03-13 0:40 ` Eric Nelson
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=513FA839.2030703@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=akcooper8@gmail.com \
--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.