Hi Vidal
Cc+meta-xilinx,
I think you’ll need to provide more information on your layers by providing the
summary of your build.
See inline
>From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
>On Behalf Of Edward Vidal
>Sent: Monday, 30 December 2013 2:29 AM
>To: yoct
Hi Bruce,
The linux-yocto orphaned meta branch commit
8ef9136539464c145963ac2b8ee0196fea1c2337
.gitignore: do not ignore meta directory
causes the linux-yocto targets in meta-xilinx/master to fail with the following
error(s):
snip ---
[ERROR] unable to complete push
| ERROR. could not upd
Hi all,
A dylan branch has been created, in meta-xilinx, for anyone needing to build
against yocto 1.4 or needing an environment that is not changing. This Dylan
branch still requires an external tool chain for the microblaze architecture
and targets linux-xlnx 3.8 and u-boot-xlnx 2013.01.
All
-community layer that you require.
Both layers use the same email list: meta-xil...@yoctoproject.org, so that is
always a good starting point to ask.
Regards
Sipke
-Original Message-
From: Khem Raj [mailto:raj.k...@gmail.com]
Sent: Thursday, 30 May 2013 12:22 PM
To: Sipke Vriend
Cc: Yocto
Microblaze
architecture, currently with bsp layers targeting the evaluation boards zc702,
zedboard and kc705. The layer is under development and further information is
available in README files within the layer.
Regards
Sipke Vriend
-Original Message-
From: Elvis Dowson [mailto:elvis.dow
Hi,
If your recipes rely on repositories at git.xilinx.com, please update them to
use
github.com/Xilinx.
Regards
Sipke
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
ed, we intend to have a 'full' and 'lite' as standard tunes for the user to
work
with and build on as required.
Regards
Sipke
On Wednesday, 27 March 2013 5:19 AM, Mark Hatle wrote:
>
>On 3/26/13 1:12 AM, Sipke Vriend wrote:
>> Hi all,
>>
>> With hel
-v830
Regards
Sipke
>On Mar 20, 2013, at 4:44 PM, Khem Raj <mailto:raj.k...@gmail.com> wrote:
>
>
>On Mar 19, 2013, at 9:08 PM, Sipke Vriend wrote:
>
>
>Hi all,
>
>We are seeking some feedback regarding common practices for defining
>TUNE_PKGARCH within Yocto.
>
Hi all,
We are seeking some feedback regarding common practices for defining
TUNE_PKGARCH within Yocto.
We need to define a unique TUNE_PKGARCH for the possible configuration of
Microblaze architecture.
Our proposal is short unique string for each HW feature which is enabled in
Microblaze