| To: | "John D. Davis" <johnd@Stanford.EDU> |
|---|---|
| Subject: | Re: Tracing the Console |
| From: | James Simmons <jsimmons@transvirtual.com> |
| Date: | Mon, 13 Aug 2001 16:18:36 -0700 (PDT) |
| Cc: | Debian MIPS list <debian-mips@lists.debian.org>, SGI MIPS list <linux-mips@oss.sgi.com> |
| In-reply-to: | <Pine.GSO.4.31.0108131556230.21357-100000@myth1.Stanford.EDU> |
| Sender: | owner-linux-mips@oss.sgi.com |
> I am currently trying to trace the console on and R4400 Indy. It seems > that everything goes through console.c using either con_write or > con_put_char. It would be great if I could communicate with someone that > has a thorough understanding of this code and its interaction with > newport_con.c. Okay. I could explain this code if you want. > I have put some prtink statements in and it seems that > newport_putcs is called several more times than it should. Don't do that. Printk calls newport_putcs so if you have printk in newport_putcs it will going into a endless loop. You could redirect the console to a different tty device, say a serial console. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Tracing the Console, John D. Davis |
|---|---|
| Next by Date: | RE: /usr/bin/file, Salisbury, Roger |
| Previous by Thread: | Tracing the Console, John D. Davis |
| Next by Thread: | help, Sathish Vasudevaiah |
| Indexes: | [Date] [Thread] [Top] [All Lists] |