Right now the alsa-driver package isn't really being maintained in terms of bug reports. I'm whisking them over to kernel so that they get some attention. I've talked with the new ALSA herd and they seem keen to remove the duplicated maintenance and let kernel handle the kernel stuff. It looks like alsa-driver support will be slowly reduced from this point. Would you consider removing the ambiguity from the ALSA guide and recommending the in-kernel ALSA drivers for standard users?
I guess I can revert all that neutral stuff I did....I'm not too thrilled that things seem so tentative (may, maybe, looks like, etc.)...I'd hate to have to undo redo undo all the work I keep doing. ^_^
I would like to clarify my comments above. I'm not trying to force anyone to use in-kernel drivers over the alsa-driver package I'm not removing alsa-driver from portage I'm not asking that documentation for alsa-driver be removed What I am asking the documentation team to CONSIDER: Instead of providing a vague "you must make a decision between X and Y" to saying "we recommend X because [...] although you do have the option of Y which may be useful in some situations".
(In reply to comment #2) > I would like to clarify my comments above. Thanks. > What I am asking the documentation team to CONSIDER: > > Instead of providing a vague "you must make a decision between X and Y" to > saying "we recommend X because [...] although you do have the option of Y which > may be useful in some situations". FWIW, that's what I had understood :)
(In reply to comment #2) Yeah, I understood you (though it seems some folks on the ML didn't). WRT the wording, I was pretty much planning to put the guide back in its previous state before Diego opened that "alsa-driver parity" bug; that is, recommending in-kernel first and then alsa-drivers second. Keep the instructions for each, too.
Fixed in CVS.
