From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] too fast key repeat in pcpae 2cpu mode
Date: Tue, 8 Apr 2014 23:19:01 -0400 [thread overview]
Message-ID: <28b8f7361e089d97d4ff6cfb75318428@brasstown.quanstro.net> (raw)
In-Reply-To: <76b81861d5873750288c3d2bd2f8f30f@jitaku.localdomain>
On Tue Apr 8 23:12:24 EDT 2014, kokamoto@hera.eonet.ne.jp wrote:
> > so basically the timing loop is messed up. if you could run the amd64
> > kernel on this machine, this will not happen.
>
> Before I do this, I tried the 'sources' pc kernel for 2 cpu.
> It recognizes 2 cpus and has no problem.
you can try using the pc i8253.c for pcpae, and see if that solves
the issue.
- erik
next prev parent reply other threads:[~2014-04-09 3:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-05 8:25 kokamoto
2014-04-05 15:09 ` erik quanstrom
2014-04-06 2:53 ` kokamoto
2014-04-06 2:41 ` erik quanstrom
2014-04-06 6:17 ` erik quanstrom
2014-04-09 5:34 ` kokamoto
2014-04-09 3:00 ` erik quanstrom
2014-04-09 5:48 ` kokamoto
2014-04-09 3:19 ` erik quanstrom [this message]
2014-04-09 7:41 ` kokamoto
2014-04-09 5:23 ` erik quanstrom
2014-04-10 8:25 ` kokamoto
2014-04-09 5:53 ` kokamoto
2014-04-10 2:22 ` Bruce Ellis
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=28b8f7361e089d97d4ff6cfb75318428@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).