[Xenomai-core] problem and solution with adeos-ipipe-2.6.13-ppc-1.0-03.patch

[Xenomai-core] problem and solution with adeos-ipipe-2.6.13-ppc-1.0-03.patch

[Fillod Stephane]

Hi,

The adeos-ipipe-2.6.13-ppc-1.0-03.patch file in Xenomai-2.0 dist appears
to be broken. The unified diff format is wrong on
include/asm-ppc/ipipe.h,
which breaks include/asm-ppc/mmu_context.h. I've found the problem while

applying the patch on a Linux 2.6.13 kernel.
Line 1664 (no pun :), instead of @@ -0,1 +1,178 @@, the following solves
the problem here: @@ -0,0 +1,177 @@

Does somebody else encountered the problem?


For the record, here is for 2.6.13-ppc-1.0-03 the result of klatency, 
with only calibrator as a load generator.

KLATENCY with load:
RTH|-----lat min|-----lat avg|-----lat max|-overrun|
RTS|       -7350|       -5715|        6420|       0|    00:03:17 1.0-00
RTS|       -6150|       -4384|       12180|       0|    00:03:13 1.0-01
RTS|       -6150|       -4183|       12480|       0|    00:03:38 1.0-02
RTS|       -6120|       -4447|        8370|       0|    00:03:47 1.0-02+
RTS|       -6210|       -5381|       12390|       0|    00:03:38 1.0-03

-- 
Stephane

PS: kudos for the 2.0 release!

Re: [Xenomai-core] problem and solution with adeos-ipipe-2.6.13-ppc-1.0-03.patch

[Aristeu Sergio Rozanski Filho]

> Hi,
> 
> The adeos-ipipe-2.6.13-ppc-1.0-03.patch file in Xenomai-2.0 dist appears
> to be broken. The unified diff format is wrong on
> include/asm-ppc/ipipe.h,
> which breaks include/asm-ppc/mmu_context.h. I've found the problem while
> 
> applying the patch on a Linux 2.6.13 kernel.
> Line 1664 (no pun :), instead of @@ -0,1 +1,178 @@, the following solves
> the problem here: @@ -0,0 +1,177 @@
> 
> Does somebody else encountered the problem?
I did.
maybe it's a good reason for 2.01?

-- 
Aristeu

Re: [Xenomai-core] problem and solution with adeos-ipipe-2.6.13-ppc-1.0-03.patch

[Philippe Gerum]

Fillod Stephane wrote:
> Hi,
> 
> The adeos-ipipe-2.6.13-ppc-1.0-03.patch file in Xenomai-2.0 dist appears
> to be broken. The unified diff format is wrong on
> include/asm-ppc/ipipe.h,
> which breaks include/asm-ppc/mmu_context.h. I've found the problem while
> 
> applying the patch on a Linux 2.6.13 kernel.
> Line 1664 (no pun :), instead of @@ -0,1 +1,178 @@, the following solves
> the problem here: @@ -0,0 +1,177 @@
> 

Gahh... Ok.

> Does somebody else encountered the problem?
> 
> 
> For the record, here is for 2.6.13-ppc-1.0-03 the result of klatency, 
> with only calibrator as a load generator.
> 
> KLATENCY with load:
> RTH|-----lat min|-----lat avg|-----lat max|-overrun|
> RTS|       -7350|       -5715|        6420|       0|    00:03:17 1.0-00
> RTS|       -6150|       -4384|       12180|       0|    00:03:13 1.0-01
> RTS|       -6150|       -4183|       12480|       0|    00:03:38 1.0-02
> RTS|       -6120|       -4447|        8370|       0|    00:03:47 1.0-02+
> RTS|       -6210|       -5381|       12390|       0|    00:03:38 1.0-03
> 

Ok, I need to check some changes between -02 and -03 before sending -04 out.

-- 

Philippe.

Re: [Xenomai-core] problem and solution with adeos-ipipe-2.6.13-ppc-1.0-03.patch

[Philippe Gerum]

Aristeu Sergio Rozanski Filho wrote:
>>Hi,
>>
>>The adeos-ipipe-2.6.13-ppc-1.0-03.patch file in Xenomai-2.0 dist appears
>>to be broken. The unified diff format is wrong on
>>include/asm-ppc/ipipe.h,
>>which breaks include/asm-ppc/mmu_context.h. I've found the problem while
>>
>>applying the patch on a Linux 2.6.13 kernel.
>>Line 1664 (no pun :), instead of @@ -0,1 +1,178 @@, the following solves
>>the problem here: @@ -0,0 +1,177 @@
>>
>>Does somebody else encountered the problem?
> 
> I did.
> maybe it's a good reason for 2.01?
> 

Maybe as we need to put perfectly buildable stuff on-line before making some 
noise as Jan's put it. Time for discovering other rough edges before 2.0.1 is 
rolled out, I guess.

-- 

Philippe.