From: Juan Linietsky <coding@reduz.com.ar> (by way of Juan Linietsky <coding@reduz.com.ar>)
To: alsa-devel@lists.sourceforge.net
Subject: Re: bug in ens1371/ens1370 joystick driver
Date: Thu, 23 Oct 2003 16:23:26 -0300 [thread overview]
Message-ID: <200310231623.26007.coding@reduz.com.ar> (raw)
On Thursday 23 October 2003 04:14, you wrote:
> Juan Linietsky wrote:
> > The ens1371 driver takes a joystick_port parameter with range 1..8
> > but that same parameter is them put into a switch to detect io port
> > values like 0x200, 0x208, etc. so the joystick will never be detected.
>
> ens1370.c says:
> MODULE_PARM(joystick_port, "1-" __MODULE_STRING(SNDRV_CARDS) "i");
> MODULE_PARM_DESC(joystick_port, "Joystick port address.");
> MODULE_PARM_SYNTAX(joystick_port, SNDRV_ENABLED
> ",allows:{{0},{0x200},{0x208},{0x210},{0x218}},dialog:list");
>
> The range 1..8 means that it's possible to specify a parameter value
> for each of the up to 8 cards (SNDRV_CARDS is defined as 8). The
> parameter itself takes the correct values.
>
>
> Regards,
> Clemens
this is still not very helpful, as modinfo -p only returns:
joystick_port int array (min = 1, max = 8), description "Joystick port
address."
how are you supposed to know that you can only enter 0x200,0x208,etc?
Specially when in the OSS driver you do:
modprobe es1371 joystick=1
and it works flawlessly
Regards
Juan Linietsky
-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community? Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
next reply other threads:[~2003-10-23 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 19:23 Juan Linietsky [this message]
2003-10-24 10:53 ` bug in ens1371/ens1370 joystick driver Takashi Iwai
2003-10-24 16:49 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2003-10-23 2:59 Juan Linietsky
2003-10-23 7:14 ` 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=200310231623.26007.coding@reduz.com.ar \
--to=coding@reduz.com.ar \
--cc=alsa-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.