[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1206490321.10573.10.camel@pasglop>
Date: Wed, 26 Mar 2008 11:12:01 +1100
From: Benjamin Herrenschmidt <benh@...abs.org>
To: Yinghai Lu <yhlu.kernel@...il.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Stefan Richter <stefanr@...6.in-berlin.de>,
Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>,
Ivan Kokshaysky <ink@...assic.park.msu.ru>,
Thomas Meyer <thomas@...3r.de>,
"Rafael J. Wysocki" <rjw@...k.pl>,
LKML <linux-kernel@...r.kernel.org>,
Adrian Bunk <bunk@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Natalie Protasevich <protasnb@...il.com>,
Myles Watson <mylesgw@...il.com>
Subject: Re: ohci1394 problem (MMIO broken) (was 2.6.25-rc6-git6: Reported
regressions from 2.6.24)
On Tue, 2008-03-25 at 17:03 -0700, Yinghai Lu wrote:
> > The good news is that I have done a patch to fix it, which has been
> > in -mm for about a month:
> iomap-fix-64-bits-resources-on-32-bits.patch
>
> does it support if size is 4G above, like 256G?
The patch just fixes pci_iomap to use resource_size_t, which fixes bugs
with MMIO addresses/size being cropped. It doesn't fix some limitations
we still, I think, have in the PCI code with 64 bits BARs on 32 bits
platforms (that we could, in fact, probably remove when resource_size_t
is 64 bits but we haven't done it yet, at least as far as I remember).
Ben.
--
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/
Powered by blists - more mailing lists