Re: blob release?

[Tim R. <Ti...@Ri...>]

- Unexplained occasional slow erases for AMD flash - Russ?
- occasional erases of the wrong partition!

once in a while when I flash a root image and a kernel image on a
shannon the blob partition is erased. I don't know why this happens. It
does not seem to happen nearly as often if I soft reboot between each
flash.

- strange flash error messages.

lock a block, write to it, you get errors. Unlock it, still error
messages. flash to it, still error messages. check it, it all worked.
The first write fails, the unlock and the second write succeed, but give
error messages.

- xmodem padding.

jffs2 uploads appear to be padded with 0x1a and so mess up jffs2 when it
tries to mark the rest of the upload block. Don't know if 0x1a can be
relied on. Perhaps we can search for 8 or more of the same byte at the
end of the last block and change them all to 0xff if found? then set the
length to this guess value and perhaps md5sums would work again? Perhaps
an upgraded protocol with length info should be implemented instead?

I'd like to see a faster boot unless keypress option (if not the
default)

Erik Mouw wrote:
> I usually release a new version when there are no knowm major bugs.
> Right now we have the following issues still open:
> - serial-typeahead bug fixed

fixed? or needs to be?

> - flash partitioning
> - parameter block support

-- 
Tim Riker - http://rikers.org/ - short SIGs! <g>
All I need to know I could have learned in Kindergarten
... if I'd just been paying attention.