From: Takashi Iwai <tiwai@suse.de>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: perex@suse.cz, alsa-devel@lists.sourceforge.net
Subject: Re: [PATCH] fix ymfpci port parameter handling
Date: Mon, 27 Oct 2003 12:10:21 +0100 [thread overview]
Message-ID: <s5hhe1v6in6.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.HPX.4.33n.0310230935090.295-100000@studcom.urz.uni-halle.de>
At Thu, 23 Oct 2003 09:37:44 +0200 (METDST),
Clemens Ladisch wrote:
>
>
> - fix detection of omitted (default) joystick_port parameter
> - make fm_port and mpu_port handling consistent with joystick_port
i think it'd be better to check all *_port parameters of all modules
to use the consistent values. so far, some drivers use the value 0 to
disable the device, some -1, and sometimes -1 is for the
auto-detection.
yes, it's cosmetic but important. we need to define the standard
values before ALSA 1.0 is out.
the candidates are:
a) -1 = disable, 0 = auto-detect, others = manual
b) 0 = disable, -1 = auto-detect, others = manual
c) 0 = disable, 1 = auto-detect, others = manual
d) 0 = disable, -1 = auto-detect, others = manual
i like the case (c) or (d).
in theory, the value 1 might be invalid in (c). but, these ports
parameters are anyway only for ISA devices, and 1 is never used as the
valid port address.
comments?
Takashi
-------------------------------------------------------
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 prev parent reply other threads:[~2003-10-27 11:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 7:37 [PATCH] fix ymfpci port parameter handling Clemens Ladisch
2003-10-27 11:10 ` Takashi Iwai [this message]
2003-10-27 11:34 ` Clemens Ladisch
2003-10-28 11:30 ` 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=s5hhe1v6in6.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.de \
--cc=perex@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