Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Shirkey <pshirkey@boosthardware.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Jaroslav Kysela <perex@suse.cz>,
	Martin Langer <martin-langer@gmx.de>,
	Clemens Ladisch <clemens@ladisch.de>,
	"alsa-devel@lists.sourceforge.net"
	<alsa-devel@lists.sourceforge.net>
Subject: Re: Re: [linux-audio-user] Evolution UC16 problems, modules.conf for usb-midi and usb-audio together
Date: Wed, 23 Oct 2002 21:25:01 +0900	[thread overview]
Message-ID: <3DB6951D.4090605@boosthardware.com> (raw)
In-Reply-To: s5hwuo91jl0.wl@alsa2.suse.de

Takashi Iwai wrote:
> At Wed, 23 Oct 2002 13:02:28 +0200 (CEST),
> Jaroslav wrote:
> 
>>On Wed, 23 Oct 2002, Martin Langer wrote:
>>
>>
>>>On Wed, Oct 23, 2002 at 11:50:37AM +0200, Clemens Ladisch wrote:
>>>
>>>>And you need to say which driver to use for snd-card-1. For the UC16 with
>>>>0.9.0rc3, it would be
>>>>	alias snd-card-1 snd-usb-midi
>>>>For 0.9.0rc4, it would be
>>>>	alias snd-card-1 snd-usb-audio
>>>>
>>>
>>>
>>>It would be better to add this module name change to the rc4 announce lines on
>>>www.alsa-project.org !
>>
>>It's not possible to comment changes for all drivers in the news 
>>section...
> 
> 
> but the change of driver names is actually very important for users,
> and there are only few:
> 
> 	snd-via686, snd-via8233 ==> snd-via82xx
> 	snd-usb-midi ==> snd-usb-audio
> 

Well I have already updated the online docs. With specifics references 
in the notes for these drivers.

It wouldn't hurt to add a note to the main page too though. It is 
profeesional courtesy.


-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================

"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem



-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en

      parent reply	other threads:[~2002-10-23 12:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1035239386.4549.73.camel@hamish.iriXx.org>
     [not found] ` <3DB57DD6.8070303@boosthardware.com>
     [not found]   ` <3DB59381.5000007@iriXx.org>
2002-10-22 19:06     ` [linux-audio-user] Evolution UC16 problems, modules.conf for usb-midi and usb-audio together Patrick Shirkey
2002-10-23  1:49       ` m
2002-10-23  9:50         ` Clemens Ladisch
2002-10-23 10:28           ` m
2002-10-23 13:00             ` Clemens Ladisch
2002-10-23 20:17               ` m
2002-10-23 11:03           ` Martin Langer
2002-10-23 11:02             ` Jaroslav Kysela
2002-10-23 11:27               ` Takashi Iwai
2002-10-23 11:44                 ` Martin Langer
2002-10-23 12:25                 ` Patrick Shirkey [this message]

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=3DB6951D.4090605@boosthardware.com \
    --to=pshirkey@boosthardware.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=clemens@ladisch.de \
    --cc=martin-langer@gmx.de \
    --cc=perex@suse.cz \
    --cc=tiwai@suse.de \
    /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