From: David S. Miller Date: Wed, 9 Dec 2009 09:39:09 +0000 (-0800) Subject: sparc64: Fix overly strict range type matching for PCI devices. X-Git-Tag: v2.6.33-rc1~80^2~13 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=4230fa3b89ea1c413766bd411a8315a3d05aa6c7;p=pandora-kernel.git sparc64: Fix overly strict range type matching for PCI devices. When we are trying to see if a range property entry applies to a given address, we are overly strict about the type. We should only allow I/O ranges for I/O addresses, and only allow CONFIG space ranges for CONFIG space address. However for MEM ranges, they come in 32-bit and 64-bit flavors. And a lack of an exact match is OK if the range is 32-bit and the address is 64-bit. We can assign a 64-bit address properly into a 32-bit parent range just fine. So allow it. Reported-by: Patrick Finnegan Signed-off-by: David S. Miller --- Reading git-diff-tree failed