From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 6 Dec 2001 18:52:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 6 Dec 2001 18:52:27 -0500 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:27923 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Thu, 6 Dec 2001 18:52:13 -0500 To: linux-kernel@vger.kernel.org From: "H. Peter Anvin" Subject: Re: Stupid PCI Bit-naming convention question Date: 6 Dec 2001 15:51:49 -0800 Organization: Transmeta Corporation, Santa Clara CA Message-ID: <9up0al$84m$1@cesium.transmeta.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Disclaimer: Not speaking for Transmeta in any way, shape, or form. Copyright: Copyright 2001 H. Peter Anvin - All Rights Reserved Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Followup to: By author: "Calin A. Culianu" In newsgroup: linux.dev.kernel > > In my attempts to investigate whether or not my m/b is afflicted by the > VIA KT266 hardware bug at device 1106:3099 register 0x95, bits 5,6,7, I > have a dumb question: Namely, how are bits numbered? > > I would assume that bits are numbered from smallest value to largest, > indexed at 0, so that bit 7 is the '128' component of a byte and bit 0 is > the '1' component.. correct? > Yes. -hpa -- at work, in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt