From: Clemens Ladisch <clemens@ladisch.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: Andreas Mohr <andi@lisas.de>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Vojtech Pavlik <vojtech@suse.cz>, Jiri Kosina <jkosina@suse.cz>
Subject: Re: [PATCH 1/2] SOUND: kill gameport bits
Date: Thu, 28 Aug 2014 22:03:55 +0200 [thread overview]
Message-ID: <53FF8B2B.3050506@ladisch.de> (raw)
In-Reply-To: <s5hppfpt520.wl-tiwai@suse.de>
Takashi Iwai wrote:
> did anyone test the patch at all...?
Appears to work. The ymfpci gameport seems to be somewhat unreliable:
analog.c: 100 out of 17347 reads (0%) on pci0000:06:06.1/gameport0 failed
analog.c: 122 out of 1111 reads (10%) on pci0000:06:07.0/gameport0 failed
There is still some dependence of the CPU speed on the loop counts
calculated by gameport_time(), but it's not very high; the following are
for 3200 and 800 MHz, 5 times each:
gameport gameport7: EMU10K1 is pci0000:06:06.1/gameport0, io 0xe480, speed 651kHz
gameport gameport8: EMU10K1 is pci0000:06:06.1/gameport0, io 0xe480, speed 651kHz
gameport gameport9: EMU10K1 is pci0000:06:06.1/gameport0, io 0xe480, speed 651kHz
gameport gameport10: EMU10K1 is pci0000:06:06.1/gameport0, io 0xe480, speed 651kHz
gameport gameport11: EMU10K1 is pci0000:06:06.1/gameport0, io 0xe480, speed 651kHz
gameport gameport12: EMU10K1 is pci0000:06:06.1/gameport0, io 0xe480, speed 612kHz
gameport gameport13: EMU10K1 is pci0000:06:06.1/gameport0, io 0xe480, speed 612kHz
gameport gameport14: EMU10K1 is pci0000:06:06.1/gameport0, io 0xe480, speed 612kHz
gameport gameport15: EMU10K1 is pci0000:06:06.1/gameport0, io 0xe480, speed 611kHz
gameport gameport16: EMU10K1 is pci0000:06:06.1/gameport0, io 0xe480, speed 612kHz
Regards,
Clemens
next prev parent reply other threads:[~2014-08-28 20:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 2:46 [PATCH 1/2] SOUND: kill gameport bits Andreas Mohr
2014-08-20 5:18 ` Dmitry Torokhov
2014-08-20 5:50 ` Andreas Mohr
2014-08-20 6:09 ` Takashi Iwai
2014-08-20 6:31 ` Dmitry Torokhov
2014-08-20 7:05 ` Takashi Iwai
2014-08-20 12:15 ` Takashi Iwai
2014-08-20 14:49 ` Dmitry Torokhov
2014-08-21 7:16 ` Geert Uytterhoeven
2014-08-20 12:29 ` One Thousand Gnomes
2014-08-20 12:53 ` Geert Uytterhoeven
2014-08-21 11:29 ` Takashi Iwai
2014-08-24 5:07 ` Andreas Mohr
2014-08-25 7:13 ` Takashi Iwai
2014-08-28 20:03 ` Clemens Ladisch [this message]
2014-08-28 21:11 ` Vojtech Pavlik
2014-08-20 14:27 ` Andreas Mohr
2014-08-20 14:48 ` Dmitry Torokhov
2014-08-20 6:39 ` Vojtech Pavlik
2014-08-20 12:20 ` One Thousand Gnomes
-- strict thread matches above, loose matches on Subject: below --
2014-08-19 16:41 Dmitry Torokhov
2014-08-20 7:33 ` Clemens Ladisch
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=53FF8B2B.3050506@ladisch.de \
--to=clemens@ladisch.de \
--cc=andi@lisas.de \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=vojtech@suse.cz \
/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).