From: Steven Scholz <steven.scholz@imc-berlin.de>
To: Alex Zeffertt <ajz@cambridgebroadband.com>
Cc: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: printk in m8xx_cpm_dpalloc() ???
Date: Wed, 24 Apr 2002 12:29:14 +0200 [thread overview]
Message-ID: <3CC688FA.724B4B4B@imc-berlin.de> (raw)
In-Reply-To: 3CC68229.9020806@cambridgebroadband.com
Alex Zeffertt wrote:
> I had the same problem. printk() uses the CPM UART driver, and the initialisation of the CPM UART
> driver uses m8xx_cpm_dpalloc(). If you make m8xx_cpm_dpalloc() use printk() then you create a
> dependency loop. Don't do it.
Thanks for your fast reply.
But I am not sure if I understand the problem.
printk() is used long before the CPM UART driver is initialized (or am I
wrong).
So how is printk done before this driver is started, i.e. rs_8xx_init is
called?
And can I output some string to the console without using the CPM UART
driver?
Steven
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-04-24 10:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 9:45 printk in m8xx_cpm_dpalloc() ??? Steven Scholz
2002-04-24 10:00 ` Alex Zeffertt
2002-04-24 10:29 ` Steven Scholz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CC688FA.724B4B4B@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--cc=ajz@cambridgebroadband.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).