From: Clemens Ladisch <clemens@ladisch.de>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: tiwai@suse.de,
ALSA Development Mailing List <alsa-devel@alsa-project.org>,
jkysela@redhat.com
Subject: Re: [PATCH] alsa: support module on-demand loading for seq and timer
Date: Tue, 23 Nov 2010 17:56:29 +0100 [thread overview]
Message-ID: <4CEBF23D.6020801@ladisch.de> (raw)
In-Reply-To: <AANLkTi=j4XA5r4DSBdZKxLJNvoAQzR+daXu0UzjcvLo4@mail.gmail.com>
Kay Sievers wrote:
> On Tue, Nov 23, 2010 at 16:45, Clemens Ladisch <clemens@ladisch.de> wrote:
>> Kay Sievers wrote:
>>> +MODULE_ALIAS("devname:snd/seq");
>>
>> The device name that alsa-lib tries to use for autoloading is actually
>> /dev/aloadSEQ.
>
> That might need to be changed then, if something depends on that, but
> nothing ever tries to open /dev/snd/seq.
No, alsa-lib pokes /dev/aloadSEQ only if opening /dev/snd/seq has
failed. (Something historical, I believe.)
>> So you're going to add the entries for card driver autoloading
>> (/dev/aloadC*), too?
>
> No, we only ever handle single-instance devices with a single fixed
> dev_t, not ones with an arbitrary number of device instances.
>
> Card drivers are loaded by hardware matches today, not on-demand, and
> not by an card number.
There are card drivers without matching hardware (such as MIDI over
a serial port, or virtual devices).
> There are no configured numbered module aliases for sound cards
> anymore, that can't work with today's setups.
Just that it cannot work with systemd doesn't imply that nobody still
uses it or that it could be dropped without regards for backward
compatibility.
Anyway, this patch is independent of ALSA's old autoload code.
Applied.
Regards,
Clemens
next prev parent reply other threads:[~2010-11-23 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 10:42 [PATCH] alsa: support module on-demand loading for seq and timer Kay Sievers
2010-11-23 15:45 ` Clemens Ladisch
2010-11-23 15:56 ` Kay Sievers
2010-11-23 16:56 ` Clemens Ladisch [this message]
2010-11-23 17:13 ` Kay Sievers
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=4CEBF23D.6020801@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=jkysela@redhat.com \
--cc=kay.sievers@vrfy.org \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).