From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:42442) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UCPqz-0001Yf-Ek for qemu-devel@nongnu.org; Mon, 04 Mar 2013 02:30:34 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UCPqy-0004Yg-7n for qemu-devel@nongnu.org; Mon, 04 Mar 2013 02:30:33 -0500 Received: from mx1.redhat.com ([209.132.183.28]:56458) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UCPqy-0004YY-0Z for qemu-devel@nongnu.org; Mon, 04 Mar 2013 02:30:32 -0500 Message-ID: <51344D93.6020004@redhat.com> Date: Mon, 04 Mar 2013 08:30:27 +0100 From: Gerd Hoffmann MIME-Version: 1.0 References: <11e3c93f4c64bda4ef46ec9de8dd8b4fa88b3ec5.1362290776.git.peter.crosthwaite@xilinx.com> <51344546.7080306@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC PATCH v1 2/4] bitops: Add UInt32StateInfo and helper functions List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Crosthwaite Cc: Blue Swirl , peter.maydell@linaro.org, qemu-devel@nongnu.org Hi, >>> + * @nw0: bits that cant be written with a 0 by the guest (sticky 1) >>> + * @nw1: bits that cant be written with a 1 by the guest (sticky 0) >> >> Why these? >> >> reset=0 + ro=1 equals nw1=1 >> reset=1 + ro=1 equals nw0=1 >> > > Some bits in my devices can only be written one-way they are either > "stuck on" once they are written, or only the hardware is allowed to > write the other way. Ah, ok. Makes sense. Can you make the description a bit more verbose to clarify this? cheers, Gerd