From: Dan Malek <dan@mvista.com>
To: Elan Feingold <elan@nxnetworks.com>
Cc: "Linuxppc-Embedded (E-mail)" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: kernel hangs at my_console_write
Date: Mon, 06 Aug 2001 14:09:44 -0400 [thread overview]
Message-ID: <3B6EDD68.55E51A8A@mvista.com> (raw)
In-Reply-To: NDBBLJLFCLLGDHJPGKGCKEBPEDAA.elan@nxnetworks.com
Elan Feingold wrote:
> .... In the version we were using, the numbers in
> embed_config() seemed to indicate that Hz were desired, but after grepping
> around, we saw that some parts of the kernel wanted Mhz.
If you take everything from the same kernel baseline, all of this will
match. At one point late in the 2.3.xx development, the values
were changed from MHz to Hz. People weren't patching/merging
correctly to get all of the right parts at the same time.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-08-06 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-06 16:18 kernel hangs at my_console_write Navin Boppuri
2001-08-06 16:36 ` Elan Feingold
2001-08-06 18:09 ` Dan Malek [this message]
2001-08-06 18:26 ` Michael Scott Shappe
-- strict thread matches above, loose matches on Subject: below --
2001-08-06 16:48 Navin Boppuri
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=3B6EDD68.55E51A8A@mvista.com \
--to=dan@mvista.com \
--cc=elan@nxnetworks.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).