Hello,
The Qi-Hardware community kernel now has an upstream compliant driver
to provide USB support for the Ben Nanonote, along with other features
and fixes.
The aforementioned changes were submitted upstream in order to have
full upstream support for the Ben kernel.
The patches that come as a f
The kernel recipe for the Ben Nanonote machine is now relying on the
Qi-Hardware kernel source code instead of the JLime kernel source code
initially.
Rename linux-jlime-ben-nanonote recipe to linux-qi-ben-nanonote to
reflect the change.
Signed-off-by: Apelete Seketeli
---
conf/machine/ben-nanon
From: Krzysztof Sywula
irssi is a text mode IRC client.
Signed-off-by: Krzysztof Sywula
Signed-off-by: Koen Kooi
---
.../recipes-connectivity/irssi/irssi_0.8.16-rc1.bb | 21 +
1 file changed, 21 insertions(+)
create mode 100644 meta-oe/recipes-connectivity/irssi/irssi_0.
On Tuesday 07 January 2014 16:03:24 Koen Kooi wrote:
> From: Krzysztof Sywula
>
> irssi is a text mode IRC client.
>
> Signed-off-by: Krzysztof Sywula
> Signed-off-by: Koen Kooi
> ---
>
> * Fixed PV
> * Added SSL support
>
> I'm open for suggestions where to put it, meta-networking might not
From: Krzysztof Sywula
irssi is a text mode IRC client.
Signed-off-by: Krzysztof Sywula
Signed-off-by: Koen Kooi
---
* Fixed PV
* Added SSL support
I'm open for suggestions where to put it, meta-networking might not be the best
place - koen
.../recipes-protocols/irssi/irssi_0.8.16-rc1.bb
I had a chat with Paul about it the other day and we thought
recipes-connectivity/ would probably suit the best.
Thanks,
Krzysztof Sywula
-Original Message-
From: Koen Kooi [mailto:k...@dominion.thruhere.net]
Sent: Tuesday, January 07, 2014 3:03 PM
To: openembedded-devel@lists.openembe
Hi all,
There will be a public OpenEmbedded TSC/workgroup meeting today. If you're
interested in discussing long-term technical efforts around the OpenEmbedded
project please join us on irc.freenode.net in channel #oe at
17:00 GMT (9am PST, 11am CST, 12 EST, 18:00 CET) today.
Cheers,
Paul
--
* Martin Jansa [140107 14:08]:
> On Tue, Jan 07, 2014 at 01:39:49PM +0100, Anders Darander wrote:
> > diff --git a/meta-oe/recipes-kernel/ktap/ktap_0.4.bb
> > b/meta-oe/recipes-kernel/ktap/ktap_0.4.bb
> > index f5dd62f..a703aec 100644
> > --- a/meta-oe/recipes-kernel/ktap/ktap_0.4.bb
> > +++ b/m
> SOB line is missing, but I've already added it manually from you first
> version of this patch.
> http://patchwork.openembedded.org/patch/64207/
> seems to work, version with attachement wasn't picked by patchwork
Ok thank you for copying over the SOB line manually
...
>> ++ cp Makefile $
On Tue, Jan 07, 2014 at 01:39:49PM +0100, Anders Darander wrote:
> libelf (elfutils) is required for resolving symbols in DSO and for sdt (taken
> from ktap docs). The earlier v0.4 recipe built ktap against libelf if it was
> found, thus enable it per default.
>
> FFI needs to be enabled for both
Add some configuration to the build process of ktap, to get a more
deterministic build. Currently, the v0.4 recipe will build with
libelf support (from the elfutils recipe), if that is found during
the compile stage, thus we have a non-deterministic build going on.
At the same time, I'm also ad
libelf (elfutils) is required for resolving symbols in DSO and for sdt (taken
from ktap docs). The earlier v0.4 recipe built ktap against libelf if it was
found, thus enable it per default.
FFI needs to be enabled for both userspace and kernel module. Currently, it is
only supported for x86_64 (en
On Tue, Jan 07, 2014 at 10:29:28AM +, Lewis, Nick wrote:
> From c77c6adf075f314209f7cd071fb5b99c0d8d0e70 Mon Sep 17 00:00:00 2001
> From: Nick Lewis
> Date: Mon, 6 Jan 2014 17:16:03 +
> Subject: [PATCH] Use libxml++ version 2.37.1 and add ptest support
>
SOB line is missing, but I've alr
>From c77c6adf075f314209f7cd071fb5b99c0d8d0e70 Mon Sep 17 00:00:00 2001
From: Nick Lewis
Date: Mon, 6 Jan 2014 17:16:03 +
Subject: [PATCH] Use libxml++ version 2.37.1 and add ptest support
---
.../libxml/libxml++-2.37.1/libxml++_ptest.patch| 73
.../recipes-core/li
>Using git format-patch and sending created file as attachment would probably
>be better, but still not picked correctly by patchwork imho.
>Please try it and we'll see.
I hope this helps. I will also do another email with it pasted inline rather
than attached
--
The details of this company a
15 matches
Mail list logo