Hi Darren,
Thanks for this, it is very informative and useful.
You've been me a good number of solid leads to follow.
Where are you storing the image? SPI, SD, USB, SATA? Assuming SATA as
you are speaking in highly general x86 terms, which typically means PC
rather than deeply embedded.
You
Dear list,
What do people do for deploying Yocto built images to actual x86 hardware?
I am researching how to build an appliance type Linux box on x86
hardware, but I am unclear on what are the generally accepted methods
for doing that. The box would need to have a read-only rootfs, mounted
://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html)
be updated with this new information? Should I file a bug report to help
this happen?
Best regards,
Markus
On 11/03/2013 03:37 PM, Khem Raj wrote:
On Thu, Oct 31, 2013 at 3:48 PM, Markus Svilans msvil...@aeonyx.ca wrote
Dear list,
I am working on a compact filesystem image, that contains firmware only
for the network hardware on the motherboard.
Therefore, I created a linux-firmware.bbappend file, with the following
contents:
# Cherrypick the firmware files that we need for our hardware
of the original recipe.
1.5 (dora) contains linux-firmware_git.bb in which case the bbappend should be
named linux-firmware_git.bbappend.
Fredag den 1. november 2013 15:43:19 skrev Markus Svilans:
Dear list,
I am working on a compact filesystem image, that contains firmware only
for the network
built under an
lxc and a chroot running Debian Wheezy, on Ubuntu 13.10 64-bit, with
MACHINE=genericx86-64.
Filed bug 5440 on Yocto Bugzilla.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5440
Markus
On 10/29/2013 10:28 PM, Markus Svilans wrote:
Thanks, Khem.
Following your suggestion, I
to build it directly bitbake syslinux
Any assistance would be greatly appreciated.
Thanks very much
Markus
On 10/29/2013 05:40 PM, Markus Svilans wrote:
Dear list,
I'm trying to build a core-image-minimal recipe using
MACHINE=genericx86-64 but it always fails at syslinux-native-6.01
recipe
feeling around in the
dark here. Maybe could someone else take a look at this?
Thanks very much
Markus
On 10/29/2013 07:11 PM, Khem Raj wrote:
On Tue, Oct 29, 2013 at 3:55 PM, Markus Svilans msvil...@aeonyx.ca wrote:
Dear list,
A quick update:
- The same build failure occurred when I
