Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Kevin Puetz <puetzk@iastate.edu>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: [PATCH] cs46xx some few corrections
Date: Wed, 18 Dec 2002 15:25:54 +0100	[thread overview]
Message-ID: <s5hy96nv1xp.wl@alsa2.suse.de> (raw)
In-Reply-To: <200212180800.50494.puetzk@iastate.edu>

At Wed, 18 Dec 2002 08:00:50 -0600,
Kevin Puetz wrote:
> 
> > > Sumary of changes:
> > > - Some volume bug fixes
> > > - SPDIF input fix.
> > > - Clear sample buffer after closing IEC958 stream.
> > > - Ring buffer fix (see my previous mail)
> > > - Some other misses, corrections ....
> >
> > applied.  thanks for your patch!
> 
> nice, now alsa cvs and the cs46xx are best friends again :-)
> 
> Any chance of getting a 2.5 merge sometime soon (since it doesn't seem that 
> the current cs46xx builds if dropped into a 2.5 tree)? It sure would be nice 
> to have the phase problems fixed there as well.

Jaroslav already posted the latest bk-patch, so hopefully it will be
merged by Linus soon.


> If there's supposed to be a way to build the alsa cvs against 2.5, that would 
> be fine too, but I couldn't figure it out.

basically, you can just copy alsa-kernel directories on 2.5 tree.
the directory structure is a bit different like the following:

alsa-kernel/include	-> linux/include/sound
alsa-kernel/Documentation -> linux/Documentation/alsa
alsa-kernel/scripts	-> skip (contains only helper scripts)
alsa-kernel/oss		-> skip (it's empty)
alsa-kernel/core, and others
			-> linux/sound/core, etc.

don't forget to reserve the old linux/sound/oss directory.
alsa-kernel/oss directory contains nothing, of course :)


Takashi


-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/

  reply	other threads:[~2002-12-18 14:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10  8:09 [PATCH] cs46xx some few corrections Benny Sjostrand
2002-12-10 13:13 ` Friedrich Ewaldt
2002-12-11 21:50   ` Benny Sjostrand
2002-12-12 14:24     ` Friedrich Ewaldt
2002-12-12 21:00       ` Benny Sjostrand
2002-12-10 16:38 ` Takashi Iwai
2002-12-18 14:00   ` Kevin Puetz
2002-12-18 14:25     ` Takashi Iwai [this message]
2002-12-18 14:39     ` Jaroslav Kysela

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=s5hy96nv1xp.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=puetzk@iastate.edu \
    /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