From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Patrick McFarland <pmcfarland@downeast.net>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: alsa es1371's joystick functionality broken in 2.6.11-mm4
Date: Sun, 20 Mar 2005 22:21:37 -0500 [thread overview]
Message-ID: <200503202221.37576.dtor_core@ameritech.net> (raw)
In-Reply-To: <200503202104.46144.pmcfarland@downeast.net>
On Sunday 20 March 2005 21:04, Patrick McFarland wrote:
> On Sunday 20 March 2005 07:39 pm, Andrew Morton wrote:
> > Patrick McFarland <pmcfarland@downeast.net> wrote:
> > > It seems that the es1371 driver (which provides its own joystick port
> > > driver) is broken in at least 2.6.11-mm4. I don't know when it broke, but
> > > it used to work around in the 2.6.8/9 days (I haven't used the joystick
> > > in awhile). The hardware and joystick still both work (tested in
> > > Windows).
> >
> > Please define "broken". I assume that audio still comes out, but that the
> > joystick doesn't work?
>
> Yup, audio works fine, this is why I never noticed. Also, the external midi
> interface also works fine. Digging around, /proc/asound/card0/audiopci says
> "Joystick enable: off, Joystick port: 0x200".
>
> I've also been looking through alsa's cvs for alsa-kernel, and I can't see any
> changes that might have broken it.
>
I could have broken it during my gameport sysfs integration... Although I can't
see anything that could cause the breakage. Can I please see your .config?
--
Dmitry
next prev parent reply other threads:[~2005-03-21 3:21 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 [this message]
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
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=200503202221.37576.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=akpm@osdl.org \
--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