All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: ALSA devel <alsa-devel@lists.sourceforge.net>
Subject: isa_bus: gusclassic
Date: Sun, 18 Feb 2007 20:48:19 +0100	[thread overview]
Message-ID: <45D8AD83.4000704@gmail.com> (raw)

Good day.

===
gusclassic: port to isa_bus infrastructure

Signed-off-by: Rene Herman <rene.herman@gmail.com>
===

snd_gusclassic_init() is no more -- the flags are already initialized to 
0 as part of the snd_gus_card structure itself and while I sort of 
expect that the C standard won't have many positive things to say about 
initializing bitfields through a kzalloc(), the code relies on this for 
other flags as well. The joystick_dac value is set directly in probe() 
now (I saw it's the same in all gus variants so should probably at some 
point be moved to snd_gus_create).

This has been tested, and works the same as before, which is to say not 
quite right.

It plays okay through ALSA's OSS emulation, but native ALSA complains:

   ALSA lib pcm.c:2017:(snd_pcm_open_conf) Invalid type for PCM
   default definition (id: default, value: cards.pcm.default)
   ALSA snd_pcm_open error: Invalid argument

Using "hw:0" gets:

   ALSA snd_pcm_hw_params_set_access error: Invalid argument

and "plughw:0" gets:

   ALSA lib pcm_plug.c:773:(snd_pcm_plug_hw_refine_schange) Unable to
   find an usable access for 'plughw:0'
   ALSA snd_pcm_hw_params_set_access error: Invalid argument

Although I'm familiar with the ALSA kernel side, I can't say the same 
about the userland or the interaction between the two and this looks 
like it might be a problem at that level. So I thought I'd just ask 
you... ;-)

(but as said, patch is good to go)

Rene.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

             reply	other threads:[~2007-02-18 19:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-18 19:48 Rene Herman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-18 19:51 isa_bus: gusclassic Rene Herman

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=45D8AD83.4000704@gmail.com \
    --to=rene.herman@gmail.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --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 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.