From: Sicelo <absicsz@gmail.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: "H. Nikolaus Schaller" <hns@goldelico.com>,
Robin Murphy <robin.murphy@arm.com>,
will@kernel.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
mchehab@kernel.org, andersson@kernel.org,
mathieu.poirier@linaro.org, Beleswar Padhi <b-padhi@ti.com>,
Andreas Kemnade <andreas@kemnade.info>,
iommu@lists.linux.dev,
arm-soc <linux-arm-kernel@lists.infradead.org>,
Linux-OMAP <linux-omap@vger.kernel.org>,
linux-media@vger.kernel.org, linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH 0/4] Fix omap-iommu bitrot
Date: Wed, 30 Oct 2024 15:28:13 +0200 [thread overview]
Message-ID: <ZyI0baBMPHVZ29-k@tp440p.steeds.sam> (raw)
In-Reply-To: <ZyIos2Gm1nf5rejI@8bytes.org>
Hi
On Wed, Oct 30, 2024 at 01:38:11PM +0100, Joerg Roedel wrote:
> On Wed, Oct 30, 2024 at 12:20:31PM +0100, H. Nikolaus Schaller wrote:
> > Why that? There was a discussion and everyone agreed to remove omap2,
> > but not omap3 and later.
>
> I raised this question to make sure the things we maintain are still
> relevant. Developer and maintainers time is limited and we should not
> spend it on stuff that nobody uses.
>
> > There are some devices besides the PandaBoard. I am aware of these where
> > this is relevant: Epson BT200, Samsung Galaxy Tab 2, Pyra Handheld
> > (in production) and we are currently thinking about producing a tiny series
> > of the DM3730 based GTA04A5 with spare parts.
> >
> > And of course we want to participate from the latest and greatest upstream changes.
>
> Okay, if there are still real users for latest mainline kernels on this
> hardware, then the effort is justified.
>
> Regards,
>
> Joerg
There is also the Nokia N900 phone (OMAP3) still seeing mainline
activity, as well as the Motorola Droid 4 (OMAP4), to name a few. I will
also be testing on the N900 around the weekend.
Thanks to everyone for the amazing work.
Sincerely
Sicelo
next prev parent reply other threads:[~2024-10-30 13:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 17:58 [PATCH 0/4] Fix omap-iommu bitrot Robin Murphy
2024-10-28 17:58 ` [PATCH 1/4] remoteproc/omap: Handle ARM dma_iommu_mapping Robin Murphy
2024-12-06 17:00 ` Mathieu Poirier
2024-10-28 17:58 ` [PATCH 2/4] media: omap3isp: " Robin Murphy
2025-02-15 6:57 ` Sicelo
2025-02-15 19:43 ` Laurent Pinchart
2025-02-16 10:27 ` Sakari Ailus
2024-10-28 17:58 ` [PATCH 3/4] iommu/omap: Add minimal fwnode support Robin Murphy
2024-10-28 17:58 ` [PATCH 4/4] iommu: Make bus_iommu_probe() static Robin Murphy
2024-10-28 20:46 ` [PATCH 0/4] Fix omap-iommu bitrot H. Nikolaus Schaller
2024-10-28 22:56 ` Mathieu Poirier
2024-10-29 17:07 ` Kevin Hilman
2024-10-30 4:55 ` Beleswar Prasad Padhi
2024-10-30 9:55 ` Joerg Roedel
2024-10-30 11:20 ` H. Nikolaus Schaller
2024-10-30 12:38 ` Joerg Roedel
2024-10-30 13:28 ` Sicelo [this message]
2024-10-30 23:49 ` Adam Ford
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=ZyI0baBMPHVZ29-k@tp440p.steeds.sam \
--to=absicsz@gmail.com \
--cc=andersson@kernel.org \
--cc=andreas@kemnade.info \
--cc=b-padhi@ti.com \
--cc=hns@goldelico.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mchehab@kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@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).