linux-kernel - Re: Missing MIPI IPU6 camera driver for Intel Alder Lake laptops

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <YvUbhx4HSxAAwIvv@pendragon.ideasonboard.com>
Date:   Thu, 11 Aug 2022 18:08:55 +0300
From:   Laurent Pinchart <laurent.pinchart@...asonboard.com>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     Paul Menzel <pmenzel@...gen.mpg.de>,
        Wang Yating <yating.wang@...el.com>,
        Christoph Jechlitschek <christoph.jechlitschek@...el.com>,
        Hao Yao <hao.yao@...el.com>, Andy Yeh <andy.yeh@...el.com>,
        Sakari Ailus <sakari.ailus@...ux.intel.com>,
        Bingbu Cao <bingbu.cao@...el.com>,
        Tianshu Qiu <tian.shu.qiu@...el.com>,
        linux-media@...r.kernel.org, Mark Pearson <markpearson@...ovo.com>,
        Dell.Client.Kernel@...l.com, linux-kernel@...r.kernel.org,
        Guenter Roeck <groeck@...gle.com>,
        Sergey Senozhatsky <senozhatsky@...omium.org>,
        Andy Whitcroft <apw@...onical.com>,
        Kai-Heng Feng <kai.heng.feng@...onical.com>,
        Christian Schaller <cschalle@...hat.com>,
        Wouter Bolsterlee <wouter@...sterl.ee>,
        Miguel Palhas <mpalhas@...il.com>, it+linux-media@...gen.mpg.de
Subject: Re: Missing MIPI IPU6 camera driver for Intel Alder Lake laptops

On Thu, Aug 11, 2022 at 05:02:40PM +0200, Greg KH wrote:
> On Thu, Aug 11, 2022 at 04:54:53PM +0300, Laurent Pinchart wrote:
> > For the time being, I agree with your recommendation to not buy these
> > devices if you care about camera support.
> 
> I second this, don't buy these devices if the vendor is not willing to
> get their drivers upstreamed properly.

"Not willing" may be a bit too harsh here. I wouldn't just blame Intel
for not upstreaming a driver if it turns out that the V4L2 API isn't a
good match and we have no proposal to provide an alternative.

This being said, I agree it's the vendor's responsibility to at least
engage with the upstream community to find a solution, and collaborate
on the implementation. I'm sure there have been way more private
discussions than I'm aware of, maybe now is the right time to extend
this to a wider audience and create a realistic plan on how to move
forward. You all know my e-mail address :-)

-- 
Regards,

Laurent Pinchart