On Thu, 2007-12-13 at 14:00 +1100, Benjamin Herrenschmidt wrote: .../...
(oops, sent too fast) > So not only we can have a dangling BAR, but nothing prevent us to > actually go turn IO or MEM decoding on in case it wasn't already the > case on that device. And I was about to say before I clicked "send".. can't we do something like writing all ff's into the BAR at the same time as we clear res->start ? Isn't that supposed to pretty much disable decoding on that BAR ? Or not... Probably still better than leaving it to whatever dangling value it had no ? Also, maybe we should disable IO and MEM decoding by default on devices for which one resource of that type failed to allocate ? Ben. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
