All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Herbert Poetzl <herbert@13thfloor.at>
Cc: Ingo Molnar <mingo@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: apic and 8254 wraparound ...
Date: Thu, 23 Dec 2004 23:37:17 +0000	[thread overview]
Message-ID: <1103845033.15193.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20041224001144.GA5192@mail.13thfloor.at>

On Gwe, 2004-12-24 at 00:11, Herbert Poetzl wrote:
> I don't know what kind of errors the buggy Mercury/
> Neptune chipset timers can cause, maybe they need some
> special handling, but from the available code, what 
> about something like this:

Data sheet is on the intel site, but essentially latching bugs on the
reads.


  reply	other threads:[~2004-12-24  0:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-24  0:11 apic and 8254 wraparound Herbert Poetzl
2004-12-23 23:37 ` Alan Cox [this message]
2004-12-24 20:00   ` Herbert Poetzl
2004-12-24 19:40     ` Alan Cox
2004-12-25 22:48       ` Herbert Poetzl
2004-12-26 18:08         ` Pavel Machek
2004-12-26 19:42           ` Herbert Poetzl

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=1103845033.15193.6.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=herbert@13thfloor.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.