From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 100ACE008D0; Sun, 9 Nov 2014 02:15:46 -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 55894E00832 for ; Sun, 9 Nov 2014 02:15:38 -0800 (PST) Received: by mail.ahsoftware.de (Postfix, from userid 65534) id A3D7A2C9C7E8; Sun, 9 Nov 2014 11:15:35 +0100 (CET) Received: from eiche.ahsoftware (p4FC37686.dip0.t-ipconnect.de [79.195.118.134]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.ahsoftware.de (Postfix) with ESMTPSA id 3E9C22C9C7E4 for ; Sun, 9 Nov 2014 11:15:35 +0100 (CET) Received: by eiche.ahsoftware (Postfix, from userid 65534) id 572118E4B8; Sun, 9 Nov 2014 11:15:34 +0100 (CET) Received: from krabat.ahsoftware (unknown [IPv6:feee::5246:5dff:fe8b:95f8]) by eiche.ahsoftware (Postfix) with ESMTP id 90E058E34E; Sun, 9 Nov 2014 10:14:40 +0000 (UTC) Message-ID: <545F3E8F.8040003@ahsoftware.de> Date: Sun, 09 Nov 2014 11:14:39 +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: Nikolay Dimitrov References: <1415353415-3805-1-git-send-email-holler@ahsoftware.de> <20141107150003.27c16356@e6520eb.localdomain> <20141107160443.765f9b19@e6520eb.localdomain> <545CE3DE.4070902@ahsoftware.de> <545CF576.5050403@ahsoftware.de> <545D79DC.8030701@mail.bg> <545E65D3.5080003@ahsoftware.de> In-Reply-To: <545E65D3.5080003@ahsoftware.de> Cc: "meta-freescale@yoctoproject.org" , Jon Nettleton , Otavio Salvador 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: Sun, 09 Nov 2014 10:15:46 -0000 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Am 08.11.2014 19:49, schrieb Alexander Holler: > I'm not confused, at least not in regard what you want to suggest. Of > course, I'm totally confused about the fact that almost nobody else > before has critized that write functionality of this driver, also I'm > already used to the fact that I'm unable to understand many things which > are happing in todays world. But nobody is perfect. ;) Just to make it more clear what this thread is about, here is a relevant sentence copied form the reference manual for the chip: "In order to avoid "rogue" code performing erroneous writes to OTP, a special unlocking sequence is required for writes to the fuse banks." Now guess why the HW was designed this way. And then look again at the driver which nullifies the careful implementation in the HW. It doesn't have to be the fault of the author, e.g. he just might have written it for internal use. The problem is that it went into kernels for public use and nobody has seen a problem. Might be because of missing knowledge about what the driver does at all or whatever. I don't know. Alexander Holler