The first milestone release for Yocto Project 2.2 is available for
download now.
http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-2.2_M1/
Thank you to everyone for your contributions.
eclipse-poky/kepler-master f357cc3f8981ae3f4401cb24435ef40ab095cb33.tar.bz2
On 2016-07-19 1:50 PM, Ernst, Eric wrote:
Bruce, can you consider this for merge into bxt-rebase?
This has now been merged.
If anything is missing, send along new pull requests.
Bruce
On Fri, Jul 15, 2016 at 10:09:08PM -0700, Weight, Russell H wrote:
These patches apply, and I'm able to
QA requested wic images for genericx86, as well as x86-64 so include
config and build for them.
[YOCTO #10006]
Signed-off-by: Bill Randle
---
buildset-config.controller/nightly-wic.conf | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git
On 21/07/16 14:32, Herve Jourdain wrote:
> v4 series:
> a. rebased
> b. Upstream-Status added to the patch to the VC4 driver (needed only for
> kernel 4.4, accepted upstream in 4.7)
>
> v3 series:
> a. patch rebased
> b. new revision of kernel, to get a version of the VC4 graphics driver that
>
Signed-off-by: Daniel Dragomir
---
bsp/axxiaarm64/axxiaarm64.cfg | 2 ++
1 file changed, 2 insertions(+)
diff --git a/bsp/axxiaarm64/axxiaarm64.cfg b/bsp/axxiaarm64/axxiaarm64.cfg
index ed2abd7..d08fe71 100644
--- a/bsp/axxiaarm64/axxiaarm64.cfg
+++
Hello Bruce!
Please apply this path on the 'yocto-4.1' branch from
git.yoctoproject.org/yocto-kernel-cache
This patch enable NCR driver and the PEI Controller for
axxiaarm64 bsp.
Thank you,
Daniel Dragomir (1):
bsp/axxiaarm64: Enable Axxia NCR and PEI drivers
bsp/axxiaarm64/axxiaarm64.cfg |
Hello all,
I'm trying to create an image with the following partition:
boot0_position=8 # KiB
uboot_position=19096 # KiB
boot0 is a blob and it loads u_boot. Please can some one help me on
this matter?
Thanks a lot,
Montez
--
___
yocto mailing
On Fri, Jul 22, 2016 at 12:03 AM, piotr.lewicki wrote:
> Hi all,
>
> I also think that's a good idea. In my opinion we should at least make
> latest LTS (4.4) the default kernel and try to add latest mainline.
>
> Probably the "proper way" of dealing with the issue is
On Fri, Jul 22, 2016 at 12:09 AM, Andre McCurdy wrote:
> On Thu, Jul 21, 2016 at 8:20 PM, Khem Raj wrote:
>>
>>> On Jul 21, 2016, at 6:45 PM, Paul Eggleton
>>> wrote:
>>>
>>> On Thu, 21 Jul 2016 18:35:25 Khem Raj wrote:
Paul,
I am having stability issues with the USB subsystem on Raspberry Pi 3 under 4.4
that I can’t reproduce under 4.1. I assume 4.1 will still remain in the recipe
when 4.4 is made the default option. How long would the 4.1 version stay so
that those that want to can keep the old kernel
Hi,
It did not help either. For some reason, hard disk is not
mounted/recognized.
After the message:
"Please append a correct "root=" boot option"
i can only see a list with ram partitions, like
ram0 (driver?)
ram1 (driver?)
...
ram15 (driver?)
There is nothing else in the list.
How can i
Remove documentation as swabber was removed from
oe-core with this commit:
commit a7ddbea345c90646e6b9ddb89f768865caffdf07
Author: Richard Purdie
Date: Mon Jun 6 12:08:56 2016 +0100
meta: Drop swabber
Signed-off-by: Maxin B. John
On Fri, Jul 22, 2016 at 1:18 PM, jags gediya wrote:
> Can i have 2 bbappend file for single recipe?
> I want to add something to the recipe whom bbappend file is already
> available but i don't want to modify that file directly. I want to add new
> bbappend file for that
Hi All,
Can i have 2 bbappend file for single recipe?
I want to add something to the recipe whom bbappend file is already
available but i don't want to modify that file directly. I want to add new
bbappend file for that recipe in my custom layer, Is it possible?
--
On Thu, Jul 21, 2016 at 8:20 PM, Khem Raj wrote:
>
>> On Jul 21, 2016, at 6:45 PM, Paul Eggleton
>> wrote:
>>
>> On Thu, 21 Jul 2016 18:35:25 Khem Raj wrote:
>>> On Thu, Jul 21, 2016 at 6:32 PM, Paul Eggleton
>>>
>>>
Hi all,
I also think that's a good idea. In my opinion we should at least make
latest LTS (4.4) the default kernel and try to add latest mainline.
Probably the "proper way" of dealing with the issue is using branches.
This way (as it is in oe-core): jethro would have kernel 3.18 and 4.1,
16 matches
Mail list logo