On Wednesday 04 November 2015 17:16:32 Khem Raj wrote:
> > On Nov 4, 2015, at 11:57 AM, Chris Hallinan wrote:
> > I was trying to "patch a patch" in a u-boot recipe using standard
> > bbappends technique. I added a task before do_patch after do_unpack
> > to munge the patch that was broken. Here
On 04/11/15 15:08, Nathan Rossi wrote:
> On Thu, Nov 5, 2015 at 12:20 AM, Toby Gomersall
> wrote:
>> Hi,
>>
>> We've tried building the linux-xlnx tree standalone and we have the DMA
>> drivers available to add in menuconfig but not when I build
>> core-image-minimal. I thought the full build wo
Just curious, does anyone know why OE-core has python3-pip
but python-pip is relegated to meta-oe?
--
Gary Thomas | Consulting for the
MLB Associates |Embedded world
I use BB_GENERATE_MIRROR_TARBALLS = "1" to generate tarballs
from the various git-based recipes I use. For the most part
this works great and once the tar file is generated, it just
gets reused.
However, just now I rebuilt my kernel which uses such a git
SRC_URI and the tar file was rebuilt even
On 2015-11-05 06:17, Gary Thomas wrote:
I use BB_GENERATE_MIRROR_TARBALLS = "1" to generate tarballs
from the various git-based recipes I use. For the most part
this works great and once the tar file is generated, it just
gets reused.
However, just now I rebuilt my kernel which uses such a git
Hi Gary,
On Thursday 05 November 2015 05:39:21 Gary Thomas wrote:
> Just curious, does anyone know why OE-core has python3-pip
> but python-pip is relegated to meta-oe?
I think it has to do with pip being supplied as part of the standard python 3
distribution from 3.4 onwards. I think for simpli
On 2015-11-05 07:14, Paul Eggleton wrote:
Hi Gary,
On Thursday 05 November 2015 05:39:21 Gary Thomas wrote:
Just curious, does anyone know why OE-core has python3-pip
but python-pip is relegated to meta-oe?
I think it has to do with pip being supplied as part of the standard python 3
distribu
On Thu, Nov 5, 2015 at 4:25 AM, Paul Eggleton
wrote:
> On Wednesday 04 November 2015 17:16:32 Khem Raj wrote:
>> > On Nov 4, 2015, at 11:57 AM, Chris Hallinan wrote:
>> > I was trying to "patch a patch" in a u-boot recipe using standard
>> > bbappends technique. I added a task before do_patch af
Change [:space:] to [[:space:]]. [:space:] is incorrect and is treated
as a list of characters. Prior to this change having a policy of
'standard' resulted in POL_TYPE being set to 'tandard'.
Change the regular expression to match from the beginning of the line
since correcting the [:space:] error
On Thursday 05 November 2015 11:25:18 Chris Hallinan wrote:
> On Thu, Nov 5, 2015 at 4:25 AM, Paul Eggleton
>
> wrote:
> > On Wednesday 04 November 2015 17:16:32 Khem Raj wrote:
> >> > On Nov 4, 2015, at 11:57 AM, Chris Hallinan
> >> > wrote:
> >> > I was trying to "patch a patch" in a u-boot re
Forgot to include the ML…
I just updated to Debian Jessie so:
$ tmux -V
tmux 1.9
I tested this commands before updating to Jessie and the output for a multipane
window was:
$ tmux list-panes -F "#{?pane_active,yes,no}"
yes
no
no
no
$ tmux list-panes -F "#{pane_height}"
43
48
49
43
Hope th
On Thu, Nov 5, 2015 at 9:05 AM, Paul Eggleton
wrote:
> On Thursday 05 November 2015 11:25:18 Chris Hallinan wrote:
>> On Thu, Nov 5, 2015 at 4:25 AM, Paul Eggleton
>>
>> wrote:
>> > On Wednesday 04 November 2015 17:16:32 Khem Raj wrote:
>> >> > On Nov 4, 2015, at 11:57 AM, Chris Hallinan
>> >> >
On Thu, Nov 5, 2015 at 8:25 AM, Chris Hallinan wrote:
> On Thu, Nov 5, 2015 at 4:25 AM, Paul Eggleton
> wrote:
>> On Wednesday 04 November 2015 17:16:32 Khem Raj wrote:
>>> > On Nov 4, 2015, at 11:57 AM, Chris Hallinan wrote:
>>> > I was trying to "patch a patch" in a u-boot recipe using standar
As you said on Wheezy, tmux 1.6 the patch provided only works when the windows has 1
pane.
If a window has multiple panes, then we got:
$ tmux list-panes -F "#{?pane_active,yes,no}"
yes
no
no
no
$ tmux list-panes -F "#{pane_height}"
43
48
49
43
This leads to:
In [2]: import subprocess as sub
I
Hi,
I noticed that runqemu starts with one TAP device by default. Inside
the VM this would be eth1 vNIC device. Is it possible to start the VM
with multiple tap devices (i.e. eth1, eth2, eth3, etc.)?
I have tried using the "runqemu-gen-tapdevs" script, which creates
multiple tap devices successfu
Hi Mark,
>I have done the same implementation for AARCH64. Loader handles
>AARCH64_TLSDESC conflict as below.
>case R_AARCH64_TLSDESC:
>
>if (! sym)
> {
>td->arg = (void*)reloc->r_addend;
>td->entry = _dl_tlsdesc_undefweak;
>
16 matches
Mail list logo
