From: Benjamin LaHaise <bcrl@redhat.com>
To: george anzinger <george@mvista.com>
Cc: David Howells <dhowells@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Dual PPro timer stopping problem
Date: Thu, 3 Oct 2002 16:46:41 -0400 [thread overview]
Message-ID: <20021003164641.F16875@redhat.com> (raw)
In-Reply-To: <3D9C7E7E.7B2BFB52@mvista.com>; from george@mvista.com on Thu, Oct 03, 2002 at 10:29:34AM -0700
On Thu, Oct 03, 2002 at 10:29:34AM -0700, george anzinger wrote:
> The keyboard is, or at least depends on polling which is
> controled by a timer, thus, no timer, => no keyboard.
Eh? Sure, by a timer internal to the keyboard itself. At least x86
hardware has an interrupt wired to its keyboard controller that is used
to signal when a keystroke is available, and if you look into the driver,
you'd see that no timers are used at all.
-ben
next prev parent reply other threads:[~2002-10-03 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 14:03 Dual PPro timer stopping problem David Howells
2002-10-03 14:24 ` Alan Cox
2002-10-03 14:36 ` David Howells
2002-10-03 17:29 ` george anzinger
2002-10-03 20:46 ` Benjamin LaHaise [this message]
2002-10-03 21:19 ` george anzinger
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=20021003164641.F16875@redhat.com \
--to=bcrl@redhat.com \
--cc=dhowells@redhat.com \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.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).