From: Takashi Iwai <tiwai@suse.de>
To: Thierry Vignaud <tvignaud@mandrakesoft.com>
Cc: Jaroslav Kysela <perex@suse.cz>,
"alsa-devel@lists.sourceforge.net"
<alsa-devel@lists.sourceforge.net>
Subject: Re: Re: [RFC] merging splited driver back
Date: Thu, 22 Aug 2002 16:29:25 +0200 [thread overview]
Message-ID: <s5h3ct7t1a2.wl@alsa2.suse.de> (raw)
In-Reply-To: <m2r8gr6mf6.fsf@vador.mandrakesoft.com>
At Thu, 22 Aug 2002 15:41:17 +0200,
Thierry Vignaud wrote:
>
> Takashi Iwai <tiwai@suse.de> writes:
>
> > > I don't like very much to merging of ENS1370 and ENS1371, because
> > > different codecs are used (snd-ak4531-codec and snd-ac97-codec).
> >
> > ah, yes, that's not beautiful to have two codec modules for one
> > driver.
> >
> >> Sure,
> >> there is common code (MIDI UART, most of PCM routines), but I think that
> >> the final difference (separate module with common code) will be
> >> negligible, but we may do it.
> >
> > well, then let's leave ens1370/1 as they are.
>
> this would have enbling to reduce memory usage if one have both 1370
> and 1371 cards, and/or reduce kernel package size :-)
the probability of former case is not so high, i guess :)
Takashi
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
next prev parent reply other threads:[~2002-08-22 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m27kimpp7r.fsf@vador.mandrakesoft.com>
2002-08-20 9:42 ` [RFC] merging splited driver back Takashi Iwai
2002-08-21 9:53 ` Jaroslav Kysela
2002-08-22 13:31 ` Takashi Iwai
2002-08-22 13:41 ` Thierry Vignaud
2002-08-22 14:29 ` Takashi Iwai [this message]
2002-08-22 18:06 ` Jaroslav Kysela
2002-08-22 19:25 ` Thierry Vignaud
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=s5h3ct7t1a2.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=perex@suse.cz \
--cc=tvignaud@mandrakesoft.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.