linux-kernel - Re: pci_fixup_video change blows up on sparc64

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20061019.022541.85409562.davem@davemloft.net>
Date:	Thu, 19 Oct 2006 02:25:41 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	alan@...hat.com
Cc:	eiichiro.oiwa.nm@...achi.com, jesse.barnes@...el.com,
	greg@...ah.com, linux-kernel@...r.kernel.org
Subject: Re: pci_fixup_video change blows up on sparc64

From: Alan Cox <alan@...hat.com>
Date: Thu, 19 Oct 2006 05:22:56 -0400

> On Thu, Oct 19, 2006 at 01:37:32AM -0700, David Miller wrote:
> > defined to do this kind of thing, for example with the
> > pcibios_bus_to_resource() interface, used by routines such as
> > drivers/pci/quirks.c:quirk_io_region().
> 
> pci_iomap() ?

Yep, but that interface needs a BAR.

The "0xc0000" usage here for the VGA rom stuff, and some of the quirk
examples, want something a little bit different.

I suppose we could create something that cooked up a fake PCI
device and a BAR, but that is a bit too much for what we're
trying to do here I'm afraid.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/