already are compatible, mostly the TI OMAP/AM
series.
Elvis Dowson
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
virtex5
virtex5-tcbootstrap
x86_64-linux
x86_64-nativesdk-pokysdk-linux
x86_64-nativesdk-poky-linux-tcbootstrap
work
all-poky-linux
ppc440-poky-linux
virtex5-poky-linux
x86_64-linux
x86_64-native
Hi,
On Aug 20, 2012, at 2:34 PM, Paul Eggleton wrote:
>
> Is "debug-tweaks" in IMAGE_FEATURES?
>
I too have the same problem, I've got debug-tweaks in IMAGE_FEATURES, but it
doesn't allow me to login. If I type root as the username, it does nothing and
brings up the login prompt again.
Sta
Hi Khem,
On Aug 21, 2012, at 7:07 AM, Khem Raj wrote:
> Now glibc can be compiled with gcc-cross-initial therefore prepare
> the stage to drop gcc-cross-intermediate
I'm adapting my earlier gcc-4.5 recipes, to try and get them to build with the
latest poky master.
I'm using eglibc-2.13, so it
On Aug 25, 2012, at 1:10 AM, Khem Raj wrote:
> On Fri, Aug 24, 2012 at 2:08 PM, Elvis Dowson wrote:
>>
>> I'm adapting my earlier gcc-4.5 recipes, to try and get them to build with
>> the latest poky master.
>>
>> I'm using eglibc-2.13, so it is p
way for an officially supported meta-xilinx layer, the details
of which will be officially announced by Xilinx.
Best regards,
Elvis Dowson
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman
Hi,
I get the following warnings when I try to do bitbake core-image-minimal
WARNING:
/tool/yocto/meta-openembedded/meta-oe/recipes-connectivity/networkmanager/networkmanager_0.9.2.0.bb:
it is recommended to set SYSTEMD_PACKAGES as -systemd
WARNING: /tool/yocto/poky/meta/recipes-extended/
Hi Martin,
On May 4, 2012, at 10:02 AM, Martin Jansa wrote:
>
> Check this thread
> http://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg24963.html
The above thread only discusses the warning, but no-one has fixed it yet. If
you can tell me what needs to be done, I'll create
This patch fixes WARNING: /tool/yocto/meta-openembedded/meta-oe/
recipes-connectivity/networkmanager/networkmanager_0.9.2.0.bb:
it is recommended to set SYSTEMD_PACKAGES as -systemd
Signed-off-by: Elvis Dowson
---
.../networkmanager/networkmanager_0.9.2.0.bb |2 +-
1 file changed, 1
"${PN}-systemd"
SYSTEMD_SERVICE = "lighttpd.service"
WARNING: /tool/yocto/poky/meta/recipes-extended/lighttpd/lighttpd_1.4.30.bb: it
is recommended to set SYSTEMD_PACKAGES as -systemd
Best regards,
Elvis Dowson
___
Openembedded-
Hi Denys,
On May 4, 2012, at 7:33 PM, Denys Dmytriyenko wrote:
>>
>> -SYSTEMD_PACKAGES = "${PN}"
>> +SYSTEMD_PACKAGES = "${PN}-systemd"
>
> That might be an overkill. I'm personally not yet very familiar with all the
> systemd specifics and not clear when to create ${PN}-systemd subpackage and
ice"
+
FILES_${PN} += "${sysconfdir} /www"
CONFFILES_${PN} = "${sysconfdir}/lighttpd.conf"
Elvis Dowson
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Hi Denys,
On May 4, 2012, at 8:27 PM, Denys Dmytriyenko wrote:
> You are trying to fix it in oe-core/poky layer, where it doesn't use systemd.
> There is a .bbappend in meta-oe for that.
Yes, you're right! :-) Ok, I'm slowly starting to see how its important to trace
any additional .bbappend r
Hi,
I've added the meta-xilinx layer, and modified my build/conf/local.conf
file as follows:
# Set the target machine details
MACHINE ?= "virtex5"
# Set Xilinx Platform Studio hardware project path
XILINX_BSP_PATH ?= "/project/xilinx-ml507"
# Set target board
XILINX_BOARD ?= "ml507"
and wh
Virtex-5 FX70T FPGA chip,
which doesn't have a hardware FPU. Do the options look okay: "m32 fpu-soft
ppc440" ?
Is there a resource I can refer to see a full list of applicable PowerPC440
gcc-4.x compiler options?
Best regards,
Elvis Dowson
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
he()
File "/tool/yocto/poky/bitbake/lib/bb/cooker.py", line 1202, in updateCache
if not self.parser.parse_next():
File "/tool/yocto/poky/bitbake/lib/bb/cooker.py", line 1671, in parse_next
self.virtuals += len(result)
UnboundLocalError: local variable 'result
File "/tool/yocto/poky/bitbake/lib/bb/cooker.py", line 1202, in updateCache
if not self.parser.parse_next():
File "/tool/yocto/poky/bitbake/lib/bb/cooker.py", line 1671, in parse_next
self.virtuals += len(result)
UnboundLocalError: local variable
Hi Khem,
> On Tue, May 29, 2012 at 9:56 PM, Khem Raj wrote:
>> On Tue, May 29, 2012 at 12:46 PM, Elvis Dowson
>> wrote:
>>> PACKAGE_EXTRA_ARCHS_tune-ppc440 = "${PACKAGE_EXTRA_ARCHS_tune-powerpc}
>>> ppc440"
>>
>> may be th
Hi,
On May 30, 2012, at 5:00 PM, Khem Raj wrote:
> On Wed, May 30, 2012 at 7:47 AM, Elvis Dowson wrote:
>>
>> What does the -nf suffix do ?
>>
>
> indicates no float
What should I call the tune configuration file: tune-ppc440.inc or
tune-ppc440-nf.inc ?
For the
2/packages-split/bash/bin/bashbug
WARNING: QA Issue: Shell scripts in base_bindir and base_sbindir should not
reference anything in exec_prefix
Best regards,
Elvis Dowson
___
Openembedded-core mailing list
Openembedded-core@lists.openembedde
Hi,
On May 31, 2012, at 7:38 PM, Elvis Dowson wrote:
> I've found the following warnings while attempting to build linux-xilinx. How
> can I trace which package it's originating from and what can I do to fix it?
>
> WARNING: QA Issue: bash: Found a reference to /usr/
.
Shouldn't python-native get built correctly the first time around?
My parallelism options as follows:
BB_NUMBER_THREADS = "6"
PARALLEL_MAKE = "-j 6"
Best regards,
Elvis Dowson
___
Openembedded-core mailing list
Openembedded-core@li
Hi,
While attempting to build linux-xilinx, I get the following warning:
WARNING: linux-xilinx: No generic license file exists for: GPL in any provider
What should I do to fix this warning?
Best regards,
Elvis Dowson
___
Openembedded-core
Hi Adrian,
When I attempt to build the linux-xilinx kernel, it doesn't
find the device tree (*.dts) in the xilinx-ml507-update BSP project. Is the
device tree supposed to be generated manually? If so, could you please tell me
how to generate it?
Best regards,
Elvis D
from there generate the device tree according to the hwd settings...
Perhaps these steps could be automated by modifying the
meta-xilinx/classes/xilinx-kernel.bbclass file, so that the EDK gets
invoked from the command line to parse the mhs file and create the
dts file
x_git.bb, do_configure
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
Best regards,
Elvis Dowson
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Hi Adrian,
On Jun 1, 2012, at 11:18 PM, Elvis Dowson wrote:
> I've created a hardware bsp project using Xilinx SDK 14.1, and used the
> xilinx-ml507-update project, (after updating it to XPS 14.1 format).
>
> Now the script in meta-xilinx/classes/xilinx-kernel.bbclass is looki
xparameters.h
}
My machine is configured as virtex-5, and meta-xilinx/conf/machine/virtex5.conf
doesn't specify TARGET_ARCH, it just defines the following
TARGET_CPU = "440"
#tune for the 440 cpu
require conf/machine/include/tune-ppc440.inc
So is that a mistake
Hi,
On Jun 2, 2012, at 10:36 PM, Elvis Dowson wrote:
> How can I debug the value of ${TARGET_ARCH} in
> meta-xilinx/classes/xilinx-boot.class, for the following function:
>
> do_export_xparam() {
> bbnote "Replacing xparameters header to match hardware model"
> xpa
Hi,
> On Jun 2, 2012, at 10:36 PM, Elvis Dowson wrote:
>
>> How can I debug the value of ${TARGET_ARCH} in
>> meta-xilinx/classes/xilinx-boot.class, for the following function:
>>
>> do_export_xparam() {
>> bbnote "Replacing xparameters header to
Hi Khem,
On Jun 3, 2012, at 2:48 AM, Khem Raj wrote:
> What's your default she I guess its not bash
I have left it as the default Dash shell, as indicated in the yocto 1.2 setup
guidelines, for Ubuntu-12.04 LTS.
Best regards,
Elvi
Hi,
I'm trying to make the
meta-xilinx/recipes-bsp/u-boot/u-boot-xilinx_git.bb recipe work for both the
virtex5 and microblaze machine architectures.
So far, I find that you can start off by simply prefixing the machine
architecture for a bunch of variables like
PV_virtex5
SRC_URI_virte
=>
/tool/yocto/poky/build/tmp/sysroots/virtex5/lib/libdl.so.2 (0xdead4000)
librt.so.1 =>
/tool/yocto/poky/build/tmp/sysroots/virtex5/lib/librt.so.1 (0xdead5000)
libpthread.so.0 =>
/tool/yocto/poky/build/tmp/sysroots/virtex5/lib/libpthread.so.0 (0xdead6000)
libc.so.6
ore, so if someone could guide me as to what I should
do, and the recipes I should take a look at, it would be great!
Best regards,
Elvis Dowson
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-b
l+alt
it releases the mouse grab, but if I click on the QEMU window, I can see the
mouse cursor moving around, but it doesn't interact with the sato desktop.
Is there a fix or workaround for this issue?
Elvis Dowson
___
Openembedded-core ma
end
ERROR: Command execution failed: Exited with 1
Summary: There were 2 WARNING messages shown.
Summary: There were 3 ERROR messages shown, returning a non-zero exit code.
best regards,
Elvis Dowson
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Hi,
On Jun 8, 2012, at 4:05 PM, Tom Zanussi wrote:
> I just posted a patch to fix this - it was a SRCREV typo.
>
> Building fine here now with that simple fix...
Yes, removing the stray 'l' character from the SRCREV fixed it, the build is
progressing fine now.
Best reg
Hi, I have modified the default qemuarm.conf file, to switch it over to using ARM Cortex A9, with hard float, vfp and neon support, by applying the following patch (which basically includes the tune-cortexa9.inc file).diff --git a/meta/conf/machine/qemuarm.conf b/meta/conf/machine/qemuarm.con
Hi Martin,
On Aug 25, 2013, at 6:44 PM, Martin Jansa wrote:
>> I find that the kernel panics upon boot.
Thanks! Any idea why the qemu with hard float configuration has a kernel panic
with linux-yocto?
Elvis Dowson
___
Openembedded-core m
27;t see a defconfig anywhere, and I was wondering how the
linux-yocto kernel picks up the defconfig from the standard/base branch.
A TI OMAP 4430 Pandaboard or i.MX6 quad-core SABRE development kit platform
would do, but not sure how the linux-yocto kernel works, in terms of
pre-selecting the corre
On Aug 25, 2013, at 10:02 PM, Elvis Dowson wrote:
> The thing is I don't see a defconfig anywhere, and I was wondering how the
> linux-yocto kernel picks up the defconfig from the standard/base branch.
I found the answer for this one:
http://www.yoctoproject.org/docs/1.4/ref
ge type.
KERNEL_IMAGETYPE = "zImage"
# Specify the serial console parameters.
SERIAL_CONSOLE = "115200 ttyAMA0"
Elvis Dowson
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Hi Bruce,
On Aug 26, 2013, at 5:03 AM, Bruce Ashfield
wrote:
> On 13-08-25 3:09 PM, Elvis Dowson wrote:
>> I noticed that you've committed the changes for qemuarma9 KMACHINE
>> configuration to the linux-yocto kernel.
>>
>> http://git.yoctoproject.org/cgit/cg
can come up the right conf files, and machine definition, I
> can pretty easily support it in linux-yocto.
Could you tell me what's steps I need to follow, to add a new machine
definition and support to the linux-yocto kernel?
I'd like to learn how to do this!
ion to the qemuarma9-standard.scc file.
From 8e9b465f242941b70d7b61045c073e82700fcd91 Mon Sep 17 00:00:00 2001
From: Elvis Dowson
Date: Mon, 26 Aug 2013 22:18:24 +0400
Subject: [PATCH] qemuarma9: Update branch to qemuarma9.
Signed-off-by: Elvis Dowson
---
meta/cfg/kernel-cache/bsp/qemuarma9/qemuarma9-standa
Hi,
I get the following error while running the bitbake linux-yocto command
for a qemu machine conf that I'm building. The build system is unable to find
the dtc binary:
| make: Leaving directory
`/tool/yocto/poky/build/tmp/work/qemuarma9-poky-linux-gnueabi/linux-yocto/3.4.52+gitAUTOINC+
On Aug 29, 2013, at 2:43 AM, Bruce Ashfield
wrote:
> On 13-08-28 11:16 AM, Elvis Dowson wrote:
>> Hi,
>>I get the following error while running the bitbake linux-yocto
>> command for a qemu machine conf that I'm building. The build system is
>&g
>> also take a look at meta-linaro, they test armv7+ qemu regularly.
I built core-image-minimal using meta-linaro, using genericarmv7 machine but it
just generates an Image file for the kernel and a tar.gz rootfs. It doesn't
look like its useful out of the box for a QEMU image. Additionally you
t-gen and current-gen platforms
out there.
Best regards,
Elvis Dowson
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
On Aug 29, 2013, at 8:17 PM, Khem Raj wrote:
>
> On Aug 29, 2013, at 1:50 AM, Elvis Dowson wrote:
>
>>>> also take a look at meta-linaro, they test armv7+ qemu regularly.
>>
>> I built core-image-minimal using meta-linaro, using genericarmv7 machine but
&
On Aug 29, 2013, at 8:23 PM, Bruce Ashfield
wrote:
> On 13-08-29 10:02 AM, Elvis Dowson wrote:
>> Hi Bruce,
>>
>> On Aug 29, 2013, at 4:35 PM, Bruce Ashfield
>> wrote:
>>
>>> With that, it's always been a manual setup for me in the past. T
e
QEMU emulator, and then using LaunchPad and Soyuz locally to
build Ubuntu on a virtual machine, rather than just re-use the official
Ubuntu binary packages. This way, I have more control over the
toolchain, and options, rather than use the existing armel or armhf
machine configurations supplie
ding a defconfig
for linux-yocto. the runqemu scripts have to be modified, etc.
I've shared all that I've done, with you, but you've apparently done this
before, and I've just spend days to find out just that!!
Thanks for the run around!!
Elvis Dowson
__
Hi Khem,
On Aug 25, 2012, at 1:59 AM, Khem Raj wrote:
> On Friday, August 24, 2012, Elvis Dowson wrote:
> >
> > On Aug 25, 2012, at 1:10 AM, Khem Raj wrote:
> >
> >> On Fri, Aug 24, 2012 at 2:08 PM, Elvis Dowson
> >> wrote:
> >>>
> >&
Hi Khem,
On Oct 6, 2012, at 7:41 PM, Khem Raj wrote:
> On Fri, Oct 5, 2012 at 11:59 PM, Elvis Dowson wrote:
>>
>> I've narrowed down the init problem, to the application of the above patch,
>> but I'm unable to figure out why it is failing. Any suggestions?
>&
Hi Khem,
On Oct 6, 2012, at 7:41 PM, Khem Raj wrote:
> On Fri, Oct 5, 2012 at 11:59 PM, Elvis Dowson wrote:
>>
>>
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=48df3fe947c4d900aa6b66d9d8352c0d9e59ebe4
eglibc: Fix eglibc-initial and let eglibc depend on it
>&g
Hi Khem,
On Oct 9, 2012, at 5:48 PM, Elvis Dowson wrote:
> So, now I've got gcc-4.5.4 working with eglibc-2.13, upto the point where the
> kconfig infrastructure was added.
>
> Next, to add the kconfig infrastructure to eglibc-2.13, and fast forward to
> the tip of the pok
Hi Robert,
On my i7 quad core machine, I've set both values to 6. Setting it to 6 appears
to be nearly the same as setting it to 8, I dare say a marginally faster by a
minute. I can build core image console in around 22 minutes.
Elvis
Sent from my iPad
On Jan 9, 2013, at 4:55 PM, "Robert P. J.
n for
the microblaze processor?
Elvis Dowson
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
> or very least improve the existing recipes for now and once the 1.4 release
> is done
> we can then propose it for inclusion in OE-Core
>
> Thanks for your time
I've built and tested the new gcc-4.8.0 recipe for the Xilinx ZC
Error 2
| ERROR: oe_runmake failed
| ERROR: Function failed: do_compile (see
/tool/yocto/poky/build/tmp/work/microblazeel-v830-bs-cmp-re-ml-div-fb-poky-linux/gcc-cross-initial/4.8.0-r0/temp/log.do_compile.8602
for further information)
Best regards,
Elvis Dowson
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
ut at 4.2Ghz and 3.8Ghz, and the difference was
only 2 to 3 minutes between 3.8GHz and 4.2GHz over-clocked, so I currently
leave it at 3.8GHz over-clocked.
I'm using two SSDs in a RAID 0 striped configuration, and build times is
around 22 minutes for a Zynq-7-ZC702 build for core-image-minimal.
Elvis Dowson
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
62 matches
Mail list logo
