From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262491AbTJXTJf (ORCPT ); Fri, 24 Oct 2003 15:09:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262497AbTJXTJe (ORCPT ); Fri, 24 Oct 2003 15:09:34 -0400 Received: from jurassic.park.msu.ru ([195.208.223.243]:12550 "EHLO jurassic.park.msu.ru") by vger.kernel.org with ESMTP id S262491AbTJXTJe (ORCPT ); Fri, 24 Oct 2003 15:09:34 -0400 Date: Fri, 24 Oct 2003 23:08:30 +0400 From: Ivan Kokshaysky To: Petr Vandrovec Cc: Linus Torvalds , Jeff Garzik , Jon Smirl , Eric Anholt , kronos@kronoz.cjb.net, Kernel Mailing List , linux-fbdev-devel@lists.sourceforge.net, dri-devel Subject: Re: [Dri-devel] Re: [Linux-fbdev-devel] DRM and pci_driver conversion Message-ID: <20031024230830.A2362@jurassic.park.msu.ru> References: <3F987E18.9080606@pobox.com> <20031024165718.GA4972@vana.vc.cvut.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20031024165718.GA4972@vana.vc.cvut.cz>; from vandrove@vc.cvut.cz on Fri, Oct 24, 2003 at 06:57:18PM +0200 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 24, 2003 at 06:57:18PM +0200, Petr Vandrovec wrote: > We need something more sophisticated. Matrox's hardware has bits > 31-16 readable/writable only if bit 0 is set to 1 (ROM enabled; you can > (obviously) set bits 31-16 & 0 in one write). When ROM is disabled, > bits 31-1 are always read as 0. Hmm, I believe it's not true at least for Mystique, Millennium II and G400. Otherwise we wouldn't be able to determine ROM size/alignment as we do probe with ROM disabled (probe.c, line 125): pci_write_config_dword(dev, rom, ~PCI_ROM_ADDRESS_ENABLE); pci_read_config_dword(dev, rom, &sz); Ivan.