summaryrefslogtreecommitdiffstats
path: root/cfg/x32.cfg
diff options
context:
space:
mode:
authorBruce Ashfield <bruce.ashfield@gmail.com>2020-04-08 23:19:56 -0400
committerBruce Ashfield <bruce.ashfield@gmail.com>2020-04-08 23:19:56 -0400
commit3f683e0777596f82fe27e8f7794d6b315b32d634 (patch)
tree4161c2c1b91ccb084fe43c9c3a8af6011acb3abe /cfg/x32.cfg
parent71db5735821c134acbfa1d547089ded68881e6de (diff)
downloadyocto-kernel-cache-master.tar.gz
yocto-kernel-cache-master.tar.bz2
yocto-kernel-cache-master.zip
mti_malta32: fix the pci resource conflictsHEADmaster
1/1 [ Author: Jack Tan Email: jack.tan@windriver.com Subject: mti_malta32: fix the pci resource conflicts Date: Wed, 10 Mar 2010 15:05:39 +0800 commit id 79896cf42f use request_resource() to replace the insert_resource() in pci_claim_resource(). But this does not fit the malta pci. With the new request_resource() kernel allocate a collision io resource for PCI ethernet. This disturb the PCI io space. One device use 0x1000 - 0x103f and the PCI ethernet use 0x1020 - 0x103f and this is cause the ethernet can't be accessed. This fix supplies a fixup function to fix the ioport collision. The old kernel log: pci 0000:00:0a.1: BAR 4: assigned [io 0x1040-0x104f] pci 0000:00:0a.1: BAR 4: set to [io 0x1040-0x104f] (PCI address [0x1040-0x104f] pci 0000:00:0a.2: BAR 4: assigned [io 0x1000-0x101f] pci 0000:00:0a.2: BAR 4: set to [io 0x1000-0x101f] (PCI address [0x1000-0x101f] pci 0000:00:0a.3: address space collision: [io 0x1000-0x103f] already in use pci 0000:00:0a.3: quirk: [io 0x1000-0x103f] claimed by PIIX4 ACPI pci 0000:00:0a.3: address space collision: [io 0x1100-0x110f] already in use pci 0000:00:0a.3: quirk: [io 0x1100-0x110f] claimed by PIIX4 SMB pci 0000:00:0a.3: BAR 7: [io 0x1000-0x103f] has bogus alignment pci 0000:00:0a.3: BAR 8: [io 0x1100-0x110f] has bogus alignment pci 0000:00:0b.0: BAR 0: assigned [io 0x1020-0x103f] pci 0000:00:0b.0: BAR 0: set to [io 0x1020-0x103f] (PCI address [0x1020-0x103f] pci 0000:00:0b.0: BAR 1: assigned [mem 0x10111000-0x1011101f] pci 0000:00:0b.0: BAR 1: set to [mem 0x10111000-0x1011101f] (PCI address [0x10111000-0x1011101f] pci 0000:00:0b.0: BAR 6: assigned [mem 0x10000000-0x100fffff pref] pci 0000:00:0c.0: BAR 0: assigned [mem 0x10110000-0x10110fff] pci 0000:00:0c.0: BAR 0: set to [mem 0x10110000-0x10110fff] (PCI address [0x10110000-0x10110fff] pci 0000:00:0c.0: BAR 1: assigned [mem 0x10100000-0x1010ffff] pci 0000:00:0c.0: BAR 1: set to [mem 0x10100000-0x1010ffff] (PCI address [0x10100000-0x1010ffff] ...... pcnet32.c:v1.35 21.Apr.2008 tsbogend@alpha.franken.de pcnet32: No access methods ...... ...... And a fixup to the original change: [ mips: malta PCI fixup, fix __init annotation warning Currently we see the following link warning: WARNING: vmlinux.o(.pci_fixup_final+0xefc): Section mismatch in reference from the variable __pci_fixup_malta_pcnet32_ioports_fixup164 to the function .init.text:malta_pcnet32_ioports_fixup() The variable __pci_fixup_malta_pcnet32_ioports_fixup164 references a function __init malta_pcnet32_ioports_fixup(). This is often seen when error handling in the init function uses functionality in the exit path. The fix is often to remove the __init annotation of malta_pcnet32_ioports_fixup() so it may be used outside an exit section. This is from the addition of "mti_malta32: fix the pci resource conflicts" (5c19c1c31c77 on v5.2/standard/mti-malta32) - which is a relatively old commit, but w/o a malta+PCnet32, I can't speak to whether this commit is still needed, or if the PCI resource overlap was solved another way. Hence here, we take the safe path and just remove the __init annotation. ] Signed-off-by: Jack Tan <jack.tan@windriver.com> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> ] Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Diffstat (limited to 'cfg/x32.cfg')
0 files changed, 0 insertions, 0 deletions