Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Justin Cormack <justin@street-vision.com>
To: martin-langer@gmx.de
Cc: Takashi Iwai <tiwai@suse.de>,
	alsa-devel@lists.sourceforge.net,
	finnendahl@folkwang-hochschule.de
Subject: Re: RME installation problems
Date: 13 Feb 2003 15:51:35 +0000	[thread overview]
Message-ID: <1045151500.1545.33.camel@lotte> (raw)
In-Reply-To: <20030213131832.GB3246@tuba.home>

On Thu, 2003-02-13 at 13:18, Martin Langer wrote:
> On Thu, Feb 13, 2003 at 12:13:46PM +0100, Takashi Iwai wrote:
> > At Thu, 13 Feb 2003 12:08:51 +0100,
> > Martin Langer wrote:
> > > On Thu, Feb 13, 2003 at 11:44:24AM +0100, Orm Finnendahl wrote:
> > > > Hi Takashi,
> > > > Am Donnerstag, den 13. Februar 2003 um 10:31:09 Uhr (+0100) schrieb
> > > > Takashi Iwai:
> > > > 
> > > > > > > ie add the 0xb revision.
> > > > >
> > > > Yes. In the old driver it just checks for 0xa and 0x64. Just add a
> > > > line to also check for 0xb.
> > 
> > but i don't see any 0x64 there...
> > 
> 
> There was a mail by Justin few weeks ago, talking about the rev. 0x64.
> http://www.mail-archive.com/alsa-devel@lists.sourceforge.net/msg05383.html
> Looks like, that this solution doesn't find it's way into CVS. 
> 
> Justin, can you send us a patch of your work?
> 

it was just

Index: alsa-kernel/pci/rme9652/hdsp.c
===================================================================
RCS file: /suse/tiwai/cvs/alsa/alsa-kernel/pci/rme9652/hdsp.c,v
retrieving revision 1.20
diff -u -r1.20 hdsp.c
--- alsa-kernel/pci/rme9652/hdsp.c      7 Feb 2003 09:18:41 -0000      
1.20
+++ alsa-kernel/pci/rme9652/hdsp.c      13 Feb 2003 11:12:26 -0000
@@ -2981,6 +2981,7 @@
        
        switch (rev & 0xff) {
        case 0xa:
+       case 0x64:
                /* hdsp_initialize_firmware() will reset this */
                hdsp->card_name = "RME Hammerfall DSP";
                break;





-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en

  reply	other threads:[~2003-02-13 15:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-12 18:30 RME installation problems Orm Finnendahl
     [not found] ` <1045076338.1544.3.camel@lotte>
2003-02-12 19:12   ` Orm Finnendahl
     [not found]     ` <1045078205.1545.29.camel@lotte>
2003-02-12 20:07       ` Orm Finnendahl
2003-02-13  9:31         ` Takashi Iwai
2003-02-13 10:44           ` Orm Finnendahl
2003-02-13 11:08             ` Martin Langer
2003-02-13 11:13               ` Takashi Iwai
2003-02-13 13:18                 ` Martin Langer
2003-02-13 15:51                   ` Justin Cormack [this message]
2003-02-14  9:34                     ` 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=1045151500.1545.33.camel@lotte \
    --to=justin@street-vision.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=finnendahl@folkwang-hochschule.de \
    --cc=martin-langer@gmx.de \
    --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