linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sven Luther <sven@genesi-usa.com>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: Sylvain Munaut <tnt@246tNt.com>,
	linuxppc-dev@ozlabs.org, spitzauer_77@gmx.de,
	sven@genesi-usa.com, Marian Balakowicz <m8@semihalf.com>
Subject: Re: State of the MPC5200 PSC AC97 driver
Date: Fri, 11 Apr 2008 09:34:50 +0200	[thread overview]
Message-ID: <20080411073450.GA1818@powerlinux.fr> (raw)
In-Reply-To: <20080411065100.GQ13814@pengutronix.de>

On Fri, Apr 11, 2008 at 08:51:00AM +0200, Robert Schwebel wrote:
> Hi Matt,
> 
> On Thu, Apr 10, 2008 at 04:25:20PM +0100, Matt Sealey wrote:
> > I have a copy of the driver I hacked to work with the new PSC
> > framework but it doesn't "work" anymore - I have no idea why.
> >
> > Mail me privately if you want it, I have no time to make patches or
> > look for a good reason for the breakages, but it compiles at least.
> > The Efika hack should be gone now (irrelevant since we released a
> > firmware that obseletes it) and the other fixmes should be by the
> > wayside considering the fscking thing doesn't play sound anymore...
> 
> I'd be interested as well; do I read your mail right that you have
> already managed to hear sound coming out of the MPC5200B PSC AC97
> interface? You would be the first one I've heared of, so it would
> definitely be interesting to see your code. 

Indeed, sound was known to work on the efika plateform, altough it is
the last patch which not merged upstream, and needs some work.

I leave matt send it to you, as he has been more in touch with this
lately.

Friendly,

Sven Luther

  reply	other threads:[~2008-04-11  7:34 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-10 10:44 State of the MPC5200 PSC AC97 driver Marian Balakowicz
2008-04-10 13:50 ` Robert Schwebel
2008-04-10 15:25 ` Matt Sealey
2008-04-11  6:51   ` Robert Schwebel
2008-04-11  7:34     ` Sven Luther [this message]
2008-04-11  7:29 ` Sylvain Munaut
2008-04-15  8:03   ` Juergen Beisert
2008-04-16 11:24     ` Juergen Beisert
2008-04-17 14:19       ` RFC: " Juergen Beisert
2008-04-17 14:23         ` Matt Sealey
2008-04-17 14:41           ` Juergen Beisert
2008-04-17 14:54             ` Matt Sealey
2008-04-17 15:05         ` Matt Sealey
2008-04-17 15:23           ` Juergen Beisert
2008-04-17 15:10         ` Matt Sealey
2008-04-17 15:23           ` Juergen Beisert
2008-04-17 15:43             ` Matt Sealey
2008-04-17 15:46               ` Sergei Shtylyov
2008-04-18 15:43         ` Peter Czanik
2008-04-18 16:02           ` Juergen Beisert
2008-04-18 18:11             ` Matt Sealey
2008-04-18 22:53               ` Grant Likely
2008-04-19 12:02                 ` Matt Sealey
2008-04-19 15:59                   ` Grant Likely
2008-04-21  8:02                   ` Juergen Beisert
2008-04-21 17:04                     ` Matt Sealey
2008-04-19 16:03           ` Grant Likely
2008-04-22 14:20         ` Olaf Hering
2008-04-11  9:23 ` State of the " Marian Balakowicz
2008-04-11 13:50   ` Grant Likely
2008-04-11 14:53     ` Marian Balakowicz

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=20080411073450.GA1818@powerlinux.fr \
    --to=sven@genesi-usa.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=m8@semihalf.com \
    --cc=r.schwebel@pengutronix.de \
    --cc=spitzauer_77@gmx.de \
    --cc=tnt@246tNt.com \
    /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).