From: James Cameron <quozl@laptop.org>
To: Linus Walleij <linusw@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>, 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>,
linux-geode@lists.infradead.org,
Andres Salomon <dilinger@queued.net>,
Lubomir Rintel <lkundrak@v3.sk>
Subject: Re: [PATCH] x86/olpc: select GPIOLIB_LEGACY
Date: Wed, 29 Apr 2026 13:07:44 +1000 [thread overview]
Message-ID: <afF2AEZ-iZibtbDT@laptop.org> (raw)
In-Reply-To: <CAD++jLmQRMs=Hwh9=Kzu_HEAqJea2jPJ=R9eBFQQVTYpXCZ+gw@mail.gmail.com>
On Wed, Apr 29, 2026 at 12:34:53AM +0200, Linus Walleij wrote:
> So if there is interest full upstream support should not be
> hard to attain. But it requires some dedication, and I wonder
> if such exist.
I'm still here, keeping infrastructure running, still have hardware,
still receive telemetry showing children using our Fedora 18 build
(!), and still answering technical questions.
But we don't have funding for this kind of work. We now buy-in
laptops.
It would be wonderful if keeping dcon happens, but I have to be
realistic; whoever does it will need to be very dedicated to acquire
second-hand hardware and work through the various other things that
stop the modern kernel from running on it. I'll cheer you on if
that's you, and may even help out by mail, but I've other funded work,
so my time is limited.
Good luck!
next prev parent reply other threads:[~2026-04-29 3:07 UTC|newest]
Thread overview: 8+ 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 3:07 ` James Cameron [this message]
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=afF2AEZ-iZibtbDT@laptop.org \
--to=quozl@laptop.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=bp@alien8.de \
--cc=brgl@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=dilinger@queued.net \
--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=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