Content-Disposition: inline
Content-Transfer-Encoding: 7BIT
Content-Type: text/plain; charset=US-ASCII
MIME-Version: 1.0
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>
Date: Wed, 28 Sep 2005 06:55:18 -0500
Subject: Re: Best Kernel Timers?
Message-Id: <20050928115518.DB7F3101D9@ws1-3.us4.outblaze.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1253
Lines: 33


> 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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/