Something is trying to register a 4GB resource. That sounds unlikely
(possible on a 64-bit PCI setup, but I think it's more likely to be some
overflow of 0 in "unsigned int").
In fact, this seems to be due to some driver bug. It looks like we have
window->size = 0xffffffffUL - window->phys + 1UL;
and in order for window->size to be 0x100000000, that means that
window->phys has to be 0. Which looks impossible, or at least like
ent->driver_data is neither DEV_CK804 nor DEV_MCP55. Very odd.
The warning:
is then just a result of the driver blindly continuing and trying to
"ioremap()" the resource even though it's bogus and the resource
allocation failed.
In other words, that driver init routine is really bad about error
handling. Carl-Daniel? David?
Linus
--