From: Kevin Fry <kevin@carts.com>
To: linuxppc emb3dd3d list <linuxppc-embedded@lists.linuxppc.org>
Subject: HZ to MHZ, 2.4.2 kernel
Date: Fri, 17 Aug 2001 12:16:25 -0700 [thread overview]
Message-ID: <3B7D6D89.2524D838@carts.com> (raw)
I remember someone having a problem with the kernel using hz and
expecting MHZ or the other way around and it seems I'm running into this
problem right now. Are there any patches or anything that address this
issue with regards to the 8260 serial and also the time.c code? This is
in HHL 2.0, 2.4.2 kernel
Thanks!
Kevin Fry
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-08-17 19:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 19:16 Kevin Fry [this message]
2001-08-20 20:13 ` HZ to MHZ, 2.4.2 kernel / update on my progress Kevin Fry
2001-08-20 20:19 ` Dan Malek
2001-08-21 16:56 ` Elan Feingold
-- strict thread matches above, loose matches on Subject: below --
2001-08-17 19:25 HZ to MHZ, 2.4.2 kernel Petersen, David (MED, GEMS-IT)
2001-08-17 20:04 ` Dan Malek
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=3B7D6D89.2524D838@carts.com \
--to=kevin@carts.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).