From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Takashi Iwai <tiwai@suse.de>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
"debian-powerpc@lists.debian.org"
<debian-powerpc@lists.debian.org>
Subject: Re: [PATCH] pmac: sound support for latest laptops
Date: Thu, 14 Apr 2005 23:15:14 +1000 [thread overview]
Message-ID: <1113484515.5516.100.camel@gaston> (raw)
In-Reply-To: <1113483344.5614.17.camel@localhost>
On Thu, 2005-04-14 at 14:55 +0200, Johannes Berg wrote:
> Hi,
>
> > This patch hacks the current Alsa snd-powermac driver to add support for
> > recent machine models with the tas3004 chip, that is basically new
> > laptop models.
>
> So this works, but is incompatible with gstreamer. I took it with a
> rhythmbox/gstreamer developer and he said that it's a driver issue. A
> gstreamer log is here:
> http://johannes.sipsolutions.net/files/rhythmbox-alsa-debug
> (produced by GST_DEBUG=alsa*:5 rhythmbox 2>&1 | tee logfile)
>
> He also asked me to try
> $ gst-launch-0.8 sinesrc ! alsasink device=hw:0
>
> which yields:
> RUNNING pipeline ...
> ERROR: pipeline doesn't want to play.
>
> So the conclusion was:
> "set_periods_near ioctl does something weird"
>
> Any ideas?
I don't know, this is definitely not a problem with the platform
specific part of the driver, which is what I've been dealin with lately.
You may find a better answer with the Alsa folks regarding the actual
PCM implementation.
next prev parent reply other threads:[~2005-04-14 13:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-10 6:16 [PATCH] pmac: sound support for latest laptops Benjamin Herrenschmidt
2005-04-10 8:37 ` Antonio-M. Corbi Bellot
2005-04-11 14:46 ` Takashi Iwai
2005-04-11 15:07 ` Johannes Berg
2005-04-11 15:21 ` Takashi Iwai
2005-04-12 0:04 ` Benjamin Herrenschmidt
2005-04-14 12:55 ` Johannes Berg
2005-04-14 13:15 ` Benjamin Herrenschmidt [this message]
2005-04-14 13:20 ` Johannes Berg
2005-04-14 16:18 ` Takashi Iwai
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=1113484515.5516.100.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=debian-powerpc@lists.debian.org \
--cc=johannes@sipsolutions.net \
--cc=linuxppc-dev@ozlabs.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 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).