So the problem there was that traditionally, e820_reserve_resource()
expected to be the first one to populate any resources. That's changed,
and that's why it now needs to use "insert_resource()" rather than
So this didn't work _originally_ either?
Yeah, I don't like it. The quirk I was talking about was the one about
apparetly bogus MMIO address:
which you said came from another BAR. That isn't the HPET.
Yeah, no, that's horrid. I'm happy it's reverted.
And no, this doesn't work.
Yeah, no, we do want reserved entries from e820 to show up to at least
stop late _dynamic_ allocations from taking over.
Yes. And I do think this is a workable model.