[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F7D3B3159@ORSMSX110.amr.corp.intel.com>
Date: Fri, 17 Aug 2018 15:56:23 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Boris Brezillon <boris.brezillon@...tlin.com>,
Arnd Bergmann <arnd@...db.de>
CC: Bjorn Helgaas <bhelgaas@...gle.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"jchandra@...adcom.com" <jchandra@...adcom.com>,
Sinan Kaya <okaya@...eaurora.org>,
Tomasz Nowicki <tn@...ihalf.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
"Miquel Raynal" <miquel.raynal@...tlin.com>
Subject: RE: how to fix acpi_pci_root_remap_iospace?
>> - Some targets don't have any support for I/O space on their PCI bus and just
>> want to get things to compile by setting PCI_IOBASE to zero, this still opens
>> up some of the same problems as above, but doesn't really help otherwise.
That sounds horrible. Why would you want to have a driver that can't possibly
work on your platform compile cleanly? That's just asking for trouble. Sombody
might load that driver, and ... all the outb/outw/outl calls just corrupt low memory.
> Hm, maybe it's just easier to revert the patch since we got rid of
> patches adding COMPILE_TEST to drivers which were using read/writesl()
> (it turned out ia64 and sparc were not the only archs to not implement
> readsx/writesx() variants, and fixing them is not that easy).
That sounds like a better course of action.
-Tony
Powered by blists - more mailing lists