alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: The Linux Audio Developers' Mailing List
	<linux-audio-dev@lists.linuxaudio.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: 2.6.31.x vs. rme vs. alsa 1.0.22?
Date: Tue, 23 Feb 2010 00:20:49 +0000	[thread overview]
Message-ID: <1266884449.3704.214.camel@localhost.localdomain> (raw)
In-Reply-To: <1266884215.3704.208.camel@localhost.localdomain>

On Tue, 2010-02-23 at 00:16 +0000, Fernando Lopez-Lezcano wrote:
> On Mon, 2010-02-22 at 23:51 +0000, Fernando Lopez-Lezcano wrote:
> > On Tue, 2010-02-16 at 17:58 -0800, Fernando Lopez-Lezcano wrote:
> > > Hey, has anyone been seeing strange behavior from this combination?
> > > 
> > >   kernel 2.6.31.x rt20 + alsa 1.0.22 userland
> > >   RME card (pcmcia card + multiface)
> > > 
> > > hdspmixer is not doing the right thing (does not initialize the card in
> > > a way in which playback works), it does not see the hwdep interface (or
> > > something like that) and disables metering,
> [MUNCH]
> > I have been trying to see if I can figure _anything_ out of this...
> > 
> > A diff of 2.6.29 (last known working) against 2.6.31.12 reveals
> > something that might have an influence on the problem:
> > 
> > in snd_hdsp_create_hwdep there are two lines added:
> > 
> > + hw->ops.open = snd_hdsp_hwdep_dummy_op;
> 
> Hmmm, looks like snd_hdsp_hwdep_dummy_op is not passing back the
> hdsp->hwdep structure to the open call at all (returning 0 is not enough
> from the description of the alsa api). That would explain what is
> happening, most probably no ioctls are found...
> 
> Am I on the right track?

Argh. I was looking at the diff backwards (DOH!). The ops.open and
ops.release ioctl calls are _missing_ in the 2.6.31.12 tree. 

-- Fernando


> >   hw->ops.ioctl = snd_hdsp_hwdep_ioctl;
> > + hw->ops.release = snd_hdsp_hwdep_dummy_op;
> > 
> > And snd_hdsp_hwdep_dummy_op just returns 0...
> > 
> > Other differences between the two files (not that many) seem irrelevant
> > to me. 
> > 
> > I imagine this is what is causing the difference in behavior (hwdep
> > fails). Any suggestions on what I could try to fix this?
> > 
> > Thanks for any help!

  reply	other threads:[~2010-02-23  0:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17  1:58 2.6.31.x vs. rme vs. alsa 1.0.22? Fernando Lopez-Lezcano
2010-02-22 23:51 ` Fernando Lopez-Lezcano
2010-02-23  0:06   ` Fernando Lopez-Lezcano
2010-02-23  0:16   ` Fernando Lopez-Lezcano
2010-02-23  0:20     ` Fernando Lopez-Lezcano [this message]
     [not found]       ` <1266884449.3704.214.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-02-23 20:48         ` [LAD] [alsa-devel] " Fernando Lopez-Lezcano
     [not found]           ` <1266958133.2507.234.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-02-23 21:22             ` Paul Davis

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=1266884449.3704.214.camel@localhost.localdomain \
    --to=nando@ccrma.stanford.edu \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-audio-dev@lists.linuxaudio.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).