![]() | ||||||||||
Messages in this thread |
On Sat, Mar 22, 2008 at 2:59 PM, H. Peter Anvin <hpa@kernel.org> wrote: > Linus Torvalds wrote: > > > > Ingo/Thomas - should ioremap*() perhaps take "resource_size_t" or a "u64" > > for the address (and then "__ioremap()" should probably take a PFN, not a > > physical address, and that one can remain just a "unsigned long"?) > > > > resource_size_t seems to make sense here. In the case when we have > 64-bit resources but no PAE support we should error our when the > resource is out of range rather than silently fail. > > > > Has anybody ever had a working 64-bit BAR on x86? Ivan? Maybe I'm missing > > something.. > > 64-bit BAR, certainly. 64-bit BAR with a value beyond 4 GB I would find > questionable at best... I suspect the answer is "no". > Opteron system with coprocessor on socket or HTX slot. will use 64bit BAR above 4g and size is more than 4g too. YH -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2008-03-22 23:31 [W:0.312 / U:0.050 seconds] ©2003-2008 Jasper Spaans | ||||||||||