From: Geert Uytterhoeven <geert@linux-m68k.org> To: Thomas Bogendoerfer <tsbogend@alpha.franken.de> Cc: Matt Mackall <mpm@selenic.com>, Herbert Xu <herbert@gondor.apana.org.au>, Dan Williams <dan.j.williams@intel.com>, Vinod Koul <vkoul@kernel.org>, "David S. Miller" <davem@davemloft.net>, Miquel Raynal <miquel.raynal@bootlin.com>, Richard Weinberger <richard@nod.at>, Vignesh Raghavendra <vigneshr@ti.com>, Jakub Kicinski <kuba@kernel.org>, Alessandro Zummo <a.zummo@towertech.it>, Alexandre Belloni <alexandre.belloni@bootlin.com>, Mark Brown <broonie@kernel.org>, Wim Van Sebroeck <wim@linux-watchdog.org>, Guenter Roeck <linux@roeck-us.net>, Liam Girdwood <lgirdwood@gmail.com>, Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>, "open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Linux Crypto Mailing List <linux-crypto@vger.kernel.org>, dmaengine <dmaengine@vger.kernel.org>, linux-ide@vger.kernel.org, MTD Maling List <linux-mtd@lists.infradead.org>, netdev <netdev@vger.kernel.org>, linux-rtc@vger.kernel.org, linux-spi <linux-spi@vger.kernel.org>, Linux Watchdog Mailing List <linux-watchdog@vger.kernel.org>, ALSA Development Mailing List <alsa-devel@alsa-project.org>, Atsushi Nemoto <anemo@mba.ocn.ne.jp> Subject: Re: [PATCH 00/10] Remove support for TX49xx Date: Wed, 6 Jan 2021 21:41:24 +0100 [thread overview] Message-ID: <CAMuHMdV86BES7dmWr-7j1jbtoSy0bH1J0e5W41p8evagi0Nqcw@mail.gmail.com> (raw) In-Reply-To: <20210106184839.GA7773@alpha.franken.de> Hi Thomas, On Wed, Jan 6, 2021 at 7:49 PM Thomas Bogendoerfer <tsbogend@alpha.franken.de> wrote: > On Wed, Jan 06, 2021 at 09:37:11AM +0100, Geert Uytterhoeven wrote: > > On Tue, Jan 5, 2021 at 3:03 PM Thomas Bogendoerfer > > <tsbogend@alpha.franken.de> wrote: > > > I couldn't find any buyable product other than reference boards using > > > TX49xx CPUs. And since nobody showed interest in keeping support for > > > it, it's time to remove it. > > > > I have an RBTX4927 development board in my board farm, boot-test every > > bi-weekly renesas-drivers release on it, and fix kernel issues when they > > appear. > > > > Is that sufficient to keep it? > > for me it is. But now we probaly need some reverts then... Indeed. Fortunately not all of it, as some removals were TX4938-only. > I wonder whether you have seen my mail about the removal > > https://lore.kernel.org/linux-mips/20201207105627.GA15866@alpha.franken.de > > and my call for people owning MIPS machines > > https://lore.kernel.org/linux-mips/20200227144910.GA25011@alpha.franken.de/ Sorry, I'm not following the linux-mips list that closely, so I hadn't seen them. It's always a good idea to CC linux-kernel, and perhaps the few people who last touched the affected files. > Still "unclaimed" machines are > > IMG Pistachio SoC based boards (MACH_PISTACHIO( > Toshiba TX39 series based machines (MACH_TX39XX) > NEC VR4100 series based machines (MACH_VR41XX) > Netlogic XLR/XLS based systems (NLM_XLR_BOARD) > Netlogic XLP based systems (NLM_XLP_BOARD) > Sibyte BCM91120C-CRhine (SIBYTE_CRHINE) > Sibyte BCM91120x-Carmel (SIBYTE_CARMEL) > Sibyte BCM91125C-CRhone (SIBYTE_CRHONE) > Sibyte BCM91125E-Rhone (SIBYTE_RHONE) > Sibyte BCM91250C2-LittleSur (SIBYTE_LITTLESUR) > Sibyte BCM91250E-Sentosa (SIBYTE_SENTOSA) > > Is there something on this list you also regulary use ? No, I don't have anything from the list above. The RBTX4927 is basically my last MIPS-based system I do boot current kernels on. In active use, not for development: - Ubiquiti EdgeRouter-X (Ralink-based). Stored in my attic: - NetGear WNDR4300 (AtherOS-based), - MikroTik Routerboard 150 (ADMtek-based, no (longer?) supported upstream), - NEC DDB VRC-5476 (upstream support removed 15 years ago ;-) 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
WARNING: multiple messages have this Message-ID (diff)
From: Geert Uytterhoeven <geert@linux-m68k.org> To: Thomas Bogendoerfer <tsbogend@alpha.franken.de> Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>, Vignesh Raghavendra <vigneshr@ti.com>, Liam Girdwood <lgirdwood@gmail.com>, Atsushi Nemoto <anemo@mba.ocn.ne.jp>, ALSA Development Mailing List <alsa-devel@alsa-project.org>, Takashi Iwai <tiwai@suse.com>, linux-ide@vger.kernel.org, MTD Maling List <linux-mtd@lists.infradead.org>, Miquel Raynal <miquel.raynal@bootlin.com>, linux-spi <linux-spi@vger.kernel.org>, linux-rtc@vger.kernel.org, Wim Van Sebroeck <wim@linux-watchdog.org>, Herbert Xu <herbert@gondor.apana.org.au>, Richard Weinberger <richard@nod.at>, Jakub Kicinski <kuba@kernel.org>, Guenter Roeck <linux@roeck-us.net>, Linux Watchdog Mailing List <linux-watchdog@vger.kernel.org>, Mark Brown <broonie@kernel.org>, Matt Mackall <mpm@selenic.com>, Dan Williams <dan.j.williams@intel.com>, Jaroslav Kysela <perex@perex.cz>, Alessandro Zummo <a.zummo@towertech.it>, netdev <netdev@vger.kernel.org>, "open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Vinod Koul <vkoul@kernel.org>, Linux Crypto Mailing List <linux-crypto@vger.kernel.org>, dmaengine <dmaengine@vger.kernel.org>, "David S. Miller" <davem@davemloft.net> Subject: Re: [PATCH 00/10] Remove support for TX49xx Date: Wed, 6 Jan 2021 21:41:24 +0100 [thread overview] Message-ID: <CAMuHMdV86BES7dmWr-7j1jbtoSy0bH1J0e5W41p8evagi0Nqcw@mail.gmail.com> (raw) In-Reply-To: <20210106184839.GA7773@alpha.franken.de> Hi Thomas, On Wed, Jan 6, 2021 at 7:49 PM Thomas Bogendoerfer <tsbogend@alpha.franken.de> wrote: > On Wed, Jan 06, 2021 at 09:37:11AM +0100, Geert Uytterhoeven wrote: > > On Tue, Jan 5, 2021 at 3:03 PM Thomas Bogendoerfer > > <tsbogend@alpha.franken.de> wrote: > > > I couldn't find any buyable product other than reference boards using > > > TX49xx CPUs. And since nobody showed interest in keeping support for > > > it, it's time to remove it. > > > > I have an RBTX4927 development board in my board farm, boot-test every > > bi-weekly renesas-drivers release on it, and fix kernel issues when they > > appear. > > > > Is that sufficient to keep it? > > for me it is. But now we probaly need some reverts then... Indeed. Fortunately not all of it, as some removals were TX4938-only. > I wonder whether you have seen my mail about the removal > > https://lore.kernel.org/linux-mips/20201207105627.GA15866@alpha.franken.de > > and my call for people owning MIPS machines > > https://lore.kernel.org/linux-mips/20200227144910.GA25011@alpha.franken.de/ Sorry, I'm not following the linux-mips list that closely, so I hadn't seen them. It's always a good idea to CC linux-kernel, and perhaps the few people who last touched the affected files. > Still "unclaimed" machines are > > IMG Pistachio SoC based boards (MACH_PISTACHIO( > Toshiba TX39 series based machines (MACH_TX39XX) > NEC VR4100 series based machines (MACH_VR41XX) > Netlogic XLR/XLS based systems (NLM_XLR_BOARD) > Netlogic XLP based systems (NLM_XLP_BOARD) > Sibyte BCM91120C-CRhine (SIBYTE_CRHINE) > Sibyte BCM91120x-Carmel (SIBYTE_CARMEL) > Sibyte BCM91125C-CRhone (SIBYTE_CRHONE) > Sibyte BCM91125E-Rhone (SIBYTE_RHONE) > Sibyte BCM91250C2-LittleSur (SIBYTE_LITTLESUR) > Sibyte BCM91250E-Sentosa (SIBYTE_SENTOSA) > > Is there something on this list you also regulary use ? No, I don't have anything from the list above. The RBTX4927 is basically my last MIPS-based system I do boot current kernels on. In active use, not for development: - Ubiquiti EdgeRouter-X (Ralink-based). Stored in my attic: - NetGear WNDR4300 (AtherOS-based), - MikroTik Routerboard 150 (ADMtek-based, no (longer?) supported upstream), - NEC DDB VRC-5476 (upstream support removed 15 years ago ;-) 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 ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2021-01-06 20:42 UTC|newest] Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-05 14:02 [PATCH 00/10] Remove support for TX49xx Thomas Bogendoerfer 2021-01-05 14:02 ` Thomas Bogendoerfer 2021-01-05 14:02 ` [PATCH 01/10] MIPS: TX49xx: Drop support Thomas Bogendoerfer 2021-01-05 14:02 ` Thomas Bogendoerfer 2021-01-05 14:59 ` Guenter Roeck 2021-01-05 14:59 ` Guenter Roeck 2021-01-05 14:02 ` [PATCH 02/10] net: tc35815: Drop support for TX49XX boards Thomas Bogendoerfer 2021-01-05 14:02 ` Thomas Bogendoerfer 2021-01-05 14:02 ` [PATCH 03/10] net: 8390: " Thomas Bogendoerfer 2021-01-05 14:02 ` Thomas Bogendoerfer 2021-01-05 14:02 ` [PATCH 04/10] spi: txx9: Remove driver Thomas Bogendoerfer 2021-01-05 14:02 ` Thomas Bogendoerfer 2021-01-05 14:02 ` [PATCH 05/10] dma: tx49 removal Thomas Bogendoerfer 2021-01-05 14:02 ` Thomas Bogendoerfer 2021-01-06 6:18 ` Vinod Koul 2021-01-06 6:18 ` Vinod Koul 2021-01-06 6:18 ` Vinod Koul 2021-01-06 19:10 ` Joe Perches 2021-01-06 19:10 ` Joe Perches 2021-01-06 19:10 ` Joe Perches 2021-01-07 16:40 ` Thomas Bogendoerfer 2021-01-07 16:40 ` Thomas Bogendoerfer 2021-01-07 16:40 ` Thomas Bogendoerfer 2021-01-08 8:27 ` Vinod Koul 2021-01-08 8:27 ` Vinod Koul 2021-01-08 8:27 ` Vinod Koul 2021-01-05 14:02 ` [PATCH 06/10] mtd: Remove drivers used by TX49xx Thomas Bogendoerfer 2021-01-05 14:02 ` Thomas Bogendoerfer 2021-01-05 14:06 ` Miquel Raynal 2021-01-05 14:06 ` Miquel Raynal 2021-01-05 14:06 ` Miquel Raynal 2021-01-05 14:02 ` [PATCH 07/10] char: hw_random: Remove tx4939 driver Thomas Bogendoerfer 2021-01-05 14:02 ` Thomas Bogendoerfer 2021-01-05 14:02 ` [PATCH 08/10] rtc: tx4939: Remove driver Thomas Bogendoerfer 2021-01-05 14:02 ` Thomas Bogendoerfer 2021-01-05 14:02 ` [PATCH 09/10] ide: tx4938ide: " Thomas Bogendoerfer 2021-01-05 14:02 ` Thomas Bogendoerfer 2021-01-05 14:02 ` [PATCH 10/10] ASoC: txx9: " Thomas Bogendoerfer 2021-01-05 14:02 ` Thomas Bogendoerfer 2021-01-05 16:08 ` (subset) [PATCH 00/10] Remove support for TX49xx Mark Brown 2021-01-05 16:08 ` Mark Brown 2021-01-06 8:37 ` Geert Uytterhoeven 2021-01-06 8:37 ` Geert Uytterhoeven 2021-01-06 16:03 ` Atsushi Nemoto 2021-01-06 16:03 ` Atsushi Nemoto 2021-01-06 18:48 ` Thomas Bogendoerfer 2021-01-06 18:48 ` Thomas Bogendoerfer 2021-01-06 20:41 ` Geert Uytterhoeven [this message] 2021-01-06 20:41 ` Geert Uytterhoeven 2021-01-07 1:17 ` Atsushi Nemoto 2021-01-07 1:17 ` Atsushi Nemoto 2021-01-07 8:04 ` Geert Uytterhoeven 2021-01-07 8:04 ` Geert Uytterhoeven 2021-01-07 8:04 ` Geert Uytterhoeven 2021-01-06 14:58 ` (subset) " Mark Brown 2021-01-06 14:58 ` Mark Brown 2021-01-12 23:33 ` Alexandre Belloni 2021-01-12 23:33 ` Alexandre Belloni
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=CAMuHMdV86BES7dmWr-7j1jbtoSy0bH1J0e5W41p8evagi0Nqcw@mail.gmail.com \ --to=geert@linux-m68k.org \ --cc=a.zummo@towertech.it \ --cc=alexandre.belloni@bootlin.com \ --cc=alsa-devel@alsa-project.org \ --cc=anemo@mba.ocn.ne.jp \ --cc=broonie@kernel.org \ --cc=dan.j.williams@intel.com \ --cc=davem@davemloft.net \ --cc=dmaengine@vger.kernel.org \ --cc=herbert@gondor.apana.org.au \ --cc=kuba@kernel.org \ --cc=lgirdwood@gmail.com \ --cc=linux-crypto@vger.kernel.org \ --cc=linux-ide@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mips@vger.kernel.org \ --cc=linux-mtd@lists.infradead.org \ --cc=linux-rtc@vger.kernel.org \ --cc=linux-spi@vger.kernel.org \ --cc=linux-watchdog@vger.kernel.org \ --cc=linux@roeck-us.net \ --cc=miquel.raynal@bootlin.com \ --cc=mpm@selenic.com \ --cc=netdev@vger.kernel.org \ --cc=perex@perex.cz \ --cc=richard@nod.at \ --cc=tiwai@suse.com \ --cc=tsbogend@alpha.franken.de \ --cc=vigneshr@ti.com \ --cc=vkoul@kernel.org \ --cc=wim@linux-watchdog.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.