From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
"Pan, Jacob jun" <jacob.jun.pan@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@linux.intel.com>,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [PATCH 3/9] x86/moorestown: add moorestown platform flags
Date: Fri, 26 Jun 2009 09:54:54 -0700 [thread overview]
Message-ID: <20090626095454.6f993a9c@jbarnes-g45> (raw)
In-Reply-To: <alpine.LFD.2.00.0906261827490.2767@localhost.localdomain>
On Fri, 26 Jun 2009 18:32:42 +0200 (CEST)
Thomas Gleixner <tglx@linutronix.de> wrote:
> On Fri, 26 Jun 2009, Ingo Molnar wrote:
> > [ Although it is beyond me why ABP was done - why wasnt HPET good
> > enough? HPET can do per CPU clockevents too and it's just as
> > off-chip (and hence fundamentally slow) as ABP. ]
>
> Welcome to the wonderful world of embedded systems. Just have a peek
> into arch/[arm/powerpc/mips] to see what's coming up to us with full
> force. I would not be surprised when we see an x86 system sharing the
> device driver for i2c or whatever with an ARM SoC in the foreseable
> future.
Ha, yeah I was just going to say "think embedded". ABP is a much
simpler spec and programming interface than HPET, and since we were
designing new custom silicon, it made sense to just do the simple
thing, rather than butchering an existing spec, then making a partial
HPET that looks like ABP anyway and forcing any future HPET updates to
conform to the new standard (very similar reasoning to the ACPI vs SFI
discussion btw). Hopefully the technologies we've come up with for
MRST will be flexible enough to be used in future platforms as well;
we'll see.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2009-06-26 16:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 0:14 Pan, Jacob jun
2009-06-26 7:19 ` Ingo Molnar
2009-06-26 9:13 ` Alan Cox
2009-06-26 9:38 ` Ingo Molnar
2009-06-26 10:16 ` Alan Cox
2009-06-26 11:04 ` Ingo Molnar
2009-06-26 11:56 ` Alan Cox
2009-06-26 12:22 ` Ingo Molnar
2009-06-26 12:33 ` Alan Cox
2009-06-26 12:51 ` Ingo Molnar
2009-06-26 13:34 ` Alan Cox
2009-06-26 14:44 ` Ingo Molnar
2009-06-26 14:29 ` Ingo Molnar
2009-06-26 16:32 ` Thomas Gleixner
2009-06-26 16:54 ` Jesse Barnes [this message]
2009-06-30 6:35 ` Pavel Machek
2009-07-01 17:25 ` Jesse Barnes
2009-07-01 20:48 ` Ingo Molnar
2009-06-26 15:00 ` Ingo Molnar
2009-06-26 16:51 ` Jesse Barnes
2009-06-26 18:45 ` Ingo Molnar
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=20090626095454.6f993a9c@jbarnes-g45 \
--to=jbarnes@virtuousgeek.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hpa@linux.intel.com \
--cc=jacob.jun.pan@intel.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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®