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] [day] [month] [year] [list]
Message-Id: <DEHVQ7YAUOG8.2TPWJBM6MTXLT@silabs.com>
Date: Tue, 25 Nov 2025 10:26:36 -0500
From: Damien Riégel <damien.riegel@...abs.com>
To: Damien Riégel <damien.riegel@...abs.com>,
        <greybus-dev@...ts.linaro.org>, "Johan Hovold" <johan@...nel.org>,
        "Alex
 Elder" <elder@...nel.org>,
        "Greg Kroah-Hartman"
 <gregkh@...uxfoundation.org>,
        <linux-kernel@...r.kernel.org>
Cc: "Silicon Labs Kernel Team" <linux-devel@...abs.com>
Subject: Re: [RFC PATCH v2 00/12] greybus: introduce CPC as transport layer

Hi Greg, Johan, and Alex,

On Fri Nov 14, 2025 at 10:07 AM EST, Damien Riégel wrote:
> Hi,
>
> This patchset brings support for Silicon Labs' CPC (Co-Processor
> Communication) protocol as transport layer for Greybus. This is
> introduced as a module that sits between Greybus and CPC Host Device
> Driver implementations, like SDIO or SPI, which are not part of this
> RFC. If there's no push back with this RFC, the final patchset ready for
> upstream will include the SDIO driver.

Gentle poke about this RFC, I would really appreciate any kind of
feedback on it.

If it's too big I can try to make it smaller to make the review easier.
As we're committing to Greybus to enable the coexistence of different
radio stacks in one chip, we want to make sure we're heading in the
right direction and that our work has a chance to get upstreamed.


Thank you!
-- 
Damien

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