Hi
How to add external driver (ex:TFT driver) to core-minimal-image.
After building core -minimal-image, in case I need to add additional package to
existing image, do i need to modify in .conf file and REBUILD IT..every
time ?
please clarify !
Thank you --
Create your own image recipe (hint: require another image, or just
copy it), that reduces the parse time. Creating the image usually takes
less than a minute.
You can also just build the new package and manually install it on the
target.
On 12/21/2014 11:07 AM, abhishek srivastava wrote:
I think I've worked this one out. It looks as if the kernel patch at
http://mailman.alsa-project.org/pipermail/alsa-devel/2013-October/067530.html
needs to be included so that the ValleyView HDMI codec is detected.
Adding it manually before compiling the kernel gives me audio over HDMI.
Chris
Hi,
I am building a system with yocto for a board which is similar to
Beagleboard-xM. So I used beagleboard as a starter. However, the kernel
is not booting. Uboot just tells me that he is starting the kernel and
then nothing happens any more.
So I guess there is something wrong with the pin
On 12/21 16:32, Fabian Schwartau wrote:
Hi,
I am building a system with yocto for a board which is similar to
Beagleboard-xM. So I used beagleboard as a starter. However, the kernel is
not booting. Uboot just tells me that he is starting the kernel and then
nothing happens any more.
So I
Am 21.12.2014 um 18:08 schrieb Maciek Borzecki:
On 12/21 16:32, Fabian Schwartau wrote:
Hi,
I am building a system with yocto for a board which is similar to
Beagleboard-xM. So I used beagleboard as a starter. However, the
kernel is
not booting. Uboot just tells me that he is starting
Hi,
I have the same requirement.
I will try it. But in my case I need to use this
https://launchpad.net/gcc-arm-embedded.
There are some way to yocto creates the gcc-arm-embedded SDK? Instead of
use the gcc-arm-embedded packages. Is it feasibly?
Thanks.
On 19/12/2014 11:21, Andrea
This mail was sent out by Package Report System.
This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade this time, they can fill in
RECIPE_NO_UPDATE_REASON_pn-xxx in upstream_tracking files to ignore this
recipe remainder until newer
This mail was sent out by Package Report System.
It will list all the recipes which can't check upstream version by script, and
will show how long it is since their last mannual version check.
You can check the detail information at
http://packages.yoctoproject.org/manuallychkinfo
PackageName
Hi guys,
Here's an update FYI. I have managed to get clang sort of working. It compiles
my sample code but I can't get the binary to execute. ./a.out simply returns:
./a.out: No such file or directory.
I'm sure that a.out exists and weirdly I could get the same binary file to run
on my build
Though it's not the same case, but I use yocto to build the android-system
with the prebuilt bionic toolchain shipped with android manifest.
So generally speaking, you can use prebuilt toolchain with customize
makefile to make building MCU's binary in yocto.
But if you want to use yocto to build
From: Ng Wei Tee wei.tee...@intel.com
Hi all,
The kernel complains that 'too much work for irq' when HSUART is
stressed in PCI mode. This 2 patches are back-ported to fix the
issue mentioned above. The patches were back-ported from upstream
kernel into linux-yocto-3.10.
It was built with Valley
From: Heikki Krogerus heikki.kroge...@linux.intel.com
It should not be used together with Auto Flow Control, and
Auto Flow Control is always enabled on Baytrail.
Signed-off-by: Heikki Krogerus heikki.kroge...@linux.intel.com
Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org
(cherry
13 matches
Mail list logo
