All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: alsa problems
Date: Tue, 28 Mar 2006 17:33:35 +0200	[thread overview]
Message-ID: <1143560015.12961.5.camel@localhost> (raw)
In-Reply-To: <s5hd5g67ipv.wl%tiwai@suse.de>

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

On Tue, 2006-03-28 at 16:21 +0200, Takashi Iwai wrote:

> Ah, that sounds OK, too.  The driver can return -ENOENT, so basically
> it looks same from the user-space as if there is no real device file.

Good point. I'm returning -ENODEV right now, but ENOENT might be
misleading, the open can also fail in the same way if the codec chips
behind the i2s bus aren't usable at the moment.

> OK, I'll pass you a patch later.
> I think, however, this won't go to 2.6.17 kernel since we have no
> caller yet.

No worries. I'll keep the current workaround, I'm not aiming for kernel
inclusion in the short term. Thus we can keep your patch on the queue
until my driver enters the queue :)

> A good point.  The handling of compressed formats is still under
> considration.  Any comments about preferred behavior are welcome.

Will think about it and send another mail.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]

      reply	other threads:[~2006-03-29 12:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28 12:10 alsa problems Johannes Berg
2006-03-28 13:08 ` Takashi Iwai
2006-03-28 13:11   ` Johannes Berg
2006-03-28 13:16     ` Takashi Iwai
2006-03-28 13:21       ` Johannes Berg
2006-03-28 13:36         ` Takashi Iwai
2006-03-28 13:44           ` Johannes Berg
2006-03-28 14:06             ` Takashi Iwai
2006-03-28 14:10               ` Johannes Berg
2006-03-28 14:21                 ` Takashi Iwai
2006-03-28 15:33                   ` Johannes Berg [this message]

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=1143560015.12961.5.camel@localhost \
    --to=johannes@sipsolutions.net \
    --cc=alsa-devel@alsa-project.org \
    --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.