From: Frank Scheiner <frank.scheiner@web.de>
To: torvalds@linux-foundation.org
Cc: "Tomáš Glozar" <tglozar@gmail.com>,
linux-kernel@vger.kernel.org,
Linux-Arch <linux-arch@vger.kernel.org>,
linux-ia64@vger.kernel.org,
debian-ia64 <debian-ia64@lists.debian.org>,
t2@t2sde.org
Subject: Re: Linux 6.9
Date: Wed, 15 May 2024 15:44:47 +0200 [thread overview]
Message-ID: <d308ad95-bee4-4401-a6f5-27bcf5bcc52d@web.de> (raw)
In-Reply-To: <CAHk-=whnKYL-WARzrZhVTZ8RP3WZc24C9_DT7JMJooONNT2udQ@mail.gmail.com>
Dear all,
here comes the usual update on Linux/ia64:
The reason for the userland regression we mentioned last time (in [1])
was found and fixed shortly after the release of v6.8.
[1]:
https://lore.kernel.org/all/145da253-b3bc-43da-a262-a3ebdfbea5a2@web.de/
Furthermore there were no new hard regressions detected in addition to
what was reported in [2] already. If you have an ia64 machine with more
than 64 hardware threads and want to run Linux on it, get in touch with
us. :-)
[2]:
https://lore.kernel.org/linux-ia64/CAHtyXDdy5Lub_UeMQRgr8O_G-XK0_XRD3J7wVB9t9rRD5x6d4g@mail.gmail.com/
Again all ia64 machines (see [3] for a list) and platforms (HP Sim on
Ski) we have available for testing continue to work, no system support
was lost during this cycle.
[3]:
https://lore.kernel.org/all/fe5f6e9b-02a2-42e9-8151-ae4b6fdba7e3@web.de/
In the meantime gcc-14 was released, meaning that the regular
compilation and testing of Linux mainline release (candidates) switched
to gcc-15 snapshots now (starting with v6.9-rc6). Enabling LRA for the
cross-compiler continues to make **no problems** for ia64 kernels. The
same is true with the switch to binutils 2.42 since v6.9-rc2.
****
Last time ([1]) we had to report about an approaching decrease in the
number of available Linux distributions with support for ia64. This was
sad to report, also because options are important.
But don't worry, the distro options for your ia64 gear just have
increased again:
Enter **EPIC Slack** ([4]) - an unofficial "port" of Slackware for ia64
that was started recently and - though still work in progress - is
already network booting on all test machines available to us. If you're
too young to know what Slackware is, head over to [5] and learn more
about it (-;.
[4]: http://epic-slack.org/
[5]: http://www.slackware.com/
****
Thank you all for your hard work on Linux!
Cheers,
Frank et al
parent reply other threads:[~2024-05-15 13:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAHk-=whnKYL-WARzrZhVTZ8RP3WZc24C9_DT7JMJooONNT2udQ@mail.gmail.com>]
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=d308ad95-bee4-4401-a6f5-27bcf5bcc52d@web.de \
--to=frank.scheiner@web.de \
--cc=debian-ia64@lists.debian.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=t2@t2sde.org \
--cc=tglozar@gmail.com \
--cc=torvalds@linux-foundation.org \
/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).