[ANNOUNCE] v4.19.50-cip3-rt2


Pavel Machek
 

Hi!

4.19.50-cip3-rt2 should be available at kernel.org. It performs well
on socfpga (Altera-Terasic-Deo-NanoAltera); but not so well on iwg20m
(r8a7743-iwg20d-q7) board.

Trees are available at

https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt-rebase

https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt

And their content should be identical. I attempted to tag it in a way
consistent with previous releases, and I attempted to sign a tag.

Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


Jan Kiszka
 

On 23.07.19 14:40, Pavel Machek wrote:
Hi!

4.19.50-cip3-rt2 should be available at kernel.org. It performs well
on socfpga (Altera-Terasic-Deo-NanoAltera); but not so well on iwg20m
(r8a7743-iwg20d-q7) board.
Thanks!

Trees are available at

https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt-rebase

https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt

And their content should be identical. I attempted to tag it in a way
consistent with previous releases, and I attempted to sign a tag.
...but you didn't push the tag yet? Or is this WiP?

Jan

--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux


Pavel Machek
 

Hi!

Trees are available at

https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt-rebase

https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt

And their content should be identical. I attempted to tag it in a way
consistent with previous releases, and I attempted to sign a tag.
...but you didn't push the tag yet? Or is this WiP?
Sorry, I forgot I need to push the tag. It should be fixed now.

Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


Zoran
 

I finally was able to make the viable .config... For the previous
rt-kernel for BBB.

root@beaglebone:~# uname -a
Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18
GMT 2019 armv7l GNU/Linux

It was very tough and rough... But I have it! Now I need to abandon
this effort, since I have another immediate things to do!

Well...

Zoran
_______

On Tue, Jul 23, 2019 at 11:06 PM Pavel Machek <pavel@denx.de> wrote:

Hi!

Trees are available at

https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt-rebase

https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt

And their content should be identical. I attempted to tag it in a way
consistent with previous releases, and I attempted to sign a tag.
...but you didn't push the tag yet? Or is this WiP?
Sorry, I forgot I need to push the tag. It should be fixed now.

Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev


Pavel Machek
 

Hi!

I finally was able to make the viable .config... For the previous
rt-kernel for BBB.

root@beaglebone:~# uname -a
Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18
GMT 2019 armv7l GNU/Linux

It was very tough and rough... But I have it! Now I need to abandon
this effort, since I have another immediate things to do!
No problem. You should be able to use same .config with the new
kernel...

Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


Zoran
 

No problem. You should be able to use same .config
with the new kernel...
U R targeting 4.19.50-cip3-rt2... I do agree 100%, but I have some
problems to do rt-tests (connecting BBB target to my VM).

Please, stay tuned. I'll resolve these problems ASAP (if ?, then Ill
publish the results) . Then I need to leave it for the time been.

Zoran
_______

On Wed, Jul 24, 2019 at 1:53 PM Pavel Machek <pavel@denx.de> wrote:

Hi!

I finally was able to make the viable .config... For the previous
rt-kernel for BBB.

root@beaglebone:~# uname -a
Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18
GMT 2019 armv7l GNU/Linux

It was very tough and rough... But I have it! Now I need to abandon
this effort, since I have another immediate things to do!
No problem. You should be able to use same .config with the new
kernel...

Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


Zoran
 

(limitations): I could NOT connect with ETH to target (something is
wrongly set with my local.conf for YOCTO rootfs)...

Here is my approximate recipe for rootfs I am using for the test
(initramfs) for your inspection (it is thud, local.conf moved to
warrior):
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/bbb-releases/bbb-warrior/local.conf

More or/and less, here are results after approximately 63 minutes of
running rt-tests:

root@beaglebone:~# uname -a
Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18
GMT 2019 armv7l GNU/Linux
_______
policy: fifo: loadavg: 291.28 287.63 267.78 21/486 30014
policy: fifo: loadavg: 186.97 215.90 243.41 5/458 22788
policy: fifo: loadavg: 248.16 243.95 244.63 194/486 8800
policy: fifo: loadavg: 283.55 240.50 243.74 9/318 2383
T: 0 (13903) P:80 I:1000 C:3942593 Min: 19 Act: 52 Avg: 45 Max: 93
T: 0 (13903) P:80 I:1000 C:3785664 Min: 19 Act: 44 Avg: 45 Max: 935
T: 0 (13903) P:80 I:1000 C:3716107 Min: 19 Act: 60 Avg: 45 Max: 936
policy: fifo: loadavg: 222.11 176.72 90.66 5/213 21249
T: 0 (13903) P:80 I:1000 C:2213895 Min: 19 Act: 38 Avg: 46 Max: 905
T: 0 (13903) P:80 I:1000 C: 181403 Min: 21 Act: 49 Avg: 45 Max: 90
T: 0 (13903) P:80 I:1000 C: 181320 Min: 21 Act: 29 Avg: 45 Max: 90

