Re: [PATCH 1/2] SOUND: kill gameport bits

2014-08-28 Thread Vojtech Pavlik
On Thu, Aug 28, 2014 at 10:03:55PM +0200, Clemens Ladisch wrote: > 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 pci:06:06.1/gameport0 failed > analog.c: 12

Re: [PATCH 1/2] SOUND: kill gameport bits

2014-08-28 Thread Clemens Ladisch
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 pci:06:06.1/gameport0 failed analog.c: 122 out of reads (10%) on pci:06:07.0/gameport0 failed There is still s

Re: [PATCH 1/2] SOUND: kill gameport bits

2014-08-25 Thread Takashi Iwai
At Sun, 24 Aug 2014 07:07:16 +0200, Andreas Mohr wrote: > > On Thu, Aug 21, 2014 at 01:29:03PM +0200, Takashi Iwai wrote: > > I did a quick hack and it seems working on my box. > > The patch is below. > > Thanks!! > > Further comments below. > > I will be testing this ASAP. > > +static bool use

Re: [PATCH 1/2] SOUND: kill gameport bits

2014-08-23 Thread Andreas Mohr
On Thu, Aug 21, 2014 at 01:29:03PM +0200, Takashi Iwai wrote: > I did a quick hack and it seems working on my box. > The patch is below. Thanks!! Further comments below. I will be testing this ASAP. > +static bool use_ktime = true; > +module_param(use_ktime, bool, 0400); Towards final commit, s

Re: [PATCH 1/2] SOUND: kill gameport bits

2014-08-21 Thread Takashi Iwai
At Wed, 20 Aug 2014 09:05:58 +0200, Takashi Iwai wrote: > > > > > > Also, I'm left wondering why e.g. my Athlon XP system (a very popular > > > > > choice for longer times) would be affected by Cpufreq... > > > > > And there are no details on how exactly cpufreq is a problem or how > > > > > this

Re: [PATCH 1/2] SOUND: kill gameport bits

2014-08-21 Thread Geert Uytterhoeven
Hi Dmitry, On Wed, Aug 20, 2014 at 4:49 PM, Dmitry Torokhov wrote: > On Wed, Aug 20, 2014 at 02:15:30PM +0200, Takashi Iwai wrote: >> At Wed, 20 Aug 2014 09:05:58 +0200, >> Takashi Iwai wrote: >> > Well, it worked on my test machine a year ago or so. Maybe I had a >> > good luck. >> >> FYI, now

Re: [PATCH 1/2] SOUND: kill gameport bits

2014-08-20 Thread Dmitry Torokhov
On Wed, Aug 20, 2014 at 02:15:30PM +0200, Takashi Iwai wrote: > At Wed, 20 Aug 2014 09:05:58 +0200, > Takashi Iwai wrote: > > Well, it worked on my test machine a year ago or so. Maybe I had a > > good luck. > > FYI, now I tested again an analog joystick on SB Live put on a Dell > IvyBridge deskt

Re: [PATCH 1/2] SOUND: kill gameport bits

2014-08-20 Thread Dmitry Torokhov
On Wed, Aug 20, 2014 at 04:27:19PM +0200, Andreas Mohr wrote: > > > > Also, I'm left wondering why e.g. my Athlon XP system (a very popular > > > > choice for longer times) would be affected by Cpufreq... > > > > And there are no details on how exactly cpufreq is a problem or how this > > > > timin

Re: [PATCH 1/2] SOUND: kill gameport bits

2014-08-20 Thread Andreas Mohr
Hi, Sorry for having introduced a cut in discussion threading (broken formatting which caused In-Reply-To header loss). Will add several slightly disconnected items in single mail due to restricted environment. On Wed, Aug 20, 2014 at 08:09:49AM +0200, Takashi Iwai wrote: > At Tue, 19 Aug 2014 2

Re: [PATCH 1/2] SOUND: kill gameport bits

2014-08-20 Thread Geert Uytterhoeven
On Wed, Aug 20, 2014 at 2:29 PM, One Thousand Gnomes wrote: >> It's the gameport core code that is currently broken under some >> situation, right? If so, marking it as broken is the first step, and >> we don't need to touch else. We may fix it later, or we may not. If >> the thing isn't improv

Re: [PATCH 1/2] SOUND: kill gameport bits

2014-08-20 Thread One Thousand Gnomes
> It's the gameport core code that is currently broken under some > situation, right? If so, marking it as broken is the first step, and > we don't need to touch else. We may fix it later, or we may not. If > the thing isn't improved, then we can drop the whole stuff. It's only broken on x86 wi

