thanks

[Florian Schlichting <Florian.Schlichting@gmx.de>]

[-- Attachment #1: Type: text/plain, Size: 1783 bytes --]

On Wed, Mar 15, 2006 at 04:42:39PM +0100, Takashi Iwai wrote:
> 
> Thanks for confirmation.  I applied the patches to CVS.

thanks to you for your patience, quick and helpful replies, and ongoing
work. And to Lee for providing initial pointers. This was the first time
that I looked into kernel code deeply enough to actually understand
something and make some modifications. And it was surprisingly easy!
(well, it took some time and persistance, but C doesn't read that
different from Java, and putting lots of printk's in suspicious places
really isn't that difficult)

I was thinking that I might have done this much earlier, had I known
that developers lacked access to hardware and thus couldn't possibly do
much debugging. I've been checking the ALSA website since at least 2002,
saw that it's a known issue, that there are bug reports filed to which
people answer, and went away again thinking that there are more
knowledgeable and able people working on it, and it's just a matter of
time and a hard problem...

Thus I was thinking whether it might help in such cases to post a note
on the driver page that people with access to a certain type of hardware
are needed to do debugging? And perhaps have a page somewhere explaining
how easy it is to start doing this, for people with some background in
programming languages?

I realize now that there are probably similar bugs everywhere, and it's
just a matter of going for one - but I've been thinking for years that
the kernel is such a monster that I'll never understand how it works,
anyway (and I still don't, but I found out that it doesn't necessarily
matter as long as one understands just the tiny part that's concerned)

Anyway, it's been a joy working with you on this!

Florian

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]