On Sat, 30 Aug 2008, Yinghai Lu wrote:
>
> in old kernel, after BAR3 request_filed, pci_assigned_unassigned
> should get update resource for that... but it could find that big
> space for it.
Exactly. So what happens is that it doesn't actually re-allocate it at
all. Not that it is necessarily even possible - it's quite possible that
that field is effectively locked some way and is read-only. Without
knowing the chipset details, we can only guess.
Linus
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
