From: Andres Salomon <dilinger@queued.net>
To: Arnd Bergmann <arnd@arndb.de>, Linus Walleij <linusw@kernel.org>
Cc: Arnd Bergmann <arnd@kernel.org>,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
Bartosz Golaszewski <brgl@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
James Cameron <quozl@us.netrek.org>,
James Cameron <quozl@laptop.org>,
linux-geode@lists.infradead.org, Lubomir Rintel <lkundrak@v3.sk>
Subject: Re: [PATCH] x86/olpc: select GPIOLIB_LEGACY
Date: Wed, 29 Apr 2026 17:18:08 -0400 [thread overview]
Message-ID: <fddba1c8-a95a-490f-962e-8505cb948672@queued.net> (raw)
In-Reply-To: <cc7fe7a5-9a60-4ab2-800b-4708abf42032@app.fastmail.com>
On 4/29/26 16:39, Arnd Bergmann wrote:
> On Wed, Apr 29, 2026, at 00:39, Andres Salomon wrote:
>> On 4/28/26 18:34, Linus Walleij wrote:
>>> On Tue, Apr 28, 2026 at 3:57 PM Arnd Bergmann <arnd@arndb.de> wrote:
[...]
>
>> I can't speak for other (former) OLPC folks, but I donated my remaining
>> OLPC hardware about seven years ago; so I no longer have any interest or
>> ability to support the hardware.
>
> I see you are still listed as paid support for AMD Geode in the
> MAINTAINERS file. Is that still the case, or did that end along
> with your involvement in XO-1?
>
No, my involvement with anything Geode and OLPC ended years ago. Feel
free to remove me from MAINTAINERS (unless someone has specific
questions about hardware, which I'm happy to answer).
> Are you aware of any Geode users that still update their kernels?
> I found that OpenWRT still publishes Geode builds (with XO-1
> disabled, but everything else built in) but no indication that
> anyone has actually run these after around 2017.
>
> Arnd
Personally I don't know anyone, but I feel like those Geode thin clients
are more likely to still be in use. A machine with 256MB of ram in 2026
is going to be an absolutely miserable laptop to use, but that's still
fine for a limited router or wifi access point. If you remove/disable
the Geode stuff, you probably won't hear complaints until the next major
OpenWRT release, though.
next prev parent reply other threads:[~2026-04-29 21:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 14:43 [PATCH] x86/olpc: select GPIOLIB_LEGACY Arnd Bergmann
2026-04-27 20:13 ` Linus Walleij
2026-04-28 13:56 ` Arnd Bergmann
2026-04-28 22:34 ` Linus Walleij
2026-04-28 22:39 ` Andres Salomon
2026-04-29 20:39 ` Arnd Bergmann
2026-04-29 21:18 ` Andres Salomon [this message]
2026-04-30 6:51 ` Arnd Bergmann
2026-04-29 3:07 ` James Cameron
2026-04-28 6:19 ` Takashi Iwai
2026-04-28 8:07 ` Bartosz Golaszewski
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=fddba1c8-a95a-490f-962e-8505cb948672@queued.net \
--to=dilinger@queued.net \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=bp@alien8.de \
--cc=brgl@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linusw@kernel.org \
--cc=linux-geode@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=mingo@redhat.com \
--cc=perex@perex.cz \
--cc=peterz@infradead.org \
--cc=quozl@laptop.org \
--cc=quozl@us.netrek.org \
--cc=tglx@kernel.org \
--cc=tiwai@suse.com \
--cc=x86@kernel.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