On 1/30/07, Mitch Bradley [EMAIL PROTECTED] wrote:
We shall take reasonable precautions to reduce the probability of
reflash-brickage to an acceptable level. A level of 0 is neither
achievable nor cost-effective.
Will the production boards have pads or a header that can be used
by an SPI
Tim Flavin wrote:
On 1/30/07, Mitch Bradley [EMAIL PROTECTED] wrote:
We shall take reasonable precautions to reduce the probability of
reflash-brickage to an acceptable level. A level of 0 is neither
achievable nor cost-effective.
Will the production boards have pads or a header that can
OLPC want to look at this type of brick insurance?
Yes, I've just been waiting until we have a clearer idea of the final
size of OFW before asking Mitch about it.
Agreed.
For now it won't help much because the EC code, which is a single point
of failure, has to be upgraded so often due
Gabor Dolla wrote:
Will this insurance thing defend against failed bios upgrade only ?
Or will this thing help when Linux wouldn't boot or X or sugar can not
start after software update ?
Failed BIOS upgrade only, but we're looking at a different mechanism to
similarly deal with userspace.
--
On 1/30/07, Mitch Bradley [EMAIL PROTECTED] wrote:
For now it won't help much because the EC code, which is a single point
of failure, has to be upgraded so often due to changes from Quanta.
yes, this is another reason I did not bring it up earlier :-)
When that settles down, we should do
ron minnich wrote:
flashus interruptus, due to things like power dropping, breaker
tripping, or, literally, people tripping on a power cable :-) Yes,
there's a battery, but ... maybe their battery has not charged for
some reason.
I asked early on that we skip flashing in a low-battery
On 1/30/07, Ivan Krstić [EMAIL PROTECTED] wrote:
ron minnich wrote:
flashus interruptus, due to things like power dropping, breaker
tripping, or, literally, people tripping on a power cable :-) Yes,
there's a battery, but ... maybe their battery has not charged for
some reason.
I asked
ron minnich wrote:
On 1/30/07, Ivan Krstić [EMAIL PROTECTED] wrote:
ron minnich wrote:
flashus interruptus, due to things like power dropping, breaker
tripping, or, literally, people tripping on a power cable :-) Yes,
there's a battery, but ... maybe their battery has not charged for
some
On Tue, 2007-01-30 at 09:48 -0700, ron minnich wrote:
On 1/30/07, Mitch Bradley [EMAIL PROTECTED] wrote:
For now it won't help much because the EC code, which is a single point
of failure, has to be upgraded so often due to changes from Quanta.
yes, this is another reason I did not bring
LinuxBIOS has a brick insurance policy which we have made heavy use
of in the supercomputing community. The operation is simple: two
copies of the BIOS, plus a set of CMOS variables and associated code
which allows for selection of a known-good, fallback BIOS, in the case
of a failed reflash
ron minnich wrote:
Question is, does OLPC want to look at this type of brick insurance?
Yes, I've just been waiting until we have a clearer idea of the final
size of OFW before asking Mitch about it.
--
Ivan Krstić [EMAIL PROTECTED] | GPG: 0x147C722D
Ivan Krstić wrote:
ron minnich wrote:
Question is, does OLPC want to look at this type of brick insurance?
Yes, I've just been waiting until we have a clearer idea of the final
size of OFW before asking Mitch about it.
Agreed.
For now it won't help much because the EC code
12 matches
Mail list logo
