mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frank Scheiner <frank.scheiner@web.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org,
	pavel@nabladev.com, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
	hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
	sr@sladewatkins.com, cc@epic-linux.org
Subject: Re: [PATCH 6.6 0000/1226] 6.6.145-rc2 review
Date: Thu, 23 Jul 2026 14:21:28 +0200	[thread overview]
Message-ID: <1e9a0b1d-cc4f-4ac7-ac53-478580181c99@web.de> (raw)
In-Reply-To: <2026072333-creed-overbite-b2a9@gregkh>

On 23.07.26 09:46, Greg Kroah-Hartman wrote:
> On Wed, Jul 22, 2026 at 07:25:26PM +0200, Frank Scheiner wrote:
>> [...]
>> In our fork of Linux post v6.6 we carry a replay of b4b1ddc that makes
>> the corresponding changes also for ia64. This is available on [3] (and
>> also attached to this message) and fixes the build for me.
>>
>> [3]: https://github.com/linux-ia64/linux-ia64/commit/a4085ca68e49f49f962ddff46a901ff3468574b8.patch
>>
>> Can this be included for linux-6.6.y, so it continues to build for
>> ia64 as is?
> 
> Sure, I'll queue it up.

Thanks a lot. That should fix our builds.

> Does anyone still actually use ia64 anymore?  I
> thought those systems were long dead.

Dead, no, not at all, maybe left for dead before we took over in 2023.
But still there were always people taking care of it in the years before
- keeping it alive for us. Much obliged for that. And today things look
vastly different compared to 2023. Tomas already mentioned a few things,
but let me add a few more:

Today we have it all: distributions that support ia64 (T2, EPIC Slack,
Afterglow), hardware and simulator support restored, software support
restored (e.g. Ruby, compilers and more, other things maybe only a
session with an LLM away), Tomas doing all sorts of optimization work
that wasn't done in years, other devs bringing in patches for various
bits of the ecosystem. And just recently out of nowhere ia64 emulators
popped up, one of it being QEMU based ([1]), currently emulating an
Itanium 2 system, with MP support and already working well enough for
MP package builds. There is now even another emulator that tries to
recreate a Merced based system ([2]).

[1]: https://github.com/syunnPC/qemu-system-ia64/

[2]: https://github.com/hotlandsoftware/gemu/

Please excuse my optimism here, but emulators with MP support will
bring in a lot more people, the scarce hardware failed to bring in so
far.

Of course we are hobbyists, we're doing it for the fun of it. If you
want to learn more, please head over to:

https://epic-linux.org/

Cheers,
Frank



  parent reply	other threads:[~2026-07-23 12:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22 14:33 Greg Kroah-Hartman
2026-07-22 15:01 ` Brett A C Sheffield
2026-07-22 17:25 ` Frank Scheiner
2026-07-23  7:46   ` Greg Kroah-Hartman
2026-07-23  9:33     ` Tomáš Glozar
2026-07-23 12:21     ` Frank Scheiner [this message]
2026-07-24  6:17       ` Greg Kroah-Hartman
2026-07-24  9:25         ` Frank Scheiner
2026-07-22 18:30 ` Florian Fainelli
2026-07-22 20:11 ` Pavel Machek
2026-07-23  8:37 ` Shung-Hsi Yu
2026-07-23 10:17   ` Greg Kroah-Hartman
2026-07-24  6:18     ` Greg Kroah-Hartman
2026-07-24  6:52       ` Shung-Hsi Yu
2026-07-24  7:58         ` Shung-Hsi Yu
2026-07-23 11:28 ` Miguel Ojeda
2026-07-23 14:30 ` Wentao Guan
2026-07-23 15:54 ` Mark Brown
2026-07-24  9:26 ` Peter Schneider
2026-07-23  9:53 Tomas Glozar

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=1e9a0b1d-cc4f-4ac7-ac53-478580181c99@web.de \
    --to=frank.scheiner@web.de \
    --cc=achill@achill.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=cc@epic-linux.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hargar@microsoft.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@nabladev.com \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=sr@sladewatkins.com \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@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

all inboxes | Powered by JetHome®