From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Gerhard Pircher <gerhard_pircher@gmx.net>,
Arnd Bergmann <arnd@arndb.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
Sparc kernel list <sparclinux@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>
Subject: Re: Old platforms: bring out your dead
Date: Wed, 13 Jan 2021 09:15:56 +0100 [thread overview]
Message-ID: <CAMuHMdU3s9hvenrRFibggT=hGDfauhh2hPcN7f3E0uG-iVG7iw@mail.gmail.com> (raw)
In-Reply-To: <CACRpkda4E2NwNw29J7x5gehtqn_m3M_Z2dHpc7xRgvb0b-p22A@mail.gmail.com>
Hi Linus,
On Wed, Jan 13, 2021 at 4:20 AM Linus Walleij <linus.walleij@linaro.org> wrote:
> On Tue, Jan 12, 2021 at 3:45 PM John Paul Adrian Glaubitz
> <glaubitz@physik.fu-berlin.de> wrote:
> That said there are a three things that people should really be doing if they
> want to keep their pet archs/subarchs around as good community
> members, and they are in essence to:
> 2. Migrate existing drivers to newly appeared and
> appropriate subsystems (I think there are some hacky heartbeat LED
> drivers down in arch/* for example) there is also the feature matrix
> core maintainers like and which appears if you type
> Documentation/features/list-arch.sh <archname>
> would be nice if you work on them if you can support them!
> Or at least take a look.
The choir is listening ;-)
For Amiga, that would require writing a real GPIO driver (modifying
gpio-mmio?) for the CIAs, and converting its users (amiflop, amijoy,
amimouse, parport_amiga, amiserial, and dmasound_paula) from direct CIA
register access to GPIO access (mctrl_gpio for amiserial)).
Note that the heartbeat LED is shared by heartbeat and audio.
An interim solution might be to just write a simple gpio driver for the
single CIA pin driving the heartbeat LED, allowing the user to set up
ledtrig-heartbeat.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2021-01-13 8:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAK8P3a2VW8T+yYUG1pn1yR-5eU4jJXe1+M_ot6DAvfr2KyXCzQ@mail.gmail.com>
2021-01-10 17:35 ` Old platforms: bring out your dead John Paul Adrian Glaubitz
2021-01-10 21:46 ` Sam Ravnborg
2021-01-11 8:05 ` John Paul Adrian Glaubitz
2021-01-11 14:55 ` chase rayfield
2021-01-12 0:26 ` Rob Landley
2021-01-12 0:50 ` chase rayfield
2021-01-12 14:37 ` John Paul Adrian Glaubitz
2021-01-11 18:09 ` Rob Landley
2021-01-11 15:04 ` Gerhard Pircher
2021-01-12 14:44 ` John Paul Adrian Glaubitz
2021-01-12 22:46 ` Linus Walleij
2021-01-13 8:09 ` Rob Landley
2021-01-13 8:21 ` Geert Uytterhoeven
2021-01-13 13:25 ` Rob Landley
2021-01-13 12:02 ` Andy Shevchenko
2021-01-13 8:15 ` Geert Uytterhoeven [this message]
2021-01-13 10:39 ` Arnd Bergmann
2021-01-14 3:54 ` New platforms: bring out your dead, was " Finn Thain
2021-01-14 9:41 ` John Paul Adrian Glaubitz
2021-01-14 9:48 ` Geert Uytterhoeven
2021-01-14 21:21 ` Arnd Bergmann
2021-01-14 22:54 ` Undesirable code, was Re: Old platforms etc Finn Thain
2021-01-14 23:09 ` Old platforms: bring out your dead Max Filippov
2021-01-15 8:31 ` Arnd Bergmann
2021-01-13 0:12 ` Old platforms never die, was " Finn Thain
2021-01-16 6:54 ` Rob Landley
2021-01-16 23:22 ` Finn Thain
2021-01-13 11:47 ` Andy Shevchenko
[not found] <CAFr9PX=BV1YFcO_GQWsW3XEo8nndjUwArzW5Fg1fnWzt8fiwGw@mail.gmail.com>
2021-01-11 9:15 ` John Paul Adrian Glaubitz
2021-01-11 9:20 ` Geert Uytterhoeven
2021-01-11 9:26 ` John Paul Adrian Glaubitz
2021-01-11 9:36 ` Geert Uytterhoeven
2021-01-11 9:50 ` Greg Ungerer
2021-01-11 9:42 ` Daniel Palmer
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='CAMuHMdU3s9hvenrRFibggT=hGDfauhh2hPcN7f3E0uG-iVG7iw@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=arnd@arndb.de \
--cc=gerhard_pircher@gmx.net \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-sh@vger.kernel.org \
--cc=sparclinux@vger.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;
as well as URLs for NNTP newsgroup(s).