Jean-Denis Boyer wrote:
> I have just tested your patch on 8260 and it fixes the problem when printk is
> called ...
The use of printk is strictly a debug function. If it is necessary to see
it print out pretty, then use a different I/O path for the application or
dump out the log buffer separately. Serial ports don't guarantee any
transactional operation with multiple users, printk isn't any different
although it does the bad thing of blocking interrupts while it processes
the message.
Adding this patch adds lots of interrupt latency and I would recommend
against it. It appears there is a bug that should be fixed to ensure
the proper synchronization of the BDs, but not with such large scale
blocking of interrupts.
Thanks.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
