Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1031226AbbDWW7y (ORCPT ); Thu, 23 Apr 2015 18:59:54 -0400 Received: from mail-wi0-f171.google.com ([209.85.212.171]:37408 "EHLO mail-wi0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753648AbbDWW7v (ORCPT ); Thu, 23 Apr 2015 18:59:51 -0400 MIME-Version: 1.0 In-Reply-To: References: <20150423213015.GA7888@google.com> Date: Thu, 23 Apr 2015 15:59:50 -0700 Message-ID: Subject: Re: git pull] drm for v4.1-rc1 From: Matthew Garrett To: Linus Torvalds Cc: Bjorn Helgaas , Dave Airlie , Daniel Vetter , Jani Nikula , DRI mailing list , Linux Kernel Mailing List , intel-gfx , "linux-pci@vger.kernel.org" , Matthew Garrett Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1083 Lines: 25 On Thu, Apr 23, 2015 at 3:47 PM, Linus Torvalds wrote: > I'm not sure why we want that IORESOURCE_ROM_SHADOW thing at all, but > yes, if what this is all about is the magic video ROM at 0xc0000, then It's used in the PCI layer to say "Read from 0xc0000 rather than the ROM BAR" and then ends up as a shorthand for "Was this the boot video device" in various places because we're bad at software. > There is no way to see that from the PCI device state, because as > mentioned, quite often the "ROM" is entirely fake, and is not just > some shadowed copy of a real underlying hardware ROM, but is > fundamentally just a RAM image decompressed from some other source and > then marked read-only. If only - nvidias used to rewrite their image at runtime. -- Matthew Garrett | matthew.garrett@coreos.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/