From: Dmitry Baryshkov <dbaryshkov@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Andreas Kemnade <andreas@kemnade.info>,
Linus Walleij <linus.walleij@linaro.org>,
paul.eggleton@linux.intel.com,
Andrea Adami <andrea.adami@gmail.com>,
Guenter Roeck <linux@roeck-us.net>,
Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
"open list:ARM TCG CPUs" <qemu-arm@nongnu.org>,
Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Janusz Krzysztofik <jmkrzyszt@gmail.com>,
Tony Lindgren <tony@atomide.com>,
Linux-OMAP <linux-omap@vger.kernel.org>,
Daniel Mack <daniel@zonque.org>,
Robert Jarzmik <robert.jarzmik@free.fr>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Stefan Lehner <stefan-lehner@aon.at>
Subject: Re: possible deprecation and removal of some old QEMU Arm machine types (pxa2xx, omap, sa1110)
Date: Thu, 15 Feb 2024 10:52:50 +0200 [thread overview]
Message-ID: <CALT56yPLobsL699K9+DDMBWwi7-iLzaYwuDwV7NmecaTY7Z6Tw@mail.gmail.com> (raw)
In-Reply-To: <7c8a5c5b-a94a-4b87-a043-f1e398b55872@app.fastmail.com>
On Thu, 15 Feb 2024 at 10:45, Arnd Bergmann <arnd@arndb.de> wrote:
>
> On Thu, Feb 15, 2024, at 09:31, Andreas Kemnade wrote:
> > On Wed, 14 Feb 2024 23:42:58 +0100
> > "Arnd Bergmann" <arnd@arndb.de> wrote:
> >> On Wed, Feb 14, 2024, at 13:26, Dmitry Baryshkov wrote:
> >> > On Tue, 13 Feb 2024 at 23:22, Linus Walleij <linus.walleij@linaro.org> wrote:
> >> >> On Tue, Feb 13, 2024 at 9:12 PM Arnd Bergmann <arnd@arndb.de> wrote:
> >> >> > On Tue, Feb 13, 2024, at 16:36, Guenter Roeck wrote:
> >> >> > > On Tue, Feb 13, 2024 at 03:14:21PM +0000, Peter Maydell wrote:
> >> >>
> >> >> Andrea Adami and Dmitry Eremin-Solenikov did the work in 2017 to
> >> >> modernize it a bit, and Russell helped out. I was under the impression
> >> >> that they only used real hardware though!
> >> >
> >> > I used both Qemu and actual hardware (having collie, poodle, tosa and
> >> > c860 that was easy).
> >> >
> >> > The biggest issue with Zaurus PDAs was that supporting interesting
> >> > parts of the platform (PCMCIA, companion chips) required almost
> >> > rebootstrapping of the corresponding drivers.
> >> > E.g. I had a separate driver for the LoCoMo chip which worked properly
> >> > with the DT systems.
> >> > PCMCIA was a huuuge trouble and it didn't play well at all. The driver
> >> > must be rewritten to use the component framework.
> >>
> >> If we want to actually go there, I think the best option for PCMCIA
> >> support is likely to replace the entire "soc_common" pcmcia driver
> >> with a simple drivers/pata/ storage driver and no support for
> >> other cards. There was a driver until commit 38943cbd25a2
> >> ("ata: remove palmld pata driver") that could serve as an
> >> template.
> >>
> > hmm, main usage for PCMCIA/CF in those devices was often something else,
> > not storage, at least on the IPAQ h2200. Wondering wether that road is
> > actually good. When I was mainly using those devices, I was not good in
> > mainlining things.
>
> Do we still support any non-storage CF devices that someone might
> actually use? Do you have a specific example in mind? These are
> the currently supported devices that I see:
The Bluetooth over the PCMCIA UART worked last time I checked it and
according to your grep it is still a valid user.
If we are talking about re-bootstrap of the PCMCIA subsystem, hostap
and orinoco come to my mind. We dropped those drivers a while ago, but
back at that time they were very useful. Also I had the out-of-tree
driver for Sharp 0.3 MP cameras using CF interface (yeah, sure, all of
those are out-of-tree nowadays).
>
> git grep -B4 -w depends.*PCMCIA | grep "Kconfig-\(config\|menuconfig\)" | grep -v ^drivers/pcmcia
> drivers/ata/Kconfig-config PATA_PCMCIA
> drivers/bluetooth/Kconfig-config BT_HCIDTL1
> drivers/bluetooth/Kconfig-config BT_HCIBT3C
> drivers/bluetooth/Kconfig-config BT_HCIBLUECARD
> drivers/comedi/Kconfig-menuconfig COMEDI_PCMCIA_DRIVERS
> drivers/mmc/host/Kconfig-config MMC_SDRICOH_CS
> drivers/mtd/maps/Kconfig-config MTD_PCMCIA
> drivers/mtd/maps/Kconfig-config MTD_PCMCIA_ANONYMOUS
> drivers/net/arcnet/Kconfig-menuconfig ARCNET
> drivers/net/arcnet/Kconfig-config ARCNET_COM20020_CS
> drivers/net/can/sja1000/Kconfig-config CAN_EMS_PCMCIA
> drivers/net/can/sja1000/Kconfig-config CAN_PEAK_PCMCIA
> drivers/net/can/softing/Kconfig-config CAN_SOFTING_CS
> drivers/net/ethernet/3com/Kconfig-config NET_VENDOR_3COM
> drivers/net/ethernet/3com/Kconfig-config PCMCIA_3C574
> drivers/net/ethernet/3com/Kconfig-config PCMCIA_3C589
> drivers/net/ethernet/8390/Kconfig-config PCMCIA_AXNET
> drivers/net/ethernet/8390/Kconfig-config APNE
> drivers/net/ethernet/8390/Kconfig-config PCMCIA_PCNET
> drivers/net/ethernet/amd/Kconfig-config PCMCIA_NMCLAN
> drivers/net/ethernet/fujitsu/Kconfig-config NET_VENDOR_FUJITSU
> drivers/net/ethernet/fujitsu/Kconfig-config PCMCIA_FMVJ18X
> drivers/net/ethernet/smsc/Kconfig-config PCMCIA_SMC91C92
> drivers/net/ethernet/xircom/Kconfig-config NET_VENDOR_XIRCOM
> drivers/net/ethernet/xircom/Kconfig-config PCMCIA_XIRC2PS
> drivers/parport/Kconfig-config PARPORT_PC_PCMCIA
> drivers/scsi/pcmcia/Kconfig-menuconfig SCSI_LOWLEVEL_PCMCIA
> drivers/ssb/Kconfig-config SSB_PCMCIAHOST_POSSIBLE
> drivers/tty/Kconfig-config IPWIRELESS
> drivers/tty/serial/8250/Kconfig-config SERIAL_8250_CS
> drivers/usb/host/Kconfig-config USB_SL811_CS
> sound/pcmcia/Kconfig-menuconfig SND_PCMCIA
>
> Arnd
--
With best wishes
Dmitry
next prev parent reply other threads:[~2024-02-15 8:53 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 12:32 possible deprecation and removal of some old QEMU Arm machine types (pxa2xx, omap, sa1110) Peter Maydell
2024-02-12 14:03 ` Guenter Roeck
2024-02-12 14:36 ` Guenter Roeck
2024-02-13 13:42 ` Marcin Juszkiewicz
2024-02-13 14:36 ` Guenter Roeck
2024-02-13 15:14 ` Peter Maydell
2024-02-13 15:36 ` Guenter Roeck
2024-02-13 20:11 ` Arnd Bergmann
2024-02-13 21:21 ` Linus Walleij
2024-02-14 10:14 ` Arnd Bergmann
2024-02-14 12:26 ` Dmitry Baryshkov
2024-02-14 13:39 ` Marcin Juszkiewicz
2024-02-14 22:15 ` Andrea Adami
2024-02-14 22:42 ` Arnd Bergmann
2024-02-15 8:31 ` Andreas Kemnade
2024-02-15 8:45 ` Arnd Bergmann
2024-02-15 8:52 ` Dmitry Baryshkov [this message]
2024-02-15 10:06 ` Marcin Juszkiewicz
2024-02-15 11:31 ` H. Nikolaus Schaller
2024-02-14 1:27 ` Aaro Koskinen
2024-02-14 5:53 ` Tony Lindgren
2024-02-14 14:57 ` Arnd Bergmann
2024-02-14 9:08 ` Daniel Mack
2024-03-08 15:41 ` Peter Maydell
2024-03-08 15:50 ` Guenter Roeck
2024-10-15 17:13 ` Peter Maydell
2024-10-15 17:30 ` Guenter Roeck
2024-10-15 17:35 ` Peter Maydell
2024-10-15 18:12 ` Guenter Roeck
2024-10-17 12:42 ` Peter Maydell
2024-10-17 14:12 ` Guenter Roeck
2024-10-17 14:29 ` Peter Maydell
2024-10-17 15:29 ` Guenter Roeck
2024-10-17 16:07 ` Peter Maydell
2024-10-17 17:53 ` Philippe Mathieu-Daudé
2024-02-14 7:37 ` Philippe Mathieu-Daudé
2024-02-14 7:49 ` Philippe Mathieu-Daudé
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=CALT56yPLobsL699K9+DDMBWwi7-iLzaYwuDwV7NmecaTY7Z6Tw@mail.gmail.com \
--to=dbaryshkov@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=andrea.adami@gmail.com \
--cc=andreas@kemnade.info \
--cc=arnd@arndb.de \
--cc=daniel@zonque.org \
--cc=haojian.zhuang@gmail.com \
--cc=jmkrzyszt@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=marcin.juszkiewicz@linaro.org \
--cc=paul.eggleton@linux.intel.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=robert.jarzmik@free.fr \
--cc=stefan-lehner@aon.at \
--cc=tony@atomide.com \
/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).