Ummm, I don't think this is how request_region() works. A second call
to request_region() for an already-allocated region will silently
fail: it will not replace the old entry with the new one.
I think it would probably be a good idea for request_region() to
return a success/failure indication. I wonder why it doesn't, but I
wrote it a long time ago and don't remember what I was thinking at the
time. Maybe I did it that way to be compatible with its predecessor,
snarf_region().
I had thought that the meaning of "reserve=" was to tell the system to
avoid probing for *anything* at certain addresses... like, it was
saying that certain addresses specified devices unknown to Linux. But
I was just rewriting what was already there, not making it up from
scratch. I think if a reserved entry should be replaced as Paul
suggests, then there should be a specific test for this situation, so
that regions allocated by other drivers cannot be replaced this way.
-- Dave Hinds
dhinds@hyper.stanford.edu