Hello,
I'm struggling getting my wandboard booting via tftp/nfs.
The first part was easy I just set up the tftp server and pointed it to the
kernel image and *.dtb file,
in the wandboard.h of u-boot I set
#define CONFIG_BOOTCOMMAND \
run netboot;
The kernel
Inside buildir/tmp/deploy/image/machine/ you have a image-name*.tar.gz
You will have to have in place the NFS client server architecture. Untar the
archive in the client location available inside /etc/exports:
The line should look like this: /home
*(rw,sync,no_subtree_check,no_root_squash),
Elizabeth,
Thanks for pulling in my commits, but it is incomplete. The top two commits
from the sullical/contrib branch are needed before the GitPoller changesource
will work. Specifically, they are commits
ecf1b8716d7e695a88976bba747af5c5bbe0007f and
The Debian 8 (codename Jessie) is frozen and has been in use in our
machines for some time. It has been working fine and as it is about to
be released it is better to whitelist it and remove the ugly warning
from build logs.
Signed-off-by: Otavio Salvador ota...@ossystems.com.br
---
The Debian 8 (codename Jessie) is frozen and has been in use in our
machines for some time. It has been working fine and as it is about to
be released it is better to whitelist it and remove the ugly warning
from build logs.
Signed-off-by: Otavio Salvador ota...@ossystems.com.br
---
Hi,
I'm observing an issue when booting BBB using today's master (Poky
b813bdebb36501500e86fea5f7e15b4b15ea0902). From what I see, default
u-boot config expects a zImage, while the beaglebone.conf sets
KERNEL_IMAGETYPE to uImage.
Also the boot mmc devices seem to be off, the default config has
On Tue, Dec 9, 2014 at 1:29 PM, Olof Johansson olof.johans...@axis.com wrote:
On 14-12-09 15:32 +0100, Otavio Salvador wrote:
The Debian 8 (codename Jessie) is frozen and has been in use in our
machines for some time. It has been working fine and as it is about to
be released it is better to
On 14-12-09 15:32 +0100, Otavio Salvador wrote:
The Debian 8 (codename Jessie) is frozen and has been in use in our
machines for some time. It has been working fine and as it is about to
be released it is better to whitelist it and remove the ugly warning
from build logs.
Signed-off-by:
On 9 December 2014 at 15:32, Otavio Salvador ota...@ossystems.com.br
wrote:
Richard, can you pick the v1 or want me to send a v3?
I had v1 in my MUT, then dropped it and added v2. I can drop that and go
back to v1. ;)
Ross
--
___
yocto mailing
U-boot 2014.07 in Poky expects a zImage kernel image, thus a build done with
current machien config will not be directly useable. Update machine config to
produce a zImage.
Signed-off-by: Maciej Borzecki maciej.borze...@open-rnd.pl
Signed-off-by: Maciek Borzecki maciek.borze...@gmail.com
---
On Tue, Dec 09, 2014 at 04:44:31PM +0100, Maciej Borzecki wrote:
U-boot 2014.07 in Poky expects a zImage kernel image, thus a build done with
current machien config will not be directly useable. Update machine config to
produce a zImage.
Signed-off-by: Maciej Borzecki
On 12/8/14, 3:55 AM, Jegan Chandru wrote:
I recommend you to file a bug here https://bugzilla.yoctoproject.org/ if not
done already. You may get a proper answer on armhf support there. From what I
see, (someone please correct me if I am wrong), there is no prelink dynamic link
armhf patch. You
On 12/09/2014 10:44 AM, Maciej Borzecki wrote:
U-boot 2014.07 in Poky expects a zImage kernel image, thus a build done with
current machien config will not be directly useable. Update machine config to
produce a zImage.
poky's README.hardware should be updated as well. When we wrote the
On Tue, Dec 9, 2014 at 1:41 PM, Burton, Ross ross.bur...@intel.com wrote:
On 9 December 2014 at 15:32, Otavio Salvador ota...@ossystems.com.br
wrote:
Richard, can you pick the v1 or want me to send a v3?
I had v1 in my MUT, then dropped it and added v2. I can drop that and go
back to v1.
I have attached the script. Basically, all that it does is extract the tarball
from the install script, untar it into a temp directory, install the rpm
created by the llvm build, then tar the temp directory back onto the tail of
the script.
The script lives in a subdirectory of the main poky
Hi Matthias,
From the following,
IP-Config: Complete:
device=eth0, hwaddr=00:1f:7b:b4:12:00, ipaddr=10.42.0.84,
mask=255.255.255.0, gw=10.42.0.1
host=10.42.0.84, domain=, nis-domain=(none)
bootserver=10.42.0.1, rootserver=10.42.0.1, rootpath=
nameserver0=10.42.0.1
I can tell
Hello Yu, Jim
I think you can get the clang executable into the SDK installer script
with something like this:
1. Add this dependency in nativesdk-packagegroup-sdk-host.bb:
*RDEPENDS_${PN} += nativesdk-name-of-clang-recipe*
2. In the clang recipe add this install() overwrite for the
Hi Matthias,
Sorry, I missed the kernel command line in all the other gobbledy-gook put out
by the boot.
Kernel command line: console=ttymxc0,115200 root=/dev/nfs ip=dhcp
nfsroot=:,v3,tcp
That doesn't look right to me.
-Jim-
From:
Hello,
I'm sending a patchset to enable Toaster logging for the autobuilder - can
you please review and comment ?
I have pending Bitbake patchset (*poky-contrib:adamian/devel-settings*)
Bitbake that adds two toaster-on-autobuilder related features:
1. build event logging flag (-w) will write an
Hi Liviu,
Thanks for the tip. I had everything but the override for
do_install_class-nativesdk().
One question please.
Will that override prevent the gcc compilers from being installed in nativesdk?
Or should I duplicate the existing do_install_class-nativesdk(), and add the
clang stuff?
On Tue, Dec 9, 2014 at 5:26 AM, Bryan Evenson beven...@melinkcorp.com wrote:
Elizabeth,
Thanks for pulling in my commits, but it is incomplete. The top two commits
from the sullical/contrib branch are needed before the GitPoller changesource
will work. Specifically, they are commits
Hello Jim,
You must add your override of do_install_class-nativesdk() in the recipe
that builds clang/llvm that will not affect how gcc gets installed in
the SDK.
You can have as many do_install_class-nativesdk() overrides across
various recipes as you like, without them conflicting.
On wto, 2014-12-09 at 10:51 -0500, Bruce Ashfield wrote:
On 12/09/2014 10:44 AM, Maciej Borzecki wrote:
U-boot 2014.07 in Poky expects a zImage kernel image, thus a build done with
current machien config will not be directly useable. Update machine config
to
produce a zImage.
poky's
A few initial comments.
TOASTER_UPLOADURL needs to be added to
config/autobuilder.conf.example. It would also be nice if it was added
to docs. Please set it to a localhost URL and comment it out for the
time being.
Also, can we make it TOASTER_UPLOAD_URL. It matches my naming
convention for
On 12/09/2014 12:59 PM, Maciek Borzecki wrote:
On wto, 2014-12-09 at 10:51 -0500, Bruce Ashfield wrote:
On 12/09/2014 10:44 AM, Maciej Borzecki wrote:
U-boot 2014.07 in Poky expects a zImage kernel image, thus a build done with
current machien config will not be directly useable. Update
I have submitted a bug here:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7056
Regards,
Qiang
On Tue, Dec 9, 2014 at 11:51 PM, Mark Hatle mark.ha...@windriver.com
wrote:
On 12/8/14, 3:55 AM, Jegan Chandru wrote:
I recommend you to file a bug here https://bugzilla.yoctoproject.org/ if
On 12/9/14, 8:41 PM, Qiang Yu wrote:
I have submitted a bug here:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7056
(Responded in the bug as well...) I have a test version of the cross prelink
with the ARM HF patch available, as commit:
2cde4ff118b5244f5577d9bc585c1ee521740af0
To
Liviu and Jim,
The thing is I'm trying to integrate LLVM+Clang together in the LLVM recipe.
The modifications that I made are just adding Clang, compiler-rt and Clang
tools within the LLVM work directory. Using this way, I can mimic the original
way (the one in LLVM website) of installing
Hello,
I'm working on incorporating an external kernel module based on the hello-mod
skeleton recipe. Everything was going well until I added the following line to
my machine configuration:
MACHINE_EXTRA_RDEPENDS += kernel-module-hello
Attempting to run bitbake core-image-base then leads to
29 matches
Mail list logo