From: Stefan Wahren <wahrenst@gmx.net>
To: Jai Luthra <jai.luthra@ideasonboard.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Peter Robinson <pbrobinson@gmail.com>,
"Ivan T. Ivanov" <iivanov@suse.de>
Cc: linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
kernel-list@raspberrypi.com,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH 4/5] media: staging: Drop bcm2835-camera driver
Date: Mon, 8 Sep 2025 14:00:40 +0200 [thread overview]
Message-ID: <0b9fa19b-195b-4bee-8f51-6b00ff2fcb6a@gmx.net> (raw)
In-Reply-To: <175690685574.8095.13306600513284108529@freya>
Hi Jai,
[add Peter & Ivan to Cc]
Am 03.09.25 um 15:40 schrieb Jai Luthra:
> Hi Stefan,
>
> Quoting Stefan Wahren (2025-08-28 00:48:22)
>> Hi Jai,
>>
>> Am 27.08.25 um 08:24 schrieb Jai Luthra:
>>> The bcm2835-camera driver is replaced by the V4L2 bcm2835-unicam driver
>>> that is already upstream. So drop it from staging.
>> AFAIK the old Raspberry Pi Camera V1 isn't supported by V4L2
>> bcm2835-unicam. Personally i'm fine with this, but this must be clear in
>> the commit message.Did you already talked to distributions like Redhat &
>> OpenSuSE about this step?
> As Dave mentioned, the OV5647 should work with V4L2. I don't have a sensor
> with me, but I can order one and try to get it working with the upstream
> kernel separate from this series.
>
> I did test the V2 camera module (IMX219) with my series applied on top of
> upstream kernel, and capture worked fine with bcm2835-unicam, so I don't
> believe V1 camera module should be an issue.
I was in holidays the last days, so I better reply to this thread /
context even there is a V2 out yet.
Yes, this explains the technical part behind the motivation and I'm fine
with this to speed up unstaging.
But my point was "Are the users informed about this step?". So I hope
the extended Cc should do this job at least for popular distributions.
Best regards
next prev parent reply other threads:[~2025-09-08 13:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 6:24 [PATCH 0/5] staging: Destage VCHIQ interface and MMAL Jai Luthra
2025-08-27 6:24 ` [PATCH 1/5] include: linux: Destage VCHIQ interface headers Jai Luthra
2025-08-27 12:40 ` Laurent Pinchart
2025-08-27 14:33 ` Umang Jain
2025-08-27 19:05 ` Stefan Wahren
2025-08-28 2:17 ` Florian Fainelli
2025-08-28 6:19 ` Stefan Wahren
2025-09-03 13:48 ` Jai Luthra
2025-09-03 15:03 ` Stefan Wahren
2025-09-03 16:16 ` Florian Fainelli
2025-09-03 16:13 ` Florian Fainelli
2025-08-27 6:24 ` [PATCH 2/5] staging: vc04_services: Cleanup formatting TODO entry Jai Luthra
2025-08-27 12:45 ` Laurent Pinchart
2025-08-27 18:55 ` Stefan Wahren
2025-08-27 6:24 ` [PATCH 3/5] platform/broadcom: Destage VCHIQ interface Jai Luthra
2025-08-27 6:24 ` [PATCH 5/5] platform/broadcom: Destage VCHIQ MMAL driver Jai Luthra
[not found] ` <20250827-vchiq-destage-v1-4-5052a0d81c42@ideasonboard.com>
2025-08-27 12:48 ` [PATCH 4/5] media: staging: Drop bcm2835-camera driver Laurent Pinchart
2025-08-27 19:18 ` Stefan Wahren
2025-09-01 10:59 ` Dave Stevenson
2025-09-03 13:40 ` Jai Luthra
2025-09-08 12:00 ` Stefan Wahren [this message]
2025-09-09 11:57 ` Peter Robinson
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=0b9fa19b-195b-4bee-8f51-6b00ff2fcb6a@gmx.net \
--to=wahrenst@gmx.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=florian.fainelli@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=iivanov@suse.de \
--cc=jai.luthra@ideasonboard.com \
--cc=kernel-list@raspberrypi.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--cc=pbrobinson@gmail.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.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