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  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]
Date:   Sun, 29 Jan 2017 18:10:01 +0100
From:   "Luis R. Rodriguez" <>
To:     Pali Rohár <>
Cc:     Kalle Valo <>,
        Arend Van Spriel <>,
        Ming Lei <>,
        "Luis R. Rodriguez" <>,
        Greg Kroah-Hartman <>,
        David Gnedt <>,
        Michal Kazior <>,
        Daniel Wagner <>,
        Tony Lindgren <>,
        Sebastian Reichel <>,
        Pavel Machek <>,
        Ivaylo Dimitrov <>,
        Aaro Koskinen <>,
        Grazvydas Ignotas <>,,,
Subject: Re: [PATCH 2/6] wl1251: Use request_firmware_prefer_user() for
 loading NVS calibration data

On Fri, Jan 27, 2017 at 02:11:46PM +0100, Pali Rohár wrote:
> So there are only two options:
> 1) Disallow it and so these users will have non-working wifi.
> 2) Allow those data to be used as fallback mechanism.

There is one "custom fallback" user in kernel which we recently
determined was a total mistake. A sysfs interface should have
been defined to enable custom LED settings. Can't a series of
sysfs interfaces be used to enable override ? So is that not a
third option worth consideration?


Powered by blists - more mailing lists