From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: what about mach-shark?
Date: Tue, 27 Aug 2013 05:16:23 +0200 [thread overview]
Message-ID: <CACRpkdbrvVsSWFGo1QjDekZRc1svKaOsFpxqQJ0TKHtU2+XgKw@mail.gmail.com> (raw)
In-Reply-To: <20130826190646.GG6617@n2100.arm.linux.org.uk>
On Mon, Aug 26, 2013 at 9:06 PM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> On Mon, Aug 26, 2013 at 09:04:05PM +0200, Linus Walleij wrote:
>> On Mon, Jul 4, 2011 at 10:08 PM, Nicolas Pitre <nico@fluxnic.net> wrote:
>>
>> > Is this used?
>>
>> This still goes unanswered after two years.
>>
>> Alexander, are you compiling and booting recent kernels on the Shark?
>>
>> I recently had a dream to convert some platforms and eventually
>> all of the arch/arm machines to GENERIC_CLOCKEVENTS and
>
> You're not going to achieve that pipedream. Really. There are platforms
> still around which don't have enough timers to be able to do anything but
> periodic interrupts at a fixed rate - with nothing available as a clock
> source other than the kernel jiffy counter incremented by that periodic
> interrupt (which would create a circular dependency.)
Yes, I guess I will run into them... But I guess it doesn't hurt to
convert over the remaining machines that can actually do this
the right way.
Yours,
Linus Walleij
next prev parent reply other threads:[~2013-08-27 3:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 20:08 what about mach-shark? Nicolas Pitre
2011-07-04 22:05 ` Russell King - ARM Linux
2011-07-04 22:20 ` Nicolas Pitre
2011-07-04 22:24 ` Russell King - ARM Linux
2011-07-05 1:51 ` Nicolas Pitre
2013-08-26 19:04 ` Linus Walleij
2013-08-26 19:06 ` Russell King - ARM Linux
2013-08-27 3:16 ` Linus Walleij [this message]
2013-08-28 9:05 ` Alexander Schulz
2013-08-28 11:53 ` Linus Walleij
2013-09-02 6:16 ` Alexander Schulz
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=CACRpkdbrvVsSWFGo1QjDekZRc1svKaOsFpxqQJ0TKHtU2+XgKw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).