Re: [gentoo-dev] Re: New ALSA maintainers
Am Donnerstag, 29. März 2007 03:50 schrieb Steve Long: Daniel Drake wrote: I have suggested that herd support for the kernelspace side (alsa-driver) be slowly reduced, by redirecting users who file bugs against it to reproduce with the in-kernel drivers, and then let kernel handle the bug resolution. This will remove duplicated maintenance efforts. This is perfectly reasonable where it is a card with drivers in both, but alas-drivers supports a broader range of hardware, eg the echo audio cards (guess who has one ;) which have never been available in-kernel. Like those in sound/pci/echoaudio/ ? Which have been in there since the commit labelled: 2006-06-28 Giuliano Pochini [ALSA] Add echoaudio sound drivers I guess this is either point c) or point f) of Daniel's list. But he should probably add a bullet point g) Hasn't looked yet. Danny -- Danny van Dyk [EMAIL PROTECTED] Gentoo/AMD64 Project, Gentoo Scientific Project -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Re: New ALSA maintainers
Steve Long wrote: This is perfectly reasonable where it is a card with drivers in both, but alas-drivers supports a broader range of hardware, eg the echo audio cards (guess who has one ;) which have never been available in-kernel. These were added to the kernel as of 2.6.18. But it is still an interesting point: how does bug handling work when the drivers are actually not in the kernel at all? I think the alsa herd would be expected to handle bugs here, although I'd readily help them out as I do for other external driver maintainers. I guess I'd like some assurance that as long as alsa-drivers supports hardware for which there are no kernel drivers, it will at least be available in the portage tree. Yes, I think we can promise that, provided that the drivers have some level of support upstream too. I did a quick check and it appears that right now, there are no drivers provided by alsa-driver which are not in the kernel source. It might be worth stripping duplicate drivers out of alsa-drivers altogether so that the two might even co-exist? Would eliminate the bug duplication in any event. This is something that can be considered later, although I have my doubts... Daniel -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Re: New ALSA maintainers
Daniel Drake wrote: I have suggested that herd support for the kernelspace side (alsa-driver) be slowly reduced, by redirecting users who file bugs against it to reproduce with the in-kernel drivers, and then let kernel handle the bug resolution. This will remove duplicated maintenance efforts. This is perfectly reasonable where it is a card with drivers in both, but alas-drivers supports a broader range of hardware, eg the echo audio cards (guess who has one ;) which have never been available in-kernel. This will also mean no more stabling of -rc releases (and probably fewer of those in portage at all). Sounds fine. alsa-driver won't be going away altogether, as it is still needed for 2.4 users (but we won't support them forever) and I think it may include a couple of drivers which aren't yet in the kernel tree. So the bug resolution for cards with drivers _not_ in the kernel will be to pass them upstream if they are reproducible? I guess I'd like some assurance that as long as alsa-drivers supports hardware for which there are no kernel drivers, it will at least be available in the portage tree. It might be worth stripping duplicate drivers out of alsa-drivers altogether so that the two might even co-exist? Would eliminate the bug duplication in any event. From what I've read in this thread, the only area of difficulty would be new chipsets, but then there'd be more developer time with less bugs, and that seems to be the way things are going anyhow. Thanks for all your hard work on the kernel. -- gentoo-dev@gentoo.org mailing list
