* Filipus Klutiero <chea...@gmail.com> [2013-05-26 18:02 -0400]:
> reopen 709106
> thanks
>
> Hi Elimar,
[...]
> A bug report should only be closed when the bug has been resolved.
To be honest, which bug? I cant figure out a bug in alsa-utils.
> If you don't know how to fix a bug, simply leave the report open.
Some users don't know how to report æ bug.
> If you believe a bug cannot be fixed, the report can be tagged
> wontfix (which is very rarely appropriate).
There is no bug to fix.
>
> In this case, there are apparently 2 ways to make progress:
>
> 1. If, as your reply implies, the chip is not supported, support
> can be introduced.
As an experienced Open Source user you must know that package
mainatiners are not responsible for writíng new drivers. You must
ask alsa-devel when and in which kernel version the mentioned chip
will be supported. I can support you if you let me know which chip
type is affected. I can then give you some hints on how to ask
alsa-devel when support will be available. As it is a driver problem
we can reassign "your bug" to Debian kernel package as a whishlist
item but that won't force the development of a driver.
>
> 2. In my case, where the problematic chip is
> not the only one and another chip works fine, another chip can be
> made the default.
How to do that is briefly described in the Debian documentaion of
the alsa-base package which was pointed out 2 times in the past.
Elimar
--
We all know Linux is great... it does infinite loops in 5 seconds.
-Linus Torvalds
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
