From: "Simon White" <s_a_white@email.com>
To: "Steven Rostedt" <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, "Ingo Molnar" <mingo@elte.hu>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: Best Kernel Timers?
Date: Wed, 28 Sep 2005 06:55:18 -0500 [thread overview]
Message-ID: <20050928115518.DB7F3101D9@ws1-3.us4.outblaze.com> (raw)
> I'm not really sure what you have against patches? If you have to wait
> for this to be in the mainline, you are going to be disappointed.
Me, personally nothing, but trying to get every user of a catweasel or
hardsid card to patch there kernel is the problem.
For those that do wish to patch there systems I have alternative
better realtime code. For those that don't I wanted something that
would approximately work as I had before.
As a note I've found it bad enough to try and get users to build the
normal drivers for there prebuilt kernels... with various requests
as to please put this in mainline (although not ready for that) so
it comes pre-built and installed for there system.
If there are no currently in mainline even approaching suitable clocks
(why I asked) then I'll resort to some custom busy waiting mechanism :(.
Thankyou for helping.
Simon
--
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm
next reply other threads:[~2005-09-28 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 11:55 Simon White [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-28 10:08 Simon White
2005-09-28 11:17 ` Steven Rostedt
2005-09-28 17:34 ` Christoph Lameter
2005-09-28 9:36 Simon White
2005-09-28 9:53 ` Steven Rostedt
2005-09-28 17:33 ` Christoph Lameter
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=20050928115518.DB7F3101D9@ws1-3.us4.outblaze.com \
--to=s_a_white@email.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®