All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sentinel <sentinel@optonline.net>
To: alsa-devel@alsa-project.org
Subject: spdif/iec958 outputs at VT1708S not recognized
Date: Tue, 26 May 2009 10:24:59 -0400	[thread overview]
Message-ID: <000401c9de0d$c06d27d0$41477770$@net> (raw)

I tried using the snapshot because I was having the same problem as Peter
was.  No spdif out on my vt1708s.  Unfortunately for me my build didn't go
quite as well, for some reason I had 2 undefined which make the snd.ko fail
to load.  Is there something that I'm missing?  I am running slamd64 distro
current, with the latest kernel along with the alsa kernel patch
"2.6.29.4-rt15".   Please help.

 

  Building modules, stage 2.

  MODPOST 131 modules

WARNING: "register_sound_special_device" [/usr/src/alsa-driver/acore/snd.ko]
undefined!

WARNING: "unregister_sound_special" [/usr/src/alsa-driver/acore/snd.ko]
undefined!

make[1]: Leaving directory `/usr/src/linux-2.6.29.4'

utils/link-modules /usr/src/alsa-driver

             reply	other threads:[~2009-05-26 14:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-26 14:24 Sentinel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-05-27  3:19 spdif/iec958 outputs at VT1708S not recognized Sentinel
2009-05-27  2:57 Sentinel
2009-05-27  5:35 ` Takashi Iwai
     [not found]   ` <003401c9dee9$322399f0$966acdd0$@net>
2009-05-27 16:51     ` Takashi Iwai
2009-05-26  3:04 Sentinel
2009-05-24  4:24 linux user
2009-04-29 12:25 Peter Niemayer
2009-04-29 15:07 ` Takashi Iwai
2009-05-05 10:48   ` Peter Niemayer
2009-05-07 14:17     ` Takashi Iwai
2009-05-07 14:17     ` Takashi Iwai
2009-05-08  9:21       ` Peter Niemayer
2009-05-08  9:30         ` Takashi Iwai
2009-05-11  8:56           ` Peter Niemayer
2009-04-29 15:19 ` David Douglas
2009-04-29 16:41   ` Vedran Miletić

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='000401c9de0d$c06d27d0$41477770$@net' \
    --to=sentinel@optonline.net \
    --cc=alsa-devel@alsa-project.org \
    /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.