From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 69F17E008D3; Fri, 7 Nov 2014 07:25:51 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mail.ahsoftware.de (h1446028.stratoserver.net [85.214.92.142]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 264F3E002A8 for ; Fri, 7 Nov 2014 07:25:46 -0800 (PST) Received: by mail.ahsoftware.de (Postfix, from userid 65534) id BF85A2C9C3F2; Fri, 7 Nov 2014 16:25:42 +0100 (CET) Received: from eiche.ahsoftware (p4FC3685E.dip0.t-ipconnect.de [79.195.104.94]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.ahsoftware.de (Postfix) with ESMTPSA id 3206E2C9C378 for ; Fri, 7 Nov 2014 16:25:42 +0100 (CET) Received: by eiche.ahsoftware (Postfix, from userid 65534) id DDA947FAA2; Fri, 7 Nov 2014 16:25:40 +0100 (CET) Received: from krabat.ahsoftware (unknown [IPv6:feee::5246:5dff:fe8b:95f8]) by eiche.ahsoftware (Postfix) with ESMTP id AA3C07F846; Fri, 7 Nov 2014 15:23:11 +0000 (UTC) Message-ID: <545CE3DE.4070902@ahsoftware.de> Date: Fri, 07 Nov 2014 16:23:10 +0100 From: Alexander Holler User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0 MIME-Version: 1.0 To: Otavio Salvador , =?UTF-8?B?RXJpYyBCw6luYXJk?= References: <1415353415-3805-1-git-send-email-holler@ahsoftware.de> <20141107150003.27c16356@e6520eb.localdomain> <20141107160443.765f9b19@e6520eb.localdomain> In-Reply-To: Cc: "meta-freescale@yoctoproject.org" , Jon Nettleton Subject: Re: [PATCH 0/1] arm: imx: fsl_otp: make fuses (OTP memory) read-only X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 15:25:51 -0000 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Am 07.11.2014 16:07, schrieb Otavio Salvador: > On Fri, Nov 7, 2014 at 1:04 PM, Eric B=C3=A9nard wrot= e: >> Hi Jon, >> >> Le Fri, 7 Nov 2014 15:31:15 +0100, >> Jon Nettleton a =C3=A9crit : >>> Fair enough. Can we all agree that it should default to disabled? >> >> On your product sure, on the evaluation board that's more questionable= =2E >> >> When an evaluation board's user reach this sysfs entries to do a write= >> to it I believe that's not a random choice but a user's choice. >> >> Maybe adding a otp_unlock entry to the sysfs before allowing write cou= ld >> secure more the feature when running on the evaluation boards so that >> the user can think twice before writing to the fuses. > > I like Eric's idea of the unlock sysfs entry for this purpose. Maybe I should mention that this extremly dangerous driver already was=20 posted for submission into the (production) kernel and nobody had a=20 problem with it's write functionality, just with some other stuff. And even if it's ok for FSL to promote this feature with their BSP, I=20 have absolutely no love for the way it was done. It now is likely part=20 of many production kernels, something never should have happened. And I still see absolutely no need to have some one time functionality=20 as part of the kernel, regardless how usefull it might be for some=20 developers. It's a waste of time and resources to include that write=20 functionality in something meant for the greater public. Especially=20 something that dangerous. Alexander Holler