All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org, Adam Goode <agoode@chromium.org>
Subject: Re: seq module loading issue
Date: Thu, 09 Oct 2014 11:21:28 +0200	[thread overview]
Message-ID: <s5hy4spioo7.wl-tiwai@suse.de> (raw)
In-Reply-To: <54365211.5040604@ladisch.de>

At Thu, 09 Oct 2014 11:14:57 +0200,
Clemens Ladisch wrote:
> 
> Takashi Iwai wrote:
> > Clemens Ladisch wrote:
> >> Takashi Iwai wrote:
> >>> If it were a simple cleanup, I'm fine with it.  But this leads to
> >>> a major behavior change, which has a high risk of incompatibility.
> >>
> >> But there would be no changed behaviour as far as the API is concerned
> >> (except for this particular issue, which is a bug).
> >
> > Currently, the sequencer stuff can be suppressed by simply not loading
> > snd-seq core module itself.  Do you mean to drop this feature?
> 
> Yes.
> 
> > Some distros don't load sequencer modules nowadays as default.
> 
> Do you know why?  Any reason except memory?

Mostly yes, and also reduce the installation base.

> > So it would result in a clear behavior change on the whole system.
> 
> And alsa-lib tries its best to do autoloading to hide the fact that
> snd-seq might not have been loaded.  Therefore, it has never been
> possible to assume, at any time, that snd-seq is _not_ loaded.

What if the sound system doesn't exist at all like a server?  The
module is built and provided even on such a system by a distro, but
it's just not enabled.

> Is the high risk of incompatibility that you mentioned this assumption,
> or anything else?

It results in a surprising outcome, and it's what I'd like to avoid.


Takashi

  reply	other threads:[~2014-10-09  9:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-08 22:00 seq module loading issue Adam Goode
2014-10-09  6:42 ` Takashi Iwai
2014-10-09  7:29   ` Clemens Ladisch
2014-10-09  7:38     ` Takashi Iwai
2014-10-09  9:14       ` Clemens Ladisch
2014-10-09  9:21         ` Takashi Iwai [this message]
2014-10-09  9:46           ` Takashi Iwai
2014-10-09 15:45             ` Takashi Iwai
2014-10-10 21:45               ` Adam Goode
2014-10-09  7:29 ` 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=s5hy4spioo7.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=agoode@chromium.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.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 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.