MIN 19 ns, MAX 936 ns (3x over 900 ns)... I would be really concerned
about MAX over > 900 ns!

On 4.4 RT kernel I had some much better # such as: Min: 19 Act:
44 Avg: 42 Max: 81

I need to do more... No time anymore now!

Best Regards,
Zoran
_______


On Wed, Jul 24, 2019 at 3:00 PM Zoran S
<zoran.stojsavljevic.de@gmail.com> wrote:

No problem. You should be able to use same .config
with the new kernel...
U R targeting 4.19.50-cip3-rt2... I do agree 100%, but I have some
problems to do rt-tests (connecting BBB target to my VM).

Please, stay tuned. I'll resolve these problems ASAP (if ?, then Ill
publish the results) . Then I need to leave it for the time been.

Zoran
_______

On Wed, Jul 24, 2019 at 1:53 PM Pavel Machek <pavel@denx.de> wrote:

Hi!

I finally was able to make the viable .config... For the previous
rt-kernel for BBB.

root@beaglebone:~# uname -a
Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18
GMT 2019 armv7l GNU/Linux

It was very tough and rough... But I have it! Now I need to abandon
this effort, since I have another immediate things to do!
No problem. You should be able to use same .config with the new
kernel...

Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


daniel.sangorrin@...
 

Hello Zoran

From: cip-dev-bounces@lists.cip-project.org <cip-dev-
(limitations): I could NOT connect with ETH to target (something is
wrongly set with my local.conf for YOCTO rootfs)...
Why don't you use ISAR CIP Core?
https://gitlab.com/cip-project/cip-core/isar-cip-core

Thanks,
Daniel


Here is my approximate recipe for rootfs I am using for the test
(initramfs) for your inspection (it is thud, local.conf moved to
warrior):
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/bbb-releases/bbb-warrior/local.conf

More or/and less, here are results after approximately 63 minutes of
running rt-tests:

root@beaglebone:~# uname -a
Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18
GMT 2019 armv7l GNU/Linux
_______
policy: fifo: loadavg: 291.28 287.63 267.78 21/486 30014
policy: fifo: loadavg: 186.97 215.90 243.41 5/458 22788
policy: fifo: loadavg: 248.16 243.95 244.63 194/486 8800
policy: fifo: loadavg: 283.55 240.50 243.74 9/318 2383
T: 0 (13903) P:80 I:1000 C:3942593 Min: 19 Act: 52 Avg: 45 Max: 93
T: 0 (13903) P:80 I:1000 C:3785664 Min: 19 Act: 44 Avg: 45 Max: 935
T: 0 (13903) P:80 I:1000 C:3716107 Min: 19 Act: 60 Avg: 45 Max: 936
policy: fifo: loadavg: 222.11 176.72 90.66 5/213 21249
T: 0 (13903) P:80 I:1000 C:2213895 Min: 19 Act: 38 Avg: 46 Max: 905
T: 0 (13903) P:80 I:1000 C: 181403 Min: 21 Act: 49 Avg: 45 Max: 90
T: 0 (13903) P:80 I:1000 C: 181320 Min: 21 Act: 29 Avg: 45 Max: 90

MIN 19 ns, MAX 936 ns (3x over 900 ns)... I would be really concerned
about MAX over > 900 ns!

On 4.4 RT kernel I had some much better # such as: Min: 19 Act:
44 Avg: 42 Max: 81

I need to do more... No time anymore now!

Best Regards,
Zoran
_______


On Wed, Jul 24, 2019 at 3:00 PM Zoran S
<zoran.stojsavljevic.de@gmail.com> wrote:

No problem. You should be able to use same .config
with the new kernel...
U R targeting 4.19.50-cip3-rt2... I do agree 100%, but I have some
problems to do rt-tests (connecting BBB target to my VM).

Please, stay tuned. I'll resolve these problems ASAP (if ?, then Ill
publish the results) . Then I need to leave it for the time been.