Re: [PATCH 1/2] SOUND: kill gameport bits

2014-08-20 Thread One Thousand Gnomes
> It wouldn't be hard to fix: That code was developed when the timing > infrastructure in the kernel was non-existent, making use of it today > would make things a lot easier. You can also use pm_qos on most machines to stop PM messing it up. Ugly but works. Alan -- To unsubscribe from this list:

Re: [PATCH 1/2] SOUND: kill gameport bits

2014-08-20 Thread Takashi Iwai
At Wed, 20 Aug 2014 09:05:58 +0200, Takashi Iwai wrote: > Well, it worked on my test machine a year ago or so. Maybe I had a > good luck. FYI, now I tested again an analog joystick on SB Live put on a Dell IvyBridge desktop with 3.17-rc1 x86-64 kernel, and it worked fine as is. So it's not that

Re: [PATCH 1/2] SOUND: kill gameport bits

2014-08-20 Thread Clemens Ladisch
Dmitry Torokhov wrote: > Gameport support hasn't been working well ever since cpufreq became > mainstream Back in the gameport-mainstream days, we did not have a usable high- resolution timer API. But why can't we use something like getrawmonotonic() now? (Yes, I'm volunteering ...) > and it be

Re: [PATCH 1/2] SOUND: kill gameport bits

2014-08-20 Thread Takashi Iwai
At Tue, 19 Aug 2014 23:31:30 -0700, Dmitry Torokhov wrote: > > On Wed, Aug 20, 2014 at 08:09:49AM +0200, Takashi Iwai wrote: > > At Tue, 19 Aug 2014 22:18:15 -0700, > > Dmitry Torokhov wrote: > > > > > > Hi Andreas, > > > > > > On Wed, Aug 20, 2014 at 04:46:38AM +0200, Andreas Mohr wrote: > > >

Re: [PATCH 1/2] SOUND: kill gameport bits

2014-08-19 Thread Vojtech Pavlik
On Tue, Aug 19, 2014 at 10:18:15PM -0700, Dmitry Torokhov wrote: > Are you actively testing gameport interfaces with real joysticks/gamepads on > these cards? And what software is still in use that runs on these old boxes > (with mainline kernel)? I still do have a huge box of gameport hardware i

Re: [PATCH 1/2] SOUND: kill gameport bits

2014-08-19 Thread Dmitry Torokhov
On Wed, Aug 20, 2014 at 08:09:49AM +0200, Takashi Iwai wrote: > At Tue, 19 Aug 2014 22:18:15 -0700, > Dmitry Torokhov wrote: > > > > Hi Andreas, > > > > On Wed, Aug 20, 2014 at 04:46:38AM +0200, Andreas Mohr wrote: > > > > > Hi, > > > > > > > Gameport support hasn't been working well ever since

Re: [PATCH 1/2] SOUND: kill gameport bits

2014-08-19 Thread Takashi Iwai
At Tue, 19 Aug 2014 22:18:15 -0700, Dmitry Torokhov wrote: > > Hi Andreas, > > On Wed, Aug 20, 2014 at 04:46:38AM +0200, Andreas Mohr wrote: > > > Hi, > > > > > Gameport support hasn't been working well ever since cpufreq became > > > mainstream and it becomes increasingly hard to find hardware

Re: [PATCH 1/2] SOUND: kill gameport bits

2014-08-19 Thread Andreas Mohr
On Tue, Aug 19, 2014 at 10:18:15PM -0700, Dmitry Torokhov wrote: > Hi Andreas, > > On Wed, Aug 20, 2014 at 04:46:38AM +0200, Andreas Mohr wrote: > > > Hi, > > > > > Gameport support hasn't been working well ever since cpufreq became > > > mainstream and it becomes increasingly hard to find hardw

Re: [PATCH 1/2] SOUND: kill gameport bits

2014-08-19 Thread Dmitry Torokhov
Hi Andreas, On Wed, Aug 20, 2014 at 04:46:38AM +0200, Andreas Mohr wrote: > Hi, > > > Gameport support hasn't been working well ever since cpufreq became > > mainstream and it becomes increasingly hard to find hardware and > > software > > that would run on such old hardware. > > Given that I'm

Re: [PATCH 1/2] SOUND: kill gameport bits

2014-08-19 Thread Andreas Mohr
Reply-To: In-Reply-To: <1408466497-25640-1-git-send-email-dmitry.torok...@gmail.com> X-Priority: none Hi, > Gameport support hasn't been working well ever since cpufreq became > mainstream and it becomes increasingly hard to find hardware and > software > that would run on such old hardware. Gi