From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Xenomai <xenomai@lists.linux.dev>
Subject: Re: dovetail kernel maintenance
Date: Sun, 17 Mar 2024 22:04:00 +0100 [thread overview]
Message-ID: <87a5mwa7br.fsf@xenomai.org> (raw)
In-Reply-To: <87il1stpd4.fsf@xenomai.org>
Philippe Gerum <rpm@xenomai.org> writes:
> Jan Kiszka <jan.kiszka@siemens.com> writes:
>
>> On 06.03.24 09:41, Philippe Gerum wrote:
>>>
>>> Jan Kiszka <jan.kiszka@siemens.com> writes:
>>>
>>>> On 21.02.24 19:30, Jan Kiszka wrote:
>>>>> Hi Philippe,
>>>>>
>>>>> people started to ask about updates for our kernel trees, and you
>>>>> mentioned to me before that you would focus on the last two LTS kernels.
>>>>> Right now, there are to-be-tagged updated sleeping in 6.1 and 6.6 but
>>>>> then also in 5.10 (all referring to the -rebase branches). Before taking
>>>>> over 5.10 and 5.15, I would like to clarify their state. But I would
>>>>> also like to know what is delaying the tagging of 6.1 and 6.6.
>>>>>
>>>>
>>>> Gentle ping for this question.
>>>>
>>>
>>> Well, my posts to the mailing list from my usual address have been
>>> rejected a couple of weeks ago due to smtp authentication issues it
>>> seems, which are now (mostly) sorted out, I thought you did receive this
>>> reply as a direct recipient though. Looks like you did not. So here it
>>> is.
>>>
>>> PS: Since this reply was written, the x86 status with respect to the
>>> Dovetail port to v6.8-rc7 has improved. Still in the process of
>>> rewriting the arm64/fpsimd stuff.
>>>
>>
>> Let us know where exactly help could be provided. I just want to avoid
>> duplicate attempts, so the development should be coordinated publicly.
>>
>
> Addressing [1] comes to mind. As I said in this thread, one could use
> the same logic which allows x86 to support preemption of the helpers for
> in-kernel fpu by the real-time core. However, I have to upgrade the
> basic arm64/fpsimd port to v6.8 before someone else can handle this
> task. ETA, hopefully next week.
>
Dovetail and EVL ports to v6.8 are now available from the usual repos
for all the supported architectures. Only lightly tested so far, but
things look good (arm64/fpsimd is back on track).
If CONFIG_NET_OOB is set, there are some warnings about missing function
declarations in the net/ core which are now turned on for ARM. We may
have to live with them until the generic changes required for enabling
the UDP support in the xenomai4 netstack are merged. Significant changes
are pending in this area.
--
Philippe.
prev parent reply other threads:[~2024-03-17 21:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 18:30 dovetail kernel maintenance Jan Kiszka
2024-03-06 7:05 ` Jan Kiszka
2024-03-06 8:41 ` Philippe Gerum
2024-03-07 8:07 ` Jan Kiszka
2024-03-11 21:30 ` Philippe Gerum
2024-03-17 21:04 ` Philippe Gerum [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a5mwa7br.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=jan.kiszka@siemens.com \
--cc=xenomai@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).