All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Benny Sjostrand <gorm@cucumelo.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: More CS4630, secondary CODEC output.
Date: Thu, 01 Aug 2002 12:57:23 +0200	[thread overview]
Message-ID: <s5hwuraalt8.wl@alsa2.suse.de> (raw)
In-Reply-To: <3D4901D9.7040409@cucumelo.org>

At Thu, 01 Aug 2002 11:39:37 +0200,
Benny Sjostrand wrote:
> 
> >
> >
> >
> >I merged your codes into the cvs.
> >The codes are almost identical except for small bugfixes,
> >re-indentation, and replacement of debug printing.
> >
> -:)
> 
> >
> >To be sure, the old dsp image is still chosen unless
> >CONFIG_SND_CS46XX_NEW_DSP is set to yes.
> >For compiling the new dsp image, please remove the comments in
> >alsa-driver/pci/cs46xx/Makefile.
> >
> With the new PCM multi channel support, I believe  there no way
> to have the support for the old image,  to many changes in cs46xx_lib.c now
> hardly depends on the new stuff.

yep, looks so...

> So if we want to still support the old code i think the only way is to 
> create
> a new directory  alsa-driver/pci/cs46xx_old/_new, having to independent
> cs46xx drivers.

i'm now merging the new stuff.  let's see what happens.

> But I hope that in some near future we can discard the old cs46xx.
> Of course that we must be sure it work at least so good as before with all
> known CS46xx soundcards before discarding anything.

yes.  if the new driver is confirmed to work on most of machines
(cs46xx is used on many notebooks), then we can obsolete it.

> 
> >Please send patches againt cvs if you modify the driver more, so that
> >I can commit it soon.
> >
> Well, i got some more work to do. I will try fixup my new code changes 
> so it follows
> the coding-style used by ALSA, and then become mergable with current CVS.
> (and you dont have to do all thoose indentation fixes again)

the coding-style of ALSA is not particular except for its naming
rule.  we followed the standard kernel coding style.

as said, i'm now managing to merge the 0731 stuff.
just a moment...


ciao,

Takashi


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2002-08-01 10:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-26 23:01 More CS4630, secondary CODEC output Benny Sjostrand
2002-07-27  0:36 ` Peter Heatwole
2002-07-27  7:02   ` Benny Sjostrand
2002-07-27 15:13     ` Frank van de Pol
2002-07-27 16:13       ` Peter Heatwole
2002-08-01  1:14     ` Peter Heatwole
2002-08-01  9:40 ` Takashi Iwai
2002-08-01  9:39   ` Benny Sjostrand
2002-08-01 10:57     ` Takashi Iwai [this message]
2002-08-01 12:42       ` Takashi Iwai
2002-08-01 12:57         ` Benny Sjostrand
2002-08-02  5:51         ` Benny Sjostrand
2002-08-02 10:14           ` Takashi Iwai
2002-08-02 15:47           ` Peter Heatwole
2002-08-02 18:16             ` Benny Sjostrand

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=s5hwuraalt8.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=gorm@cucumelo.org \
    /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.