NEW hdsp 9652 problems - {WAS: alsaconf -L - where's Waldo?)

NEW hdsp 9652 problems - {WAS: alsaconf -L - where's Waldo?)

[Mark Knecht]

Takashi,
   I have two sound devices (on-board Via device and an RME HDSP 9652)
but I only want to configure the RME. Currently alsaconf finds the RME,
attempts to install the drivers, and then the drivers fail saying they
cannot find the cards. I had hoped that possibly the log file would give
me more information on why. I suppose it will not if it's only for ISA
devices. (BTW - alsaconf does find this Via chip and can configure it
correctly.)

   I think that the --help for alsaconf should make this more clear.
Currently it says:

 -L|--log       logging on /tmp/alsaconf.log

No idea it only covers ISA devcies.

OK, so I start with a clean /etc/modules.conf looking like this:

alias parport_lowlevel parport_pc
alias eth0 bcm4400
alias usb-controller ehci-hcd
alias usb-controller1 usb-uhci

lspci -v shows:

<SNIP>
00:0e.0 Multimedia audio controller: Xilinx, Inc. RME Hammerfall DSP
(rev 68)
        Flags: bus master, medium devsel, latency 32, IRQ 10
        Memory at e9800000 (32-bit, non-prefetchable) [size=64K]
<SNIP>

I then run alsaconf. It shows the hdsp and the via82xx. I choose the
hdsp and get the following:

Loading driver..
Starting sound driver snd-hdsp
/lib/modules/2.4.20-1.12.ll.acpi/kernel/drivers/sound/pci/rme9652/snd-hdsp.o: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
      You may find more information in syslog or the output from dmesg
init_module: No such device
/lib/modules/2.4.20-1.12.ll.acpi/kernel/drivers/sound/pci/rme9652/snd-hdsp.o: insmod /lib/modules/2.4.20-1.12.ll.acpi/kernel/drivers/sound/pci/rme9652/snd-hdsp.o failed
/lib/modules/2.4.20-1.12.ll.acpi/kernel/drivers/sound/pci/rme9652/snd-hdsp.o: insmod snd-hdsp failed
                                                           [FAILED]
Setting default volumes..
===============================================================================

 Now ALSA is ready to use.
 For adjustment of volumes, please use alsamixer or gamix.

 Have a lot of fun!                                         │
[root@Wizard etc]#

modules.conf now looks like:

alias parport_lowlevel parport_pc
alias eth0 bcm4400
alias usb-controller ehci-hcd
alias usb-controller1 usb-uhci
# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF verion 0.9.0 ---
alias char-major-116 snd
alias snd-card-0 snd-hdsp
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
options snd major=116 cards_limit=1 device_mode=0666
options snd-hdsp index=0
# --- END: Generated by ALSACONF, do not edit.

The card is not recognized on reboot either. dmesg shows a log string of
these messages:


Hammerfall memory allocator: buffers allocated for 1 cards
RME Hammerfall-DSP: no cards found
Hammerfall memory allocator: buffers allocated for 1 cards
RME Hammerfall-DSP: no cards found


Now, this all worked fine on the previous 2.4.19-1.ll kernel from the
PlanetCCRMA site **BEFORE** I updated firmware on the HDSP 9652 for new
Win XP driver support. After updating firmware for the card, the
alsaconf program I had for the 2.4.19-1.ll kernel no longer recognized
the card at all and cannot write anything in modules.conf.

I have a new PC in my studio, using a newer kernel from the Planet not
released widely yet. (2.4.20-1.12.ll.acpi) The kernel is dated Sunday,
Feb. 2nd. The alsa RPM is dated Feb. 18th and appears to be alsa
0.9.0-45, if that makes sense. I understand some of this might be
Fernando's numbering system for the Planet.

The alsaconf that comes with this kernel recognizes the card, but the
driver doesn't load and says there's no card.

Chicken & egg problem apparently...

Thanks for any help you can provide.

Cheers,
Mark






On Fri, 2003-03-21 at 05:59, Takashi Iwai wrote:
> At 21 Mar 2003 05:50:47 -0800,
> Mark Knecht wrote:
> > 
> > Hi,
> >    The --help option says that I can get a log file from alsaconf using
> > the -L option. If I look in /tmp while alsaconf is running, I see some
> > files, but when alsaconf has finished, the files are gone...
> 
> yep, they are temporary working directories.
> 
> > 
> > [mark@Wizard mark]$ ls /tmp
> > alsaconf.3nMgvm  alsaconf.txNTFm  ksocket-mark  orbit-mark   
> > ssh-XX7Jn9me
> > alsaconf.Ef6KCm  kde-mark         mcop-mark     ssh-XX1CS1IB 
> > ssh-XXIbrHpS
> > [mark@Wizard mark]$ ls /tmp
> > kde-mark  ksocket-mark  mcop-mark  orbit-mark  ssh-XX1CS1IB 
> > ssh-XX7Jn9me  ssh-XXIbrHpS
> > [mark@Wizard mark]$
> > 
> > Is this file possibly put somewhere else? I'm trying to figure out why
> > alsaconf is complaining about this card.
> 
> /tmp/alsaconf.log is created only when the legacy cards are probed.
> it's for a deubgging purpose only...
> 
> 
> > Loading driver..
> > Starting sound driver snd-hdsp
> > /lib/modules/2.4.20-1.12.ll.acpi/kernel/drivers/sound/pci/rme9652/snd-hdsp.o: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
> >       You may find more information in syslog or the output from dmesg
> > init_module: No such device
> > /lib/modules/2.4.20-1.12.ll.acpi/kernel/drivers/sound/pci/rme9652/snd-hdsp.o: insmod /lib/modules/2.4.20-1.12.ll.acpi/kernel/drivers/sound/pci/rme9652/snd-hdsp.o failed
> > /lib/modules/2.4.20-1.12.ll.acpi/kernel/drivers/sound/pci/rme9652/snd-hdsp.o: insmod snd-hdsp failed
> 
> do you already have another sound module?
> alsaconf can configure only the first device (i.e. index=0).
> configuring more than one card is not supported yet.
> 
> 
> Takashi




-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en

Re: NEW hdsp 9652 problems - {WAS: alsaconf -L - where's Waldo?)

[Justin Cormack]

On Fri, 2003-03-21 at 16:17, Mark Knecht wrote:
> Takashi,
>    I have two sound devices (on-board Via device and an RME HDSP 9652)
> but I only want to configure the RME. Currently alsaconf finds the RME,
> attempts to install the drivers, and then the drivers fail saying they
> cannot find the cards. I had hoped that possibly the log file would give
> me more information on why. I suppose it will not if it's only for ISA
> devices. (BTW - alsaconf does find this Via chip and can configure it
> correctly.)

You need a more recent version of the driver, probably the cvs version
for this card. The configurator probably checks the PCI id but not the
revision nuumber.




-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en

Re: NEW hdsp 9652 problems - {WAS: alsaconf -L - where's Waldo?)

[Mark Knecht]

On Fri, 2003-03-21 at 08:39, Justin Cormack wrote:
> On Fri, 2003-03-21 at 16:17, Mark Knecht wrote:
> > Takashi,
> >    I have two sound devices (on-board Via device and an RME HDSP 9652)
> > but I only want to configure the RME. Currently alsaconf finds the RME,
> > attempts to install the drivers, and then the drivers fail saying they
> > cannot find the cards. I had hoped that possibly the log file would give
> > me more information on why. I suppose it will not if it's only for ISA
> > devices. (BTW - alsaconf does find this Via chip and can configure it
> > correctly.)
> 
> You need a more recent version of the driver, probably the cvs version
> for this card. The configurator probably checks the PCI id but not the
> revision nuumber.

Justin,
   Thanks for the reply. It makes sense to me, however, since I use the
PlanetCCRMA flow, and alsa is supplied as an RPM, I have no way (that I
know of) to just get a new driver, compile it and try it out. I need a
new RPM, I think.

   Thanks for the ideas!

Cheers,
Mark



-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en

Re: NEW hdsp 9652 problems - {WAS: alsaconf -L - where's Waldo?)

[Paul Davis]

>Now, this all worked fine on the previous 2.4.19-1.ll kernel from the
>PlanetCCRMA site **BEFORE** I updated firmware on the HDSP 9652 for new
>Win XP driver support. After updating firmware for the card, the
>alsaconf program I had for the 2.4.19-1.ll kernel no longer recognized
>the card at all and cannot write anything in modules.conf.

you cannot use the current ALSA driver with the new firmware.

i submitted a patch to handle the new firmware, but it has not been
put into CVS yet. meanwhile, thomas charbonnel has extended the work i
did and added some more stuff, and so we are working on a "mega-patch"
that fixes lots of issues with full H-DSP support.

once thomas gets his tasklet problems fixed (for MIDI I/O without
affecting PCM latency), we'll submit the patch again.

--p


-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en

Re: NEW hdsp 9652 problems - {WAS: alsaconf -L - where's Waldo?)

[Mark Knecht]

On Fri, 2003-03-21 at 09:45, Paul Davis wrote:
> >Now, this all worked fine on the previous 2.4.19-1.ll kernel from the
> >PlanetCCRMA site **BEFORE** I updated firmware on the HDSP 9652 for new
> >Win XP driver support. After updating firmware for the card, the
> >alsaconf program I had for the 2.4.19-1.ll kernel no longer recognized
> >the card at all and cannot write anything in modules.conf.
> 
> you cannot use the current ALSA driver with the new firmware.
> 
> i submitted a patch to handle the new firmware, but it has not been
> put into CVS yet. meanwhile, thomas charbonnel has extended the work i
> did and added some more stuff, and so we are working on a "mega-patch"
> that fixes lots of issues with full H-DSP support.
> 
> once thomas gets his tasklet problems fixed (for MIDI I/O without
> affecting PCM latency), we'll submit the patch again.
> 
> --p

Paul,
   Well, I guess thanks then for saving the rest of my vacation Friday
from being a total waste of time. I took the day off to focus on getting
this Alsa stuff going. Now I find I cannot. Too bad for me I guess. 

    I guess I will take my vacation day and rewire my studio to get this
Linux box out of the audio path completely. In a few hours I'll be back
to where I was last September, other than using Linux for email now, it
just doesn't seem like a positive 6 months.

   Not your fault. All mine for even trying to use this Linux stuff
seriously I suppose. Such disappointment.

Mark



-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en

Re: NEW hdsp 9652 problems - {WAS: alsaconf -L - where's Waldo?)

[Paul Davis]

>   Well, I guess thanks then for saving the rest of my vacation Friday
>from being a total waste of time. I took the day off to focus on getting
>this Alsa stuff going. Now I find I cannot. Too bad for me I guess. 

mark - i'm not trying to apportion blame, but i would note that if you
had not updated the firmware, this would not have happened. also, i
had hoped that takashi or jaroslav would have applied the patches
already mailed to the mailing list to CVS, but they chose not for
various reasons.

i use my H-DSP almost every day, and it works without problems for
most things (you know most of the issues). the problems you have had
are unfortunate, and i regret them, but unfortunately i do not have
write access to ALSA CVS (i'm not sure i want it), and trying to
support the very confusing situation that RME have created with the
H-DSP has been hard to do (2 PCI rev numbers, 2 incompatible ROM-based
firmware versions, 2 versions of the driver-loaded "firmware", plus
the hdsp-9652 which is "a lot" like the h-dsp but has no driver-loaded
firmware and different register access rules .... sigh).

i believe that my work and now thomas's will be available very soon,
and will make the hdsp a truly phenomenal card under linux. thomas
also has written an almost-finished version of totalmix for linux
(with bitmaps from RME), and that is really impressive to see
running. 

next time you go to upgrade the firmware on anything (your BIOS, a
SCSI adapter, a sound card), its best to be sure to ask first if it
will affect existing driver's ability to interact with the h/w.

--p




-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en

Re: NEW hdsp 9652 problems - {WAS: alsaconf -L - where's Waldo?)

[Mark Knecht]

On Fri, 2003-03-21 at 11:05, Paul Davis wrote:
> >   Well, I guess thanks then for saving the rest of my vacation Friday
> >from being a total waste of time. I took the day off to focus on getting
> >this Alsa stuff going. Now I find I cannot. Too bad for me I guess. 
> 
> mark - i'm not trying to apportion blame, but i would note that if you
> had not updated the firmware, this would not have happened. also, i
> had hoped that takashi or jaroslav would have applied the patches
> already mailed to the mailing list to CVS, but they chose not for
> various reasons.

Paul,
   I completely accept responsibility for this series of problems.
Between September and December I had an opportunity to choose what
hardware to buy. I made my choice, right or wrong. From December until
today I have waited for this hardware to really work, but it doesn't
work today. Two weeks ago, wanting to compare Linux and Windows in more
depth, and making no real progress with Linux, I pressed the button and
allowed RME's software to update my card so that I could use the best
they have to offer in Windows. It killed Linux. That was my choice, wise
or not.

   On the positive side, I must tell people that Linux kicks but. I can
run my box with Linux/Alsa/Jack, doing recording, or playing CDs, at sub
3mS latencies. I've pushed it down to 1.2mS and it's not failed, but I
think it might. The same box, running Win XP, cannot do better than 12mS
and seems to work better at 23mS. Guess which one I'd rather be using
when I use soft synths live?

   This issue is not your fault, nor your responsility to fix. You are
quite busy with two very important projects, Jack and Ardour. You don't
need to become a focal point for developing specifc drivers. I don't
expect it of you.

   I have come to understand just how much Alsa support is on a very
adhoc basis. It is not possible, I think, for any user like myself to
depend on a specific piece of hardware having support, or really knowing
when any piece of hardware will _ever_ be supported. I've also come to
find out just how much Alsa and Jack are still at the point of changing
protocols. This causes things to break. Beyond that, there is a general
sense that if developers want to change things and cause stuff to break,
then users should just put up with it, or learn to compile kernels, or
spend their time reading web sites to find solutions for problems that
didn't exist the day before. I don't think that works very well, but I
have no power to influence the outcome of you or anyone else in the
development community when you press your buttons.

   The unfortunate part of this adventure into Linuxland is that 6
months has gone by and I have barely written music. This is not what I
want, nor the way I'm willing to spend my time. 

   Will this machine ever work in the future? I don't know, but I hope
so. In the meantime I have a shiny new Athlon XP 2600+, 512MB of PC2700
DRAM, RME HDSP 9652 and a disk drive that's doing 45-50MB/Sec sitting
here doing nothing but fetchmail.

Cheers,
Mark


> 
> i use my H-DSP almost every day, and it works without problems for
> most things (you know most of the issues). the problems you have had
> are unfortunate, and i regret them, but unfortunately i do not have
> write access to ALSA CVS (i'm not sure i want it), and trying to
> support the very confusing situation that RME have created with the
> H-DSP has been hard to do (2 PCI rev numbers, 2 incompatible ROM-based
> firmware versions, 2 versions of the driver-loaded "firmware", plus
> the hdsp-9652 which is "a lot" like the h-dsp but has no driver-loaded
> firmware and different register access rules .... sigh).
> 
> i believe that my work and now thomas's will be available very soon,
> and will make the hdsp a truly phenomenal card under linux. thomas
> also has written an almost-finished version of totalmix for linux
> (with bitmaps from RME), and that is really impressive to see
> running. 
> 
> next time you go to upgrade the firmware on anything (your BIOS, a
> SCSI adapter, a sound card), its best to be sure to ask first if it
> will affect existing driver's ability to interact with the h/w.
> 
> --p
> 
> 




-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en

Re: NEW hdsp 9652 problems - {WAS: alsaconf -L - where's Waldo?)

[Jaakko Prättälä]

Lainaus Paul Davis <paul@linuxaudiosystems.com>:

> mark - i'm not trying to apportion blame, but i would note that if you
> had not updated the firmware, this would not have happened. also, i
> had hoped that takashi or jaroslav would have applied the patches
> already mailed to the mailing list to CVS, but they chose not for
> various reasons.
> 
> i use my H-DSP almost every day, and it works without problems for
> most things (you know most of the issues).
[...]
> i believe that my work and now thomas's will be available very soon,
> and will make the hdsp a truly phenomenal card under linux.

How about if you send a diff of the driver you're using with
your hdsp with firmware rev 11 against current cvs?
I've never done it but I could try and build an
first-aid rpm for Mark and others who want it.
Unless of course cvs will be up to date very soon.

I tried to patch the driver with your patch version II I found
in the archives but it was very difficult because of the extra
linefeeds the mail archive had added to the patch. I don't think
it went right. At least the first hunk I had to edit in by hand
afterwards. Whatever the reason, my multiface doesn't get
recognized. It might be my pcmcia setup or (hopefully not)
the laptop or the card itself. It would be great to have
less places to look for faults.

If you don't see making and sending a patch like this
as a good idea, could you or Thomas give a rough estimate of the
time it will take Thomas to finish his work? I'm asking
these things _not_ to hurry you up but because
I have to make plans and draw a map of the
setup I'm going to use in a theater production we start
building in a week from now. If my card doesn't work at that point,
it's ok by me, I'll just use something else.
I'd love to use the multiface of course :-)

> thomas
> also has written an almost-finished version of totalmix for linux
> (with bitmaps from RME), and that is really impressive to see
> running.

You guys simply *rule*! :-)

--
Jaakko Prättälä
Jaakko.Prattala@Helsinki.FI
http://www.cs.Helsinki.FI/Jaakko.Prattala


-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en

Re: NEW hdsp 9652 problems - {WAS: alsaconf -L - where's Waldo?)

[Michael Ulbrich]

Jaakko Prättälä wrote:
> 
> Lainaus Paul Davis <paul@linuxaudiosystems.com>:
> 
> > mark - i'm not trying to apportion blame, but i would note that if you
> > had not updated the firmware, this would not have happened. also, i
> > had hoped that takashi or jaroslav would have applied the patches
> > already mailed to the mailing list to CVS, but they chose not for
> > various reasons.
> >
> > i use my H-DSP almost every day, and it works without problems for
> > most things (you know most of the issues).
> [...]
> > i believe that my work and now thomas's will be available very soon,
> > and will make the hdsp a truly phenomenal card under linux.
> 
> How about if you send a diff of the driver you're using with
> your hdsp with firmware rev 11 against current cvs?
> I've never done it but I could try and build an
> first-aid rpm for Mark and others who want it.
> Unless of course cvs will be up to date very soon.
> 
> I tried to patch the driver with your patch version II I found
> in the archives but it was very difficult because of the extra
> linefeeds the mail archive had added to the patch. I don't think
> it went right. At least the first hunk I had to edit in by hand
> afterwards. Whatever the reason, my multiface doesn't get
> recognized. It might be my pcmcia setup or (hopefully not)
> the laptop or the card itself. It would be great to have
> less places to look for faults.

<snip>

Hi list,

yeah, I'd like to second what Jaakko asks for.

I did patch the current hdsp.c (rev. 1.26) with Paul's version II patch
and Thomas' spdifFrequency bitmasks fix. After some preliminary
corrections as described above, I'm quite sure that the patch was
applied correctly.

It was not possible to get the firmware rev 11 loaded. During boot the
test for iobox does not recognize the attached Multiface. Manually
loading the driver 'modprobe snd-hdsp' completely freezes the machine.

Preloading the firmware by booting into Windoze helps a bit in that
after loading Linux again and applying a certain combination of card
ejects and reinserts combined with modprobing the driver finally leads
to a stable (?) setup with sound output on the line out jack.

If you decide to post some beta version of the announced mega patch, I'd
like to offer some help in testing and reporting (if time permits, but
over the weekend there's always some ... ;-).

I'd love to see (hear!) the hdsp fully supported under Linux.

Greetings from Berlin ... Michael


-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en

Re: NEW hdsp 9652 problems - {WAS: alsaconf -L - where's Waldo?)

[Paul Davis]

>It was not possible to get the firmware rev 11 loaded. During boot the

which version? the initial version i sent to the list was
corrupted. the correct files look like this:

-rw-rw-r--   1 paul     paul       293050 Mar 11 09:50 /usr/local/music/src/alsa-cvs/alsa-kernel/pci/rme9652/digiface_firmware_rev11.dat
-rw-rw-r--   1 paul     paul       293051 Mar 11 09:51 /usr/local/music/src/alsa-cvs/alsa-kernel/pci/rme9652/multiface_firmware_rev11.dat


-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en

Re: NEW hdsp 9652 problems - {WAS: alsaconf -L - where's Waldo?)

[Michael Ulbrich]

Paul Davis wrote:
> 
> >It was not possible to get the firmware rev 11 loaded. During boot the
> 
> which version? the initial version i sent to the list was
> corrupted. the correct files look like this:
> 
> -rw-rw-r--   1 paul     paul       293050 Mar 11 09:50 /usr/local/music/src/alsa-cvs/alsa-kernel/pci/rme9652/digiface_firmware_rev11.dat
> -rw-rw-r--   1 paul     paul       293051 Mar 11 09:51 /usr/local/music/src/alsa-cvs/alsa-kernel/pci/rme9652/multiface_firmware_rev11.dat

Hi Paul,

yep, I got the correct versions from:

ftp://ftp.alsa-project.org/pub/tests/hdsp_rev11.tar.bz2

as Jaroslaw posted on Sun, Mar 16.

Thanks ... Michael


-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en

Re: NEW hdsp 9652 problems - {WAS: alsaconf -L - where's Waldo?)

[Jaroslav Kysela]

On Fri, 21 Mar 2003, Paul Davis wrote:

> >   Well, I guess thanks then for saving the rest of my vacation Friday
> >from being a total waste of time. I took the day off to focus on getting
> >this Alsa stuff going. Now I find I cannot. Too bad for me I guess. 
> 
> mark - i'm not trying to apportion blame, but i would note that if you
> had not updated the firmware, this would not have happened. also, i
> had hoped that takashi or jaroslav would have applied the patches
> already mailed to the mailing list to CVS, but they chose not for
> various reasons.

Paul, I think that my impression regarding these patches was that they're 
intended mostly for testing. Please, mark patches which should go to the 
CVS tree explicitly. Nobody other than the driver developer knows it.

						Jaroslav

-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs



-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en