public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Kemnade <andreas@kemnade.info>
To: Hans Verkuil <hverkuil@xs4all.nl>, linux-omap@vger.kernel.org
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH] media: staging: drop omap4iss
Date: Mon, 18 Nov 2024 20:00:25 +0100	[thread overview]
Message-ID: <20241118200025.3daab676@akair> (raw)
In-Reply-To: <815a789d-85a5-44a1-8b9c-429ac0101e3f@xs4all.nl>

Am Mon, 2 Sep 2024 10:42:31 +0200
schrieb Hans Verkuil <hverkuil@xs4all.nl>:

> The omap4 camera driver has seen no progress since forever, and
> now OMAP4 support has also been dropped from u-boot (1). So it is
> time to retire this driver.
> 

Argumenting with OMAP4 support in U-Boot is silly. That indicates that
there is no movement in keeping u-boot uptodate. Bootloader
development/updating is more risky especially if not done by the vendor,
good chances to brick something. And the bootloader might need
signing. So that argument is done nothing.

Better arguments would be to check if someone has something cooking and
feels not comfortable yet to climb Mount Upstream.

A good place to ask would be the omap platform
list: linux-omap@vger.kernel.org

I get still devicetrees for omap4 devices to review. So there is some
activity with omap4. If you look at postmarketOS you see also some
activity.

And also someone ported the driver to devicetree support:
https://github.com/iridia-ulb/meta-builderbot/blob/master/recipes-kernel/linux/linux-stable-4.16/0008-omap4iss-Fix-multiple-bugs-and-use-device-tree.patch

So the situation is not that simple. I am still evaluating it because I
myself have a device with omap4 and camera.

Regards,
Andreas

       reply	other threads:[~2024-11-18 19:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <815a789d-85a5-44a1-8b9c-429ac0101e3f@xs4all.nl>
2024-11-18 19:00 ` Andreas Kemnade [this message]
2024-11-19  7:02   ` [PATCH] media: staging: drop omap4iss Laurent Pinchart
2024-11-20  7:54     ` Andreas Kemnade
2024-11-20  8:39       ` Laurent Pinchart
2024-11-21 10:27         ` Andreas Kemnade
2024-11-21 10:52           ` H. Nikolaus Schaller
2024-11-21 11:12             ` H. Nikolaus Schaller
2024-11-21 11:40       ` Unknown
2024-11-21 16:21         ` Andreas Kemnade

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=20241118200025.3daab676@akair \
    --to=andreas@kemnade.info \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=sakari.ailus@linux.intel.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