Lu, Yinghai wrote:
> In the V2 you need to everyone happy
> 1. ROMCC: print
> 2. CAR: a. print
> b. printk
> c. print when ram is enabled already
> d. printk when ram is enabled already
> c/d are introduced for USBDebug direct, because dbg_info will be in RAM
> instead of cache..
> dbg_info will contain the BAR info that is needed for dbgp_bulk_write_x
Sorry, I still dont get it. Why can't romcc just use print_, CAR could
only use printk, and printk does the right thing, depending on whether
we have ram or not. that's two variations instead of 5.
Stefan
--
coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br.
Tel.: +49 761 7668825 • Fax: +49 761 7664613
Email: [EMAIL PROTECTED] • http://www.coresystems.de/
--
linuxbios mailing list
linuxbios@linuxbios.org
http://www.openbios.org/mailman/listinfo/linuxbios