Zoran
_______

On Wed, Jul 24, 2019 at 1:53 PM Pavel Machek <pavel@denx.de> wrote:

Hi!

I finally was able to make the viable .config... For the previous
rt-kernel for BBB.

root@beaglebone:~# uname -a
Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18
GMT 2019 armv7l GNU/Linux

It was very tough and rough... But I have it! Now I need to abandon
this effort, since I have another immediate things to do!
No problem. You should be able to use same .config with the new
kernel...

Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev


Zoran
 

Why don't you use ISAR CIP Core?
https://gitlab.com/cip-project/cip-core/isar-cip-core
With all due respect (and I do really respect prominent CIP founders),
I need to make this problem solved solely by myself...

But, anyway, thank you for the advise! :-)

Zoran
_______

On Thu, Jul 25, 2019 at 2:22 AM <daniel.sangorrin@toshiba.co.jp> wrote:

Hello Zoran

From: cip-dev-bounces@lists.cip-project.org <cip-dev-
(limitations): I could NOT connect with ETH to target (something is
wrongly set with my local.conf for YOCTO rootfs)...
Why don't you use ISAR CIP Core?
https://gitlab.com/cip-project/cip-core/isar-cip-core

Thanks,
Daniel


Here is my approximate recipe for rootfs I am using for the test
(initramfs) for your inspection (it is thud, local.conf moved to
warrior):
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/bbb-releases/bbb-warrior/local.conf

More or/and less, here are results after approximately 63 minutes of
running rt-tests:

root@beaglebone:~# uname -a
Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18
GMT 2019 armv7l GNU/Linux
_______
policy: fifo: loadavg: 291.28 287.63 267.78 21/486 30014
policy: fifo: loadavg: 186.97 215.90 243.41 5/458 22788
policy: fifo: loadavg: 248.16 243.95 244.63 194/486 8800
policy: fifo: loadavg: 283.55 240.50 243.74 9/318 2383
T: 0 (13903) P:80 I:1000 C:3942593 Min: 19 Act: 52 Avg: 45 Max: 93
T: 0 (13903) P:80 I:1000 C:3785664 Min: 19 Act: 44 Avg: 45 Max: 935
T: 0 (13903) P:80 I:1000 C:3716107 Min: 19 Act: 60 Avg: 45 Max: 936
policy: fifo: loadavg: 222.11 176.72 90.66 5/213 21249
T: 0 (13903) P:80 I:1000 C:2213895 Min: 19 Act: 38 Avg: 46 Max: 905
T: 0 (13903) P:80 I:1000 C: 181403 Min: 21 Act: 49 Avg: 45 Max: 90
T: 0 (13903) P:80 I:1000 C: 181320 Min: 21 Act: 29 Avg: 45 Max: 90

MIN 19 ns, MAX 936 ns (3x over 900 ns)... I would be really concerned
about MAX over > 900 ns!

On 4.4 RT kernel I had some much better # such as: Min: 19 Act:
44 Avg: 42 Max: 81

I need to do more... No time anymore now!

Best Regards,
Zoran
_______


On Wed, Jul 24, 2019 at 3:00 PM Zoran S
<zoran.stojsavljevic.de@gmail.com> wrote:

No problem. You should be able to use same .config
with the new kernel...
U R targeting 4.19.50-cip3-rt2... I do agree 100%, but I have some
problems to do rt-tests (connecting BBB target to my VM).

Please, stay tuned. I'll resolve these problems ASAP (if ?, then Ill
publish the results) . Then I need to leave it for the time been.

Zoran
_______

On Wed, Jul 24, 2019 at 1:53 PM Pavel Machek <pavel@denx.de> wrote:

Hi!

I finally was able to make the viable .config... For the previous
rt-kernel for BBB.

root@beaglebone:~# uname -a
Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18
GMT 2019 armv7l GNU/Linux

It was very tough and rough... But I have it! Now I need to abandon
this effort, since I have another immediate things to do!
No problem. You should be able to use same .config with the new
kernel...

Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev


Pavel Machek
 

On Wed 2019-07-24 18:06:46, Zoran S wrote:
(limitations): I could NOT connect with ETH to target (something is
wrongly set with my local.conf for YOCTO rootfs)...

Here is my approximate recipe for rootfs I am using for the test
(initramfs) for your inspection (it is thud, local.conf moved to
warrior):
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/bbb-releases/bbb-warrior/local.conf

