| 1 |
Steve Long wrote: |
| 2 |
> This is perfectly reasonable where it is a card with drivers in both, but |
| 3 |
> alas-drivers supports a broader range of hardware, eg the echo audio cards |
| 4 |
> (guess who has one ;) which have never been available in-kernel. |
| 5 |
|
| 6 |
These were added to the kernel as of 2.6.18. |
| 7 |
|
| 8 |
But it is still an interesting point: how does bug handling work when |
| 9 |
the drivers are actually not in the kernel at all? |
| 10 |
|
| 11 |
I think the alsa herd would be expected to handle bugs here, although |
| 12 |
I'd readily help them out as I do for other external driver maintainers. |
| 13 |
|
| 14 |
> I guess I'd like some assurance that as long as alsa-drivers supports |
| 15 |
> hardware for which there are no kernel drivers, it will at least be |
| 16 |
> available in the portage tree. |
| 17 |
|
| 18 |
Yes, I think we can promise that, provided that the drivers have some |
| 19 |
level of support upstream too. I did a quick check and it appears that |
| 20 |
right now, there are no drivers provided by alsa-driver which are not in |
| 21 |
the kernel source. |
| 22 |
|
| 23 |
> It might be worth stripping duplicate drivers out of alsa-drivers altogether |
| 24 |
> so that the two might even co-exist? Would eliminate the bug duplication in |
| 25 |
> any event. |
| 26 |
|
| 27 |
This is something that can be considered later, although I have my doubts... |
| 28 |
|
| 29 |
Daniel |
| 30 |
-- |
| 31 |
gentoo-dev@g.o mailing list |
Archives