public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Patrick McFarland <pmcfarland@downeast.net>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>,
	linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: alsa es1371's joystick functionality broken in 2.6.11-mm4
Date: Wed, 11 May 2005 16:00:11 +0200	[thread overview]
Message-ID: <s5hhdh92784.wl@alsa2.suse.de> (raw)
In-Reply-To: <200504202303.33898.pmcfarland@downeast.net>

At Wed, 20 Apr 2005 23:03:27 -0400,
Patrick McFarland wrote:
> 
> [1  <text/plain; utf-8 (quoted-printable)>]
> On Wednesday 20 April 2005 10:29 pm, Dmitry Torokhov wrote:
> > Ok... I know that sidewinder needs its timeouts increased to about 6ms to
> > work with 2.6. Have you tried OSS driver - to make sure that layer above
> > the soundcard works?
> 
> Well, thats what I've been thinking thats screwing me. Because I've been using 
> ALSA since my 2.4.x days (I switched over to 2.6 and 2.6.1), and I know my 
> analog joystick works with ALSA and 2.6 (I just don't know when the bug 
> appeared) and I've also upgraded my ALSA userland over the years. Infact, I'm 
> almost convinced that the ALSA userland is causing the bug.

Hmm, I'm not sure what you "userland" mean, but ALSA lib and utils
have nothing to do with input devices...


Takashi

      reply	other threads:[~2005-05-11 14:00 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-20 20:57 alsa es1371's joystick functionality broken in 2.6.11-mm4 Patrick McFarland
2005-03-21  0:39 ` Andrew Morton
2005-03-21  2:04   ` Patrick McFarland
2005-03-21  3:21     ` Dmitry Torokhov
2005-03-22  0:58       ` Patrick McFarland
2005-03-22  3:15         ` Dmitry Torokhov
2005-03-22  3:41           ` Patrick McFarland
2005-03-22  3:49             ` Dmitry Torokhov
2005-03-22 12:06               ` Patrick McFarland
2005-03-22 13:58                 ` Dmitry Torokhov
2005-03-23  2:19                   ` Patrick McFarland
2005-03-23  4:41                     ` Patrick McFarland
2005-03-24  6:00                       ` Dmitry Torokhov
2005-03-25 14:28                         ` Patrick McFarland
2005-03-27 11:23                           ` Patrick McFarland
2005-03-31  4:59                             ` Patrick McFarland
2005-04-07 11:17                               ` Patrick McFarland
2005-04-07 19:52                                 ` Ian Pilcher
2005-04-08  1:33                                   ` Patrick McFarland
2005-04-15  1:18                                 ` Patrick McFarland
2005-04-15  1:26                                   ` Lee Revell
2005-04-15  1:41                                     ` Patrick McFarland
2005-04-20  4:47                                   ` Patrick McFarland
2005-04-21  1:42                                     ` Patrick McFarland
2005-04-21  2:12                                       ` Dmitry Torokhov
2005-04-21  2:21                                         ` Patrick McFarland
2005-04-21  2:29                                           ` Dmitry Torokhov
2005-04-21  3:03                                             ` Patrick McFarland
2005-05-11 14:00                                               ` Takashi Iwai [this message]

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=s5hhdh92784.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=akpm@osdl.org \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmcfarland@downeast.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