linux-kernel - Re: [PATCH v2] Serial: silabs si4455 serial driver

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: <9615854e-3012-f22d-07bf-901a5bc7a410@kernel.org>
Date:   Fri, 11 Dec 2020 06:33:14 +0100
From:   Jiri Slaby <jirislaby@...nel.org>
To:     József Horváth <info@...istro.hu>,
        'Greg Kroah-Hartman' <gregkh@...uxfoundation.org>
Cc:     'Rob Herring' <robh+dt@...nel.org>, linux-serial@...r.kernel.org,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] Serial: silabs si4455 serial driver

On 10. 12. 20, 20:46, József Horváth wrote:
>> Implement the basic serial driver first, and then we can talk about
>> "custom" configurations and the like, using the correct apis.
> 
> Without the SI4455_IOC_SEZC call, the driver can't configure the Si4455 and not working at all.
> The cofiguration for interface is provided by user for application.
> It contains the base frequency, channel spacing, modulation, and a lot of more stuff, and generated by Silicon Labs Wireless Development Suite.
> The generated configuration is in a non public(compressed, encrypted...who knows) format, so without this the driver can't provide configuration parameters to Si4455.

request_firmware() comes to my mind then.

thanks,
-- 
js
suse labs