More or/and less, here are results after approximately 63 minutes of
running rt-tests:

root@beaglebone:~# uname -a
Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18
GMT 2019 armv7l GNU/Linux
_______
policy: fifo: loadavg: 291.28 287.63 267.78 21/486 30014
policy: fifo: loadavg: 186.97 215.90 243.41 5/458 22788
policy: fifo: loadavg: 248.16 243.95 244.63 194/486 8800
policy: fifo: loadavg: 283.55 240.50 243.74 9/318 2383
T: 0 (13903) P:80 I:1000 C:3942593 Min: 19 Act: 52 Avg: 45 Max: 93
T: 0 (13903) P:80 I:1000 C:3785664 Min: 19 Act: 44 Avg: 45 Max: 935
T: 0 (13903) P:80 I:1000 C:3716107 Min: 19 Act: 60 Avg: 45 Max: 936
policy: fifo: loadavg: 222.11 176.72 90.66 5/213 21249
T: 0 (13903) P:80 I:1000 C:2213895 Min: 19 Act: 38 Avg: 46 Max: 905
T: 0 (13903) P:80 I:1000 C: 181403 Min: 21 Act: 49 Avg: 45 Max: 90
T: 0 (13903) P:80 I:1000 C: 181320 Min: 21 Act: 29 Avg: 45 Max: 90
Your log is corrupted, see?

If it was real, it would be

Max: 905
Max: 90

But you have

Max: 905
Max: 90

Notice the whitespace.

MIN 19 ns, MAX 936 ns (3x over 900 ns)... I would be really concerned
about MAX over > 900 ns!
It is usec, not nsec, AFAICT.

Best regards,
Pavel

--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


Zoran
 

Your log is corrupted, see?
You are correct, I should write that these are preliminary WTH/ad-hoc
results (I need to fix/rerun these in the correct setup, I know).

It is usec, not nsec, AFAICT.
Again, correct. I wrote nsec instead usec, having in mind INTEL
technology per asm instruction. INTEL illusions/delusions in my brain.
I am trying to catch up on armv7, A8 and A9, since these gadgets
started ruling the embedded industry.

Thank you,
Zoran
_______

On Fri, Jul 26, 2019 at 11:05 PM Pavel Machek <pavel@denx.de> wrote:

On Wed 2019-07-24 18:06:46, Zoran S wrote:
(limitations): I could NOT connect with ETH to target (something is
wrongly set with my local.conf for YOCTO rootfs)...

Here is my approximate recipe for rootfs I am using for the test
(initramfs) for your inspection (it is thud, local.conf moved to
warrior):
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/bbb-releases/bbb-warrior/local.conf

More or/and less, here are results after approximately 63 minutes of
running rt-tests:

root@beaglebone:~# uname -a
Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18
GMT 2019 armv7l GNU/Linux
_______
policy: fifo: loadavg: 291.28 287.63 267.78 21/486 30014
policy: fifo: loadavg: 186.97 215.90 243.41 5/458 22788
policy: fifo: loadavg: 248.16 243.95 244.63 194/486 8800
policy: fifo: loadavg: 283.55 240.50 243.74 9/318 2383
T: 0 (13903) P:80 I:1000 C:3942593 Min: 19 Act: 52 Avg: 45 Max: 93
T: 0 (13903) P:80 I:1000 C:3785664 Min: 19 Act: 44 Avg: 45 Max: 935
T: 0 (13903) P:80 I:1000 C:3716107 Min: 19 Act: 60 Avg: 45 Max: 936
policy: fifo: loadavg: 222.11 176.72 90.66 5/213 21249
T: 0 (13903) P:80 I:1000 C:2213895 Min: 19 Act: 38 Avg: 46 Max: 905
T: 0 (13903) P:80 I:1000 C: 181403 Min: 21 Act: 49 Avg: 45 Max: 90
T: 0 (13903) P:80 I:1000 C: 181320 Min: 21 Act: 29 Avg: 45 Max: 90
Your log is corrupted, see?

If it was real, it would be

Max: 905
Max: 90

But you have

Max: 905
Max: 90

Notice the whitespace.

MIN 19 ns, MAX 936 ns (3x over 900 ns)... I would be really concerned
about MAX over > 900 ns!
It is usec, not nsec, AFAICT.

Best regards,
Pavel

--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany