From: Luca Montecchiani <luca.montecchiani@teamfab.it>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Luca Montecchiani <m.luca@iname.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@redhat.com>
Subject: Re: [PATCH] Trident 4DWave DX/NX joystick support
Date: Thu, 20 Dec 2001 17:05:25 +0100 [thread overview]
Message-ID: <3C220C45.FD0D1CB2@teamfab.it> (raw)
In-Reply-To: <3C21229F.A6864423@iname.com> <20011220153855.C30746@suse.cz>
Vojtech Pavlik wrote:
> I must say I don't like the patch much.
There are couples of other pci cards that do the same
and right now is the only way to make joystick works with
trident sound card.
I hope to help some users around here.
> If there is anything going to be added to trident.c
> in regards to enabling the joystick, I think most of
> the pcigame.c code should be moved in there.
Not necessary, 2.2.19 joy-pci code works fine, no conflict
no oops, what about comparing against 2.4.x pcigame ?
Unfortunately I don't know how do that, but I can help you
testing patch, etc...
I hope to provide you the oops I've got insmodding analog
tomorrow.
> That way, there won't be
> resource conflicts and we won't lose any functionality.
I don't understand where the problem came from, with
2.2.19 everything work fine, I can use the joy-pci with
the trident module up and running, with the 2.4.17rc2
trident and pcigame are mutually exclusive.
Because of the 2.4.x pci changes ? Let's see.
ciao,
luca
next prev parent reply other threads:[~2001-12-20 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 23:28 [PATCH] Trident 4DWave DX/NX joystick support Luca Montecchiani
2001-12-20 14:38 ` Vojtech Pavlik
2001-12-20 16:05 ` Luca Montecchiani [this message]
2001-12-20 20:57 ` Vojtech Pavlik
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=3C220C45.FD0D1CB2@teamfab.it \
--to=luca.montecchiani@teamfab.it \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.luca@iname.com \
--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