From: Bill Fink <billfink@mindspring.com>
To: Michel D?nzer <michel@daenzer.net>
Cc: linuxppc-dev@lists.linuxppc.org,
yellowdog-general@lists.terrasoftsolutions.com
Subject: Re: dmasound audio patch
Date: Mon, 8 Apr 2002 10:14:43 -0400 [thread overview]
Message-ID: <20020408101443.01f48537.billfink@mindspring.com> (raw)
In-Reply-To: <1018270252.1870.8601.camel@tibook>
On 08 Apr 2002, Michel Dänzer wrote:
> On Mon, 2002-04-08 at 14:41, Bill Fink wrote:
> > On 08 Apr 2002, Michel Dänzer wrote:
> >
> > > Must be an old version of xmms? It swaps bytes if necessary since 1.2.5
> > > or so.
> >
> > Hi Michel,
> >
> > That's good to know. I was using xmms-1.2.4 that came with YDL 2.1,
> > but I see that YDL 2.2 has xmms-1.2.5, so I'll give that a try.
>
> Hmm, looking at our xmms changelog, the endianness fixes may only be in
> 1.2.6 or later. YMMV.
Well even the just released YDL 2.2 only has xmms-1.2.5, which is still
broken. For the record, I did get the Rawhide xmms-1.2.7 source RPM and
did an "rpm --rebuild" on it, and can report that xmms-1.2.7 does in fact
work fine, but that was a fair amount of work and time. I'm still going
to stick with my friend's dmasound kernel patch, so I don't have to go
through all this for the next sound app I might happen to try that's not
yet endianness aware.
-Thanks
-Bill
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-08 14:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-07 21:23 dmasound audio patch Bill Fink
2002-04-08 10:30 ` Michel Dänzer
2002-04-08 12:41 ` Bill Fink
2002-04-08 12:50 ` Michel Dänzer
2002-04-08 14:14 ` Bill Fink [this message]
2002-04-08 13:22 ` Bill Fink
2002-04-08 11:49 ` Benjamin Herrenschmidt
2002-04-08 19:23 ` Bill Fink
2002-04-08 18:45 ` Benjamin Herrenschmidt
2002-04-09 1:52 ` Bill Fink
2002-04-09 2:24 ` jeffk
2002-04-09 7:18 ` Ethan Benson
-- strict thread matches above, loose matches on Subject: below --
2002-04-10 3:36 Bill Fink
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=20020408101443.01f48537.billfink@mindspring.com \
--to=billfink@mindspring.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=michel@daenzer.net \
--cc=yellowdog-general@lists.terrasoftsolutions.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 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.