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: <20160708185237.GC28589@dtor-ws>
Date:	Fri, 8 Jul 2016 11:52:37 -0700
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	"jeffrey.lin" <yajohn@...il.com>
Cc:	rydberg@...omail.se, groeck@...omium.org, robh@...nel.org,
	jeffrey.lin@...-ic.com, ealin.chiu@...-ic.com,
	jason.yeh@...-ic.com, KP.li@...-ic.com,
	linux-kernel@...r.kernel.org, linux-input@...r.kernel.org
Subject: Re: [v1.1,3/3] modify raydium firmware update rule

Hi Jeffrey,

On Fri, Jul 08, 2016 at 07:38:59AM -0700, jeffrey.lin wrote:
> Hi dmitry:
> >> modify raydium touch firmware update rule.
> 
> >Why? You need to explain why you are proposing a change (but as I
> >mentioned I see no reason for using custom file names for firmware. Have
> >userspace adjust name as needed by the driver.
> 
> >Thanks.
> 
> Just want to easy to do firmware update version control in the factory. If do this,
> factory do not easy update wrong version.

Just have your factory image rename firmware to canonical name before
initiating update. There is no need to encumber kernel code with this.

Thanks.

-- 
Dmitry

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