On 15.11.2007 01:32, Jordan Crouse wrote:
I think printk is always available - any previous printk pain has been
(finally) resolved.
That warrants updating the design doc as well as another question: Is
printk available before early serial port setup? AFAICS it is not. We
have to
On 15/11/07 11:45 +0100, Carl-Daniel Hailfinger wrote:
On 15.11.2007 01:32, Jordan Crouse wrote:
I think printk is always available - any previous printk pain has been
(finally) resolved.
That warrants updating the design doc as well as another question: Is
printk available before
On 15.11.2007 17:20, Jordan Crouse wrote:
On 15/11/07 11:45 +0100, Carl-Daniel Hailfinger wrote:
On 15.11.2007 01:32, Jordan Crouse wrote:
I think printk is always available - any previous printk pain has been
(finally) resolved.
That warrants updating the design doc as
I think printk is always available - any previous printk pain has been
(finally) resolved.
On 15/11/07 01:25 +0100, Carl-Daniel Hailfinger wrote:
Fix code comments/documentation related to printk.
Sprinkle TODOs all over obviously wrong comments.
Document possible execution flow alternatives
