Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@gmail.com>
To: Timur Tabi <timur@freescale.com>
Cc: ALSA devel <alsa-devel@alsa-project.org>
Subject: Re: How do I update the ALSA SoundCard Matrix?
Date: Thu, 13 Sep 2007 19:36:12 +0200	[thread overview]
Message-ID: <46E9750C.9070702@gmail.com> (raw)
In-Reply-To: <46E952F4.4070906@freescale.com>

On 09/13/2007 05:10 PM, Timur Tabi wrote:

> I'm looking at 
> http://bugtrack.alsa-project.org/main/index.php/Matrix:Main. I'm trying 
> to add information on the CS4270 driver that I wrote, but I just don't 
> get it.  I know how to edit normal Wiki pages, but this looks different.
> 
> It looks like all the information is obtained from some database 
> somewhere.
> 
> This page
> 
> http://bugtrack.alsa-project.org/main/index.php/Help:Howto-Edit
> 
> supposedly tells me how to edit, but it's useless.  It doesn't really 
> tell me *how* to edit, it just tells me that it can.
> 
> So what am I missing?  How do I add information on a new driver?  I'll 
> need to add information on a new vendor soon, too.

When I added/updated a few things a while ago, I just did everything 
manually, working from example. Added various cards here:

http://www.alsa-project.org/main/index.php/Matrix:Vendor-Terratec

and created a new vendor page for AdLib, which probably serves nicely as a 
minimal template:

http://www.alsa-project.org/main/index.php/Matrix:Vendor-AdLib

The information in the current matrix was transferred from an older non-wiki 
matrix but as far as I know, this simple manual editing is all there's to it 
now. I'll admit I lost my way in the TerraTec page a few times since it gets 
fairly clumsy, but well, just refresh and check a lot before you commit ;-)

Rene.

  reply	other threads:[~2007-09-13 17:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13 15:10 How do I update the ALSA SoundCard Matrix? Timur Tabi
2007-09-13 17:36 ` Rene Herman [this message]
2007-09-13 22:20 ` Eliot Blennerhassett

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=46E9750C.9070702@gmail.com \
    --to=rene.herman@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=timur@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox