[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <731ead88-8dc9-4032-86f5-7a2dd5044b22@gmx.net>
Date: Wed, 27 Aug 2025 21:18:22 +0200
From: Stefan Wahren <wahrenst@....net>
To: Jai Luthra <jai.luthra@...asonboard.com>,
Florian Fainelli <florian.fainelli@...adcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@...adcom.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Ray Jui
<rjui@...adcom.com>, Scott Branden <sbranden@...adcom.com>
Cc: linux-rpi-kernel@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-staging@...ts.linux.dev,
linux-kernel@...r.kernel.org, kernel-list@...pberrypi.com,
Dave Stevenson <dave.stevenson@...pberrypi.com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>
Subject: Re: [PATCH 4/5] media: staging: Drop bcm2835-camera driver
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?
> This also simplifies destaging of VCHIQ MMAL, by reducing the users of
> the MMAL API (this driver is one of them).
AFAIU this drops the only one user of VCHIQ MMAL. So please explain, why
we still need this API and how this should be tested?
Best regards
Powered by blists - more mailing lists