Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Ivica Ico Bukvic <ico@fuse.net>
Cc: alsa-devel@lists.sourceforge.net, alsa-user@lists.sourceforge.net
Subject: Re: dxs_support and via82xx (yet once more)
Date: Fri, 23 Apr 2004 19:08:22 +0200	[thread overview]
Message-ID: <s5hisfqmxkp.wl@alsa2.suse.de> (raw)
In-Reply-To: <20040423165625.MXVQ19268.smtp2.fuse.net@64BitBadass>

At Fri, 23 Apr 2004 12:56:35 -0400,
Ivica Ico Bukvic wrote:
> 
> > > alias char-major-116 snd
> > > alias char-major-14 soundcore
> > > alias snd-card-0 via82xx
> >                    ^^^^^^^
> >                    snd-via82xx
> 
> Hmmm, but somewhere along the road while troubleshooting this/installing
> something told me (a script) that I should drop the snd- prefix. Are you
> saying that I still need snd- prefix? The alsa init does succeed after all
> even with only via82xx (modprobing) so that's why I am asking.

yes, the module name still consists of snd- prefix.
the snd_ prefix was dropped from the module OPTIONS.
(e.g. dxs_support would have been named as snd_dxs_support in the old
 versions.)

> > > #I tried every possible option
> > > options via82xx dxs_support=1
> > 
> > this line is useless.
> 
> Because it's missing snd- prefix? (I removed the hdsp stuff from the
> modules.conf for the better legibility but using cards without snd- prefix
> seemed to work just fine, so I am guessing that snd- is needed for the
> options call only, or am I misunderstanding this?)

snd- prefix is for the module NAMES, but not for module OPTIONS.
again, there is no via82xx module.  there is only snd-via82xx module.
defining the options for via82xx is useless because options for a
non-existing module will be never referred.


> > > options snd-card-0 dxs_support=1

this one is also useless.  remove it.
(snd-card-0 is just an alias, not the real module name.)


> > > options snd-via82xx dxs_support=1
> 
> Shouldn't this then work?

yes, in theory it should work.
that's why i asked you to make sure any other definitions exist.
there must be another error in the configuration.


BTW, i assume that are you using 2.4 kernel.  is it right?


Takashi


-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297

  reply	other threads:[~2004-04-23 17:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-23  4:12 dxs_support and via82xx (yet once more) ico
2004-04-23 10:43 ` Takashi Iwai
2004-04-23 16:56   ` Ivica Ico Bukvic
2004-04-23 17:08     ` Takashi Iwai [this message]
2004-04-24 18:02       ` [Alsa-devel] dxs_support and via82xx (yet once more) -- some new findings Ivica Ico Bukvic
2004-04-24 18:16         ` 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=s5hisfqmxkp.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=ico@fuse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox