Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: James Courtier-Dutton <James@superbug.co.uk>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] New snd-audigyls driver available.
Date: Fri, 03 Dec 2004 22:09:02 +0100	[thread overview]
Message-ID: <s5hzn0v1441.wl@alsa2.suse.de> (raw)
In-Reply-To: <41B0CA3C.8070606@superbug.co.uk>

At Fri, 03 Dec 2004 20:19:08 +0000,
James Courtier-Dutton wrote:
> 
> Takashi Iwai wrote:
> > At Fri, 03 Dec 2004 19:18:41 +0000,
> > James Courtier-Dutton wrote:
> > 
> >>Takashi Iwai wrote:
> >>
> >>>At Thu, 02 Dec 2004 22:42:15 +0000,
> >>>James Courtier-Dutton wrote:
> >>>
> >>>
> >>>>I have updated the snd-audigyls driver.
> >>>>It now consists of several .c files because the old audigyls.c was 
> >>>>getting too big.
> >>>>
> >>>>Please download from
> >>>>http://www.alsa-project.org/~james/alsa-driver/audigyls.0.0.20.tar.bz2
> >>>>
> >>>>untar that into ./alsa-driver/pci/emu10k1
> >>>
> >>>
> >>>How about to create its own subdirectory pci/audigyls?
> >>>There is no sharing module between audigyls and emu10k.
> >>>
> >>>
> >>>Takashi
> >>>
> >>>
> >>
> >>There are no major similarities between the ca0106 driver and the emu10k 
> >>driver.
> >>So creating a new directory seems like a good idea to me.
> >>The chip on the card is labeled "CA0106-DAT", so maybe we should rename 
> >>audigyls to ca0106.
> >>So, the new directory would be ca0106, and the filename would change.
> >>e.g. audigyls_main.c -> ca0106_main.c
> >>
> >>I think this renaming might be a good idea, because that driver works 
> >>with the "AudigyLS" and "Live 24bit" so calling the driver the 
> >>"audigyls" is a bit of a mistake really.
> > 
> > 
> > OTOH, ca0106 would be hard to find out that Audigy LS corresponds to
> > it...
> > 
> > I don't mind to rename it from the technical viewpoint, though.
> > 
> > 
> >>So, just take the files, make those simple changes and then add them to 
> >>the alsa cvs.
> > 
> > 
> > Shall I replace the struct/function names from audigyls to ca0106,
> > too?  Or, would you like to keep audigyls there?
> > 
> > 
> > Takashi
> > 
> 
> Ah! Good question. I think for the sake of consistancy, replacing those 
> would also be a good idea.
> Do you want me to do that, or would it be easier if you do it.

Could you do that?  I can't test the changed driver here.


Takashi


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

  reply	other threads:[~2004-12-03 21:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-02 22:42 [PATCH] New snd-audigyls driver available James Courtier-Dutton
2004-12-03 11:38 ` Takashi Iwai
2004-12-03 19:18   ` James Courtier-Dutton
2004-12-03 20:05     ` Takashi Iwai
2004-12-03 20:19       ` James Courtier-Dutton
2004-12-03 21:09         ` Takashi Iwai [this message]
2004-12-04 12:38           ` James Courtier-Dutton
2004-12-06 15:28             ` Takashi Iwai

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=s5hzn0v1441.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=James@superbug.co.uk \
    --cc=alsa-devel@alsa-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox