As discussed, we need to add a separate control to manage whether the
monotonic or the real-time clock should be used for GPIO timestamping.
Patch 1 adds this, keeping the default to monotonic. This can be added
to 3.1.x stable as well. Patch 2 aligns the default to the rest of
Xenomai, using
From: Jan Kiszka
This is in line with other drivers and should avoid surprises like [1]
in the future.
[1] https://xenomai.org/pipermail/xenomai/2021-June/045661.html
Signed-off-by: Jan Kiszka
---
include/rtdm/uapi/gpio.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 13.08.21 17:04, Fabrice Fontaine via Xenomai wrote:
> Allow the user to disable demo and testsuite to decrease compilation
> time and save disk space.
>
> Signed-off-by: Fabrice Fontaine
> ---
> Makefile.am | 12 ++--
> configure.ac | 12
> 2 files changed, 22
From: Jan Kiszka
This should help to catch breakages of the compat case.
We only need to build userland as the kernel is already covered by the
x86 job.
Signed-off-by: Jan Kiszka
---
.gitlab-ci.yml | 19 ++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git
From: Jan Kiszka
The y2038 test will pass the syscall number as variable. This is in
conflict with immediate constraint the current wrapper uses so far.
Relax it, the compiler will still use immediate where possible.
Signed-off-by: Jan Kiszka
---
Adding this before your series in next.
On 13.08.21 17:04, Fabrice Fontaine via Xenomai wrote:
> Fix the following build failures on arc and riscv32 (same issue in
> demo/alchemy/altency.c and testsuite/latency/latency.c):
>
> altency.c: In function ‘display’:
> altency.c:262:21: error: format ‘%ld’ expects argument of type ‘long int’,
From: Jan Kiszka
This was missed by 1ba9500dd5.
Signed-off-by: Jan Kiszka
---
recipes-kernel/linux/linux-xenomai_latest.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/recipes-kernel/linux/linux-xenomai_latest.bb
b/recipes-kernel/linux/linux-xenomai_latest.bb
index 09df461..836fa52
On 13.08.21 16:33, Florian Bezdeka wrote:
> According to POSIX message queues have kernel persistence, which means
> they are not cleaned up until the next reboot.
>
> The test has a mq_unlink() as "precondition", so it will clean up
> failed test runs silently but /proc/xenomai/registry/usage
On 13.08.21 13:36, Florian Bezdeka wrote:
> The tracing support was disabled on arm64 but enabled on all other
> targets we support. Taking the trace configuration from armhf to be able
> to trace on arm64 as well.
>
> Signed-off-by: Florian Bezdeka
> ---
>
On 13.08.21 15:17, Fabrice Fontaine wrote:
> Le ven. 13 août 2021 à 10:54, Jan Kiszka a écrit :
>>
>> On 13.08.21 10:12, Fabrice Fontaine via Xenomai wrote:
>>> Allow the user to disable demo and testsuite to avoid the following
>>> build failures on arc and riscv32:
>>
>> Are you working on
From: Jan Kiszka
Duplicate slashes cause no harm, but a missing can lead to confusing
errors.
Signed-off-by: Jan Kiszka
---
Inserted before "ci: Add default for S3_BUCKET_URL" which didn't add a
slash, thus triggered this issue.
scripts/deploy_to_aws.sh | 2 +-
1 file changed, 1
From: Jan Kiszka
This corresponds to the default for LAVA_ARTIFACTS_URL.
Signed-off-by: Jan Kiszka
---
Changes in v2:
- reorder to fix failing consistency check before default was assigned
scripts/deploy_to_aws.sh | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
On 13.08.21 10:12, Fabrice Fontaine via Xenomai wrote:
> Allow the user to disable demo and testsuite to avoid the following
> build failures on arc and riscv32:
Are you working on ports to those archs? Or is xenomai userland just
prematurely built for those in buildroot?
>
> latency.c: In
On 13.08.21 08:53, Jan Kiszka via Xenomai wrote:
> On 12.08.21 18:28, Florian Bezdeka wrote:
>> From: Song Chen
>>
>> Add a syscall specific for mq_timedreceive64 with 64bit time_t.
>>
>> Signed-off-by: Song Chen
>> [Florian:
>> - Reformat c
On 12.08.21 09:09, Florian Bezdeka wrote:
> Hi!
>
> Just another y2038 related syscall, once again based on v1 sent out by
> Song and rebased to current next with some code- and test-cleanups applied.
>
> @Song:
> This one was the last one in my inbox. Please make sure that all
> following
On 11.08.21 10:11, Florian Bezdeka wrote:
> Hi!
>
> Just another y2038 related syscall, once again based on v1 sent out by
> Song and rebased to current next.
>
> Best regards,
> Florian
>
> Florian Bezdeka (2):
> y2038: cobalt/posix/monitor: Adding monitor_wait64
> y2038:
On 12.08.21 18:38, Florian Bezdeka wrote:
> According to POSIX message queues have kernel persistence, which means
> they are not cleaned up until the next reboot.
>
> The test has a mq_unlink() as "precondition", so it will clean up
> failed test runs silently but /proc/xenomai/registry/usage
On 12.08.21 18:28, Florian Bezdeka wrote:
> From: Song Chen
>
> Add a syscall specific for mq_timedreceive64 with 64bit time_t.
>
> Signed-off-by: Song Chen
> [Florian:
> - Reformat commit msg
> - relocate code
> - tracing
> - fix syscall declarations
> ]
> Signed-off-by: Florian
On 12.08.21 16:39, Bezdeka, Florian (T RDA IOT SES-DE) wrote:
> On Thu, 2021-08-12 at 14:45 +0200, Jan Kiszka wrote:
>> On 12.08.21 14:39, Bezdeka, Florian (T RDA IOT SES-DE) wrote:
>>> Hi all,
>>>
>>> I just noticed that the posix_select test of smokey is leaking one
>>> registry element:
>>>
>>>
On 12.08.21 14:39, Bezdeka, Florian (T RDA IOT SES-DE) wrote:
> Hi all,
>
> I just noticed that the posix_select test of smokey is leaking one
> registry element:
>
> $ cat /proc/xenomai/registry/usage
> 8/512
>
> $ /smokey --run=posix_select
> posix_select OK
>
> $ cat
On 12.08.21 07:50, C Smith wrote:
> Hi Jan,Thanks for your prompt reply. I reduced my very large app to
> about 200 lines, it only starts one periodic process. but I still get
> this error during linkage:
>
> /usr/xenomai/lib/xenomai/bootstrap.o: In function `xenomai_main':
>
From: Jan Kiszka
No need to encode the European zone here into the default, let AWS sort
this out.
Signed-off-by: Jan Kiszka
---
scripts/run-lava-tests.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/run-lava-tests.sh b/scripts/run-lava-tests.sh
index
From: Jan Kiszka
This corresponds to the default for LAVA_ARTIFACTS_URL.
Signed-off-by: Jan Kiszka
---
scripts/deploy_to_aws.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/deploy_to_aws.sh b/scripts/deploy_to_aws.sh
index 5a5b29a..98deebc 100755
---
On 10.08.21 20:21, Philippe Gerum via Xenomai wrote:
>
> I won't join the Xenomai meeting this week, so this is the latest news
> from Dovetail and Xenomai 4:
>
> Dovetail runs on top of v5.14-rc5 (arm, arm64 and x86_64), the code is
> visible from the v5.14-dovetail-rebase branch at [1]. As
On 10.08.21 17:27, Florian Bezdeka wrote:
> Hi!
>
> Here comes the next y2038 related syscall implementation. Once again
> based on v1 sent out by Song. I had to rework the patches a bit, mostly
> to stay POSIX compatible (EAGAIN vs. ETIMEOUT) and necessary test
> adjustments and improvements.
>
On 06.08.21 10:50, Jan Kiszka via Xenomai wrote:
> On 02.08.21 17:43, Jan Kiszka via Xenomai wrote:
>> From: Jan Kiszka
>>
>> This is a temporary hack: Our AWS runners see a lot of DNS errors for
>> deb.debian.org. Let's see if they are less with this server.
>
On 10.08.21 12:33, Jan Kiszka via Xenomai wrote:
> On 10.08.21 12:23, Florian Bezdeka wrote:
>> Hi!
>>
>> This series is based on the series posted by Song some time ago. The
>> testing part has been heavily reworked. Details are mentioned in the
>> descript
On 10.08.21 12:23, Florian Bezdeka wrote:
> Hi!
>
> This series is based on the series posted by Song some time ago. The
> testing part has been heavily reworked. Details are mentioned in the
> description of the last patch.
>
> @Jan: Patch 1 and 2 are re-sends. They are not directly related to
From: Jan Kiszka
Do not fail the test if packets arrive late or are lost due to the
delays a VM, specifically an emulator like QEMU, may bring. Only if all
packets are lost, something is wrong and should be reported.
Signed-off-by: Jan Kiszka
---
This now replaces "testsuite/smokey:
From: Jan Kiszka
Since gcc-9, direct usage of r7 is in conflict with compiler
allocations. Skip it.
This pushes mach_arm_nodiv_llimd beyond r10. r11 is reserved as frame
pointer, but r12 should be fine between function calls and long branches
like in this case.
Signed-off-by: Jan Kiszka
---
On 09.08.21 17:11, Jan Kiszka via Xenomai wrote:
> On 09.08.21 17:09, Philippe Gerum wrote:
>>
>> Jan Kiszka writes:
>>
>>> On 07.08.21 17:52, Jan Kiszka via Xenomai wrote:
>>>> From: Jan Kiszka
>>>>
>>>> Since gcc-9, dire
On 09.08.21 17:09, Philippe Gerum wrote:
>
> Jan Kiszka writes:
>
>> On 07.08.21 17:52, Jan Kiszka via Xenomai wrote:
>>> From: Jan Kiszka
>>>
>>> Since gcc-9, direct usage of r7 is in conflict with compiler
>>> allocations. Skip it.
>>&
On 07.08.21 17:52, Jan Kiszka via Xenomai wrote:
> From: Jan Kiszka
>
> Since gcc-9, direct usage of r7 is in conflict with compiler
> allocations. Skip it.
>
> Signed-off-by: Jan Kiszka
> ---
> .../arch/arm/include/asm/xenomai/uapi/arith.h | 14 +++
On 06.08.21 15:00, Jan Kiszka via Xenomai wrote:
> Hi all,
>
> just wanted to debug the RTnet issues we now see in CI on arm and arm64.
> I picked arm as first target, but that apparently starts to break with
> gcc-9 or newer (tried 9.2 and 10.2):
>
> make[5]: Entering di
From: Jan Kiszka
Converting them into inline functions helps to avoid clobbering of w8.
Without this, the compiler may squeeze function calls between the setup
of __scno in w8 and the actually submission of the syscall. Seen with
the smokey y2038 testcase.
Signed-off-by: Jan Kiszka
---
Close
On 09.08.21 10:01, Philippe Gerum wrote:
>
> Philippe Gerum writes:
>
>> Jan Kiszka writes:
>>
>>> Hi all,
>>>
>>> the failing y2038 testcase we see in CI [1] is caused by another problem
>>> of our syscall wrappers, this time on arm64:
>>>
>>> /* Timeout is never read by the kernel,
Hi all,
the failing y2038 testcase we see in CI [1] is caused by another problem
of our syscall wrappers, this time on arm64:
/* Timeout is never read by the kernel, so NULL should be OK */
ret = XENOMAI_SYSCALL5(sc_nr, mq, msg, strlen(msg), 0, NULL);
235c: b940dfe0
From: Jan Kiszka
The status value is the pointer, not where the pointer points to.
Signed-off-by: Jan Kiszka
---
Not yet resolving the unexpected assertion, though.
testsuite/smokey/y2038/syscall-tests.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Jan Kiszka
We modify sshd_config, so we need the server to be installed already.
passwd is no longer needed, though.
Signed-off-by: Jan Kiszka
---
recipes-core/customizations/customizations.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On 08.08.21 19:21, Philippe Gerum wrote:
>
> Jan Kiszka writes:
>
>> On 07.08.21 19:00, Philippe Gerum wrote:
>>>
>>> Jan Kiszka writes:
>>>
Hi all,
just wanted to debug the RTnet issues we now see in CI on arm and arm64.
I picked arm as first target, but that apparently
From: Jan Kiszka
We must not write more than what was allocated and reported via
msg_namelen by userspace. We may truncate, though, then reporting what
would have been written if there had been enough space.
Signed-off-by: Jan Kiszka
---
kernel/drivers/net/stack/ipv4/udp/udp.c | 12
From: Jan Kiszka
The msg struct passed to the recvmsg handler for udp and packet sockets
is not located in userspace. Therefore, we must not use rtnet_put_arg to
update its content, it may fail on some archs, namely arm and arm64.
Just assign, the syscall entry function will take care of copying
On 02.08.21 18:56, Jan Kiszka via Xenomai wrote:
> From: Jan Kiszka
>
> Make sure that we consider all pids taken from or sent to userspace via
> syscalls as virtual. That means converting them to global pids before
> processing them or converting them back to virtual pids
On 07.08.21 19:00, Philippe Gerum wrote:
>
> Jan Kiszka writes:
>
>> Hi all,
>>
>> just wanted to debug the RTnet issues we now see in CI on arm and arm64.
>> I picked arm as first target, but that apparently starts to break with
>> gcc-9 or newer (tried 9.2 and 10.2):
>>
>> make[5]: Entering
From: Jan Kiszka
Since gcc-9, direct usage of r7 is in conflict with compiler
allocations. Skip it.
Signed-off-by: Jan Kiszka
---
.../arch/arm/include/asm/xenomai/uapi/arith.h | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git
On 07.08.21 09:43, C Smith via Xenomai wrote:
> I can compile but not link my xenomai app. I get:
> /usr/bin/ld: skipping incompatible /usr/xenomai/lib/libtrank.so when
> searching for -ltrank
> /usr/bin/ld: skipping incompatible /usr/xenomai/lib/libcobalt.so when
> searching for -lcobalt
> etc.
>
From: Jan Kiszka
This is default-on in Debian 11 and triggers in heapobj_pkg_init_shared
or heapobj_bind_session without adding value - we truncate for good
reasons.
Signed-off-by: Jan Kiszka
---
configure.ac | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/configure.ac
On 06.08.21 18:16, Jan Kiszka wrote:
> On 06.08.21 15:34, Philippe Gerum wrote:
>>
>> Jan Kiszka writes:
>>
>>> On 06.08.21 15:09, Philippe Gerum wrote:
Jan Kiszka writes:
> Hi all,
>
> just wanted to debug the RTnet issues we now see in CI on arm and arm64.
> I
On 06.08.21 15:34, Philippe Gerum wrote:
>
> Jan Kiszka writes:
>
>> On 06.08.21 15:09, Philippe Gerum wrote:
>>>
>>> Jan Kiszka writes:
>>>
Hi all,
just wanted to debug the RTnet issues we now see in CI on arm and arm64.
I picked arm as first target, but that apparently
On 06.08.21 15:09, Philippe Gerum wrote:
>
> Jan Kiszka writes:
>
>> Hi all,
>>
>> just wanted to debug the RTnet issues we now see in CI on arm and arm64.
>> I picked arm as first target, but that apparently starts to break with
>> gcc-9 or newer (tried 9.2 and 10.2):
>>
>> make[5]: Entering
Hi all,
just wanted to debug the RTnet issues we now see in CI on arm and arm64.
I picked arm as first target, but that apparently starts to break with
gcc-9 or newer (tried 9.2 and 10.2):
make[5]: Entering directory '/xenomai/lib/cobalt/arch/arm'
CC libarch_la-features.lo
features.c: In
On 05.08.21 16:41, Jan Kiszka via Xenomai wrote:
> On 05.08.21 14:29, Q. Gylstorff wrote:
>> From: Quirin Gylstorff
>>
>> The beagle bone black does most[1] of the time not boot ipipe 4.4 + xenomai
>> 3.0.x if
>> the following kernel configuration elements ar
On 02.08.21 17:43, Jan Kiszka via Xenomai wrote:
> From: Jan Kiszka
>
> This is a temporary hack: Our AWS runners see a lot of DNS errors for
> deb.debian.org. Let's see if they are less with this server.
>
> Signed-off-by: Jan Kiszka
> ---
>
> Seems to work, though
On 06.08.21 10:23, Chen, Hongzhan wrote:
>
>
> -Original Message-
>> From: Jan Kiszka
>> Sent: Friday, August 6, 2021 4:12 PM
>> To: Chen, Hongzhan ; Xenomai
>> Subject: Re: [PATCH] testsuite/smokey: net: Load rtnet module if missing
>>
>> On 06.08.21 09:48, Chen, Hongzhan wrote:
>>>
On 06.08.21 09:48, Chen, Hongzhan wrote:
>
>
>> -Original Message-
>> From: Jan Kiszka
>> Sent: Friday, August 6, 2021 3:38 PM
>> To: Xenomai
>> Cc: Chen, Hongzhan
>> Subject: [PATCH] testsuite/smokey: net: Load rtnet module if missing
>>
>> From: Jan Kiszka
>>
>> This allows to run
On 05.08.21 07:01, Jan Kiszka via Xenomai wrote:
> On 05.08.21 02:39, Chen, Hongzhan wrote:
>>
>>
>>> -Original Message-
>>> From: Jan Kiszka
>>> Sent: Wednesday, August 4, 2021 6:20 PM
>>> To: Chen, Hongzhan ; xenomai@xenomai.org
>&g
From: Jan Kiszka
This allows to run RTnet tests if the core is built as module but not
yet loaded at the start of the test.
For that, silence error reports of 'modprobe rtnet'.
Signed-off-by: Jan Kiszka
---
This should do the trick as well, just a bit simpler.
Please tag the patch with the subsystem, in this case "drivers/gpio:".
On 05.08.21 17:15, François Legal via Xenomai wrote:
> This patch allows to select which time source (monotonic/realtime) is used to
> timestamp GPIO events.
> The time source used to be monotonic which is the opposite of
On 05.08.21 14:29, Q. Gylstorff wrote:
> From: Quirin Gylstorff
>
> The beagle bone black does most[1] of the time not boot ipipe 4.4 + xenomai
> 3.0.x if
> the following kernel configuration elements are active:
> - CONFIG_RAW_PRINTK
> - CONFIG_DEBUG_LL
> - CONFIG_IPIPE_DEBUG
> -
On 05.08.21 09:23, Philippe Gerum wrote:
>
> Jan Kiszka writes:
>
>> On 04.08.21 09:35, Philippe Gerum via Xenomai wrote:
>>> From: Philippe Gerum
>>>
>>> Signed-off-by: Philippe Gerum
>>> ---
>>> COPYING | 45 +
>>> 1 file changed, 45
On 05.08.21 08:12, Chen, Hongzhan wrote:
>
>
>
>
On 05.08.21 07:32, Chen, Hongzhan wrote:
>
>
>> -Original Message-
>> From: Jan Kiszka
>> Sent: Thursday, August 5, 2021 1:26 PM
>> To: Chen, Hongzhan ; xenomai@xenomai.org
>> Subject: Re: [PATCH V2] testsuite/smokey: net: load rtnet module if it has
>> not been loaded
>>
>> On
On 05.08.21 07:21, Chen, Hongzhan wrote:
>
>
>> -Original Message-
>> From: Jan Kiszka
>> Sent: Thursday, August 5, 2021 1:01 PM
>> To: Chen, Hongzhan ; xenomai@xenomai.org
>> Subject: Re: [PATCH V2] testsuite/smokey: net: load rtnet module if it has
>> not been loaded
>>
>> On
On 05.08.21 02:39, Chen, Hongzhan wrote:
>
>
>> -Original Message-
>> From: Jan Kiszka
>> Sent: Wednesday, August 4, 2021 6:20 PM
>> To: Chen, Hongzhan ; xenomai@xenomai.org
>> Subject: Re: [PATCH 2/2] testsuite/smokey: net_client: skip late packet
>> error in vm mode
>>
>> On
On 05.08.21 05:13, Hongzhan Chen via Xenomai wrote:
> Before checking net config, rtnet should be ready.
>
> Signed-off-by: Hongzhan Chen
>
> diff --git a/testsuite/smokey/net_common/setup.c
> b/testsuite/smokey/net_common/setup.c
> index 1badabdfb..a0512b00d 100644
> ---
On 04.08.21 09:35, Philippe Gerum via Xenomai wrote:
> From: Philippe Gerum
>
> Signed-off-by: Philippe Gerum
> ---
> COPYING | 45 +
> 1 file changed, 45 insertions(+)
> create mode 100644 COPYING
>
> diff --git a/COPYING b/COPYING
> new file mode
On 04.08.21 16:29, Gylstorff Quirin wrote:
>> But thanks for debugging this. Maybe also clarify that the board
>> generally does not boot, but sometimes it still does.
>
> My target never boots with xenomai-images
> b06f6eeef11500b6bce55a1a1e1e27e43fc3fd77.
>
This one, e.g., did so:
On 04.08.21 04:47, Hongzhan Chen via Xenomai wrote:
> In vm mode, skip late packet error in functional test to avoid
> test failure.
>
> Signed-off-by: Hongzhan Chen
>
> diff --git a/testsuite/smokey/net_common/client.c
> b/testsuite/smokey/net_common/client.c
> index d13d72918..752ea55ed
On 04.08.21 04:47, Hongzhan Chen via Xenomai wrote:
> Before checking net config, rtnet should be ready.
>
> Signed-off-by: Hongzhan Chen
>
> diff --git a/testsuite/smokey/net_common/setup.c
> b/testsuite/smokey/net_common/setup.c
> index 1badabdfb..719d8175f 100644
> ---
On 04.08.21 02:32, Chen, Hongzhan wrote:
>
>
>> -Original Message-
>> From: Jan Kiszka
>> Sent: Tuesday, August 3, 2021 5:37 PM
>> To: Chen, Hongzhan ; xenomai@xenomai.org
>> Subject: Re: xenomai warning after upgrade to linux 5.4.115
>>
&g
On 03.08.21 13:18, Lange Norbert via Xenomai wrote:
> Hello,
>
> There is some bigger kernel oops when an rtnet device is unbound from
> linux but still accessible via ioctl.
> Effect and backtrace depends on timing, usually the rt_igb module will not
> decrease its reference count, and a
On 29.07.21 10:02, Jan Kiszka via Xenomai wrote:
> On 29.07.21 08:43, Chen, Hongzhan wrote:
>> After we upgraded our linux to 5.4.115 from 5.4.76 and rebased IPIPE
>> patchset for xenomai 3.1.X, there is xenomai warning
>> printed as in attached xenomai_warning_on_linux5.4
On 03.08.21 09:53, Chen, Hongzhan wrote:
>
>
>> -Original Message-
>> From: Jan Kiszka
>> Sent: Tuesday, August 3, 2021 3:40 PM
>> To: Chen, Hongzhan ; xenomai@xenomai.org
>> Subject: Re: about RTnet* smokey test skipped issue on Qemu
>>
>> On 03.08.21 08:46, Chen, Hongzhan wrote:
>>>
On 03.08.21 08:46, Chen, Hongzhan wrote:
>
>
>> -Original Message-
>> From: Jan Kiszka
>> Sent: Tuesday, August 3, 2021 12:59 PM
>> To: Chen, Hongzhan ; xenomai@xenomai.org
>> Subject: Re: about RTnet* smokey test skipped issue on Qemu
>>
>> On 03.08.21 06:31, Chen, Hongzhan wrote:
>>>
On 03.08.21 06:31, Chen, Hongzhan wrote:
> Firstly, I found that all smokey tests including RTnet* pass on bare
> metal x86 platform
> but three RTnet* related test items are skipped on Qemu. After further
> debug, actually there is
> no supported rtnet device found on Qemu with current network
From: Jan Kiszka
Make sure that we consider all pids taken from or sent to userspace via
syscalls as virtual. That means converting them to global pids before
processing them or converting them back to virtual pids in the caller's
namespace before reporting them. We also need to switch thread
On 22.07.21 16:15, Jan Kiszka via Xenomai wrote:
> On 22.07.21 14:07, MONTET Julien wrote:
>> Hi,
>>
>> I tested all of your patches last week, and it did not change anything.
>> Compiling the Xenomai libraries directly on Docker didn't solve the issue.
>>
>
On 02.08.21 10:14, Jan Kiszka via Xenomai wrote:
> On 28.07.21 09:27, Jean-Baptiste Trédez via Xenomai wrote:
>> Current fec driver does not build on xenomai 3 and on recent kernel (ex :
>> 5.4). This driver was completely rewritten on mainline kernel.
>> This work uses prev
On 02.08.21 12:29, Florian Bezdeka wrote:
> On 02.08.21 12:27, Jan Kiszka wrote:
>> On 02.08.21 12:06, Florian Bezdeka wrote:
>>> On 02.08.21 11:45, Jan Kiszka wrote:
On 31.07.21 09:08, Florian Bezdeka wrote:
> This patch was based on the patch sent out by Song and reworked.
>
From: Jan Kiszka
This is a temporary hack: Our AWS runners see a lot of DNS errors for
deb.debian.org. Let's see if they are less with this server.
Signed-off-by: Jan Kiszka
---
Seems to work, though only one run passed so far. Go this way for now?
ci/gitlab-ci-base.yml | 1 +
1 file
On 23.07.21 10:04, Philippe Gerum wrote:
>
> François Legal writes:
>
>> Le Mardi, Juin 22, 2021 12:07 CEST, Philippe Gerum a
>> écrit:
>>
>>>
>>> Jan Kiszka writes:
>>>
On 22.06.21 11:31, Philippe Gerum wrote:
>
> Jan Kiszka writes:
>
>> On 22.06.21 10:37, Philippe
From: Jan Kiszka
Addresses "cast from pointer to integer of different size".
Signed-off-by: Jan Kiszka
---
kernel/drivers/serial/rt_imx_uart.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/drivers/serial/rt_imx_uart.c
b/kernel/drivers/serial/rt_imx_uart.c
index
On 02.08.21 12:06, Florian Bezdeka wrote:
> On 02.08.21 11:45, Jan Kiszka wrote:
>> On 31.07.21 09:08, Florian Bezdeka wrote:
>>> This patch was based on the patch sent out by Song and reworked.
>>> Especially
>>> - switched from CLOCK_MONOTONIC to CLOCK_REALTIME
>>> According to POSIX this
On 02.08.21 11:09, Jan Kiszka via Xenomai wrote:
> On 28.07.21 09:27, Jean-Baptiste Trédez via Xenomai wrote:
>> Signed-off-by: Jean-Baptiste Trédez
>>
>>
>> Content :
>>
>> net: fec: add phy_reset_after_clk_enable
On 31.07.21 09:08, Florian Bezdeka wrote:
> This patch was based on the patch sent out by Song and reworked.
> Especially
> - switched from CLOCK_MONOTONIC to CLOCK_REALTIME
> According to POSIX this service is based on CLOCK_REALTIME
>
> - Fixed some mutex leaks / missing
On 31.07.21 09:19, Florian Bezdeka wrote:
> Hi all,
>
> this is kind of a re-send of the patch series originall published by
> Song. There were some things that had to be addressed:
>
> - Code formattings
> - Copy paste errors in the test suite
> - Failing / incomplete tests, missing test
On 28.07.21 09:27, Jean-Baptiste Trédez via Xenomai wrote:
> Signed-off-by: Jean-Baptiste Trédez
>
>
> Content :
>
> net: fec: add phy_reset_after_clk_enable() support
>
> Some PHYs (for example the SMSC LAN8710/LAN8720) doesn't allow turning
> the
From: Jan Kiszka
Signed-off-by: Jan Kiszka
---
.gitlab-ci.yml | 1 +
1 file changed, 1 insertion(+)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 0d354c04d7..05b226b474 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -135,6 +135,7 @@ variables:
- ./scripts/config -m
On 28.07.21 09:27, Jean-Baptiste Trédez via Xenomai wrote:
> From: Philippe Gerum
>
> This driver has three runtime modes:
>
> - full RTnet mode for all devices (default)
>
> - partial RTnet. RTnet mode only for devices which do not define/set
> the boolean "rtnet-disabled" to true in the
On 28.07.21 14:35, Hongzhan Chen via Xenomai wrote:
> Some smokey test items depend on xenomai debug and we need to switch
> it on to help smokey test pass.
>
> Signed-off-by: Hongzhan Chen
>
> diff --git a/ci/gitlab-ci-base.yml b/ci/gitlab-ci-base.yml
> index e23849d..2638dec 100644
> ---
On 31.07.21 09:08, Florian Bezdeka wrote:
> Hi!
>
> This series is based on the series posted by Song some time ago. The
> testing part has been heavily reworked. Details are mentioned in the
> description of the last patch.
>
> @Jan: Patch 1 and 2 are re-sends. They are not directly related to
On 29.07.21 16:47, Florian Bezdeka wrote:
> According to the POSIX spec the value of the timeout parameter needs
> not to be validated if the mutex/semaphore could be taken immediately.
>
> While the implementation of the semaphore timedwait (sem_timedwait())
> allowed an invalid timeout
On 29.07.21 13:29, Florian Bezdeka wrote:
> The mutex of the smokey_barrier used inside protect_handover() was
> never destroyed. This had side effects when trying to extend the test
> suite with an additional function that had a mutex located on the same
> address than the never cleaned up
On 29.07.21 09:32, François Legal wrote:
> Le Mardi, Juillet 27, 2021 18:44 CEST, Jan Kiszka a
> écrit:
>
>> On 27.07.21 14:13, François Legal wrote:
>>> Le Lundi, Juillet 26, 2021 14:01 CEST, Jan Kiszka
>>> a écrit:
>>>
On 17.05.21 11:44, François Legal via Xenomai wrote:
>
On 28.07.21 09:27, Jean-Baptiste Trédez via Xenomai wrote:
> Current fec driver does not build on xenomai 3 and on recent kernel (ex :
> 5.4). This driver was completely rewritten on mainline kernel.
> This work uses previous work from Gilles Chanteperdrix and Philippe Gerum
> (rebase over
On 28.07.21 09:28, Jean-Baptiste Trédez via Xenomai wrote:
> Signed-off-by: Jean-Baptiste Trédez
> ---
> kernel/drivers/net/drivers/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/drivers/net/drivers/Kconfig
> b/kernel/drivers/net/drivers/Kconfig
> index
On 30.07.21 18:02, Rajesh Venkataraman via Xenomai wrote:
> Hello,
>We are trying to move our embedded real time application from RTOS to
> Linux. So we first ported our RTOS application to a RT-Linux. In RT-Linux
> we have cpu isolation and run our main realtime interrupt as a pthread
> with
On 30.07.21 09:14, Bezdeka, Florian (T RDA IOT SES-DE) wrote:
> On Thu, 2021-07-29 at 19:29 +0200, Jan Kiszka wrote:
>> On 29.07.21 18:22, Bezdeka, Florian (T RDA IOT SES-DE) wrote:
>>> On Thu, 2021-07-29 at 17:45 +0200, Jan Kiszka wrote:
On 29.07.21 17:06, Philippe Gerum wrote:
>
>
On 29.07.21 18:22, Bezdeka, Florian (T RDA IOT SES-DE) wrote:
> On Thu, 2021-07-29 at 17:45 +0200, Jan Kiszka wrote:
>> On 29.07.21 17:06, Philippe Gerum wrote:
>>>
>>> Florian Bezdeka writes:
>>>
According to the POSIX spec the value of the timeout parameter needs
not to be validated
On 29.07.21 17:06, Philippe Gerum wrote:
>
> Florian Bezdeka writes:
>
>> According to the POSIX spec the value of the timeout parameter needs
>> not to be validated if the mutex/semaphore could be taken immediately.
>>
>> While the implementation of the semaphore timedwait (sem_timedwait())
>>
501 - 600 of 2528 matches
Mail list logo
