Fix to allow loading binary images in areas RedBoot does not believe to be RAM.

["Patrick Doyle" <wpd at delcomsys dot com>]

I don't think I sent this one one yet.  If I did, my apologies -- I still
haven't done that brain upgrade that I was looking for last week.

Anyway, I went to load a binary image into an area of memory that RedBoot
did not believe to be RAM, but I knew to be RAM.  RedBoot kindly put up a
prompt asking if I really knew what I was doing.  So I said "Yes".  Then
RedBoot promptly started the download, and then halted it when it tried to
write beyond the end of what it thought was RAM.  This annoyed me a little
bit (since I just told it I knew what I was doing), and the result is this
patch.  I figure if RedBoot has already asked the user if (s)he knows what
(s)he is doing, then RedBoot should remember that.

--wpd

Attachment: load.patch
Description: Binary data