All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Anders Vinjar <andersvi@extern.uio.no>
Cc: alsa-user@lists.sourceforge.net, alsa-devel@lists.sourceforge.net
Subject: Re: [Alsa-devel] vxpocket 440 with alsa, problems with vxloader
Date: Fri, 14 Jan 2005 15:46:17 +0100	[thread overview]
Message-ID: <s5hllaw6pc6.wl@alsa2.suse.de> (raw)
In-Reply-To: <copllawumfe.fsf@olivier.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]

At Fri, 14 Jan 2005 15:15:17 +0100,
Anders Vinjar wrote:
> 
> Thanks alot for response.  It got me further, but still no sound
> out.  Anybody got a clue where this gets wrong?
> 
> >>> "TI" == Takashi Iwai <tiwai@suse.de> writes:
> 
> >> alsa is version 1.0.7
> 
> TI> vxpocket/vxp440 driver in ALSA 1.0.7 has a severe bug.
> TI> Try ALSA 1.0.8 instead.
> TI> 
> TI> On ALSA 1.0.8, the firmware is loaded via hotplug automatically, so
> TI> you don't need vxloader.  (It's only for 2.6 kernels.)
> TI> Don't forget to update alsa-firmware, too.
> 
> With alsa-1.0.8, and upgraded firmware it behaves as follows.
> Pcmcia card is card-1, builtin sound is card-0:

Does your kernel support hotplug firmware loader (CONFIG_FW_LOADER)?
And is hotplug working?

Check whether /proc/asound/devices whether you have a "[1-0] hardware
dependent device".  If you have it, the hotplug firmware loader isn't
enabled.  Use vxloader, run "vxloader -c1".

With the attached patch, you can check whether the firmware is loaded
or not via the proc file.


Takashi

[-- Attachment #2: Type: text/plain, Size: 868 bytes --]

Index: alsa-kernel/drivers/vx/vx_core.c
===================================================================
RCS file: /suse/tiwai/cvs/alsa/alsa-kernel/drivers/vx/vx_core.c,v
retrieving revision 1.12
diff -u -r1.12 vx_core.c
--- alsa-kernel/drivers/vx/vx_core.c	20 Dec 2004 11:04:40 -0000	1.12
+++ alsa-kernel/drivers/vx/vx_core.c	14 Jan 2005 14:43:46 -0000
@@ -610,6 +610,10 @@
 	static char *uer_type[] = { "Consumer", "Professional", "Not Present" };
 	
 	snd_iprintf(buffer, "%s\n", chip->card->longname);
+	snd_iprintf(buffer, "Xilinx Firmware: %s\n",
+		    chip->chip_status & VX_STAT_XILINX_LOADED ? "Loaded" : "No");
+	snd_iprintf(buffer, "Device Initialized: %s\n",
+		    chip->chip_status & VX_STAT_DEVICE_INIT ? "Yes" : "No");
 	snd_iprintf(buffer, "DSP audio info:");
 	if (chip->audio_info & VX_AUDIO_INFO_REAL_TIME)
 		snd_iprintf(buffer, " realtime");

  reply	other threads:[~2005-01-14 14:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-14 11:42 vxpocket 440 with alsa, problems with vxloader andersvi
2005-01-14 12:09 ` Takashi Iwai
2005-01-14 14:15   ` Anders Vinjar
2005-01-14 14:46     ` Takashi Iwai [this message]
2005-01-14 23:36       ` andersvi
2005-01-14 14:30   ` andersvi

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=s5hllaw6pc6.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=andersvi@extern.uio.no \
    /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.