Dear David VomLehn, In message <20090612003302.GA23715@xxxxxxxxxxxxxxxxxxxxxxx> you wrote: > > > However, the value and what's being proposed here and what I and others > > proposed--at least in the embedded kingdom--seems high and the features and > > implementation needn't be mutually exclusive. > > I agree. In this case, we have three different approaches to three different > problems (bootloader buffers, continuous state logging, and in-kernel capture > of logging). All are problems that need to be solved. Personally, I'd love > to have the continuous state logging, though I don't need the bootloader > buffer part. Question is: do we need three different solutions, or can we come up with one solution that covers all? Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@xxxxxxx "If it ain't broke, don't fix it." - Bert Lantz -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
