1 |
Ioannis Aslanidis wrote: |
2 |
> Well, to be honest, I am neither supporter nor detractor. I think that |
3 |
> it's upstream that should go and fix themselves. It's them who have |
4 |
> caused all this. |
5 |
|
6 |
The bug you linked to is a natural effect of maintaining kernel drivers |
7 |
outside of the kernel source tree. |
8 |
|
9 |
It is not the fault of the alsa-driver maintainers (either Gentoo or |
10 |
upstream people who push tarballs), since they don't control the |
11 |
in-kernel API's. |
12 |
|
13 |
It's not the kernels fault because the kernel does not claim to maintain |
14 |
a stable internal API, and it actually readily claims the opposite. This |
15 |
is not going to change. With reference to the problems an unstable |
16 |
internal API causes, kernel people will give you one answer and one |
17 |
answer only: get your code in the kernel. Problems like these simply do |
18 |
not happen there. |
19 |
|
20 |
So, in this particular case, if the alsa-driver portage package did not |
21 |
exist, the bug in question (plus a whole series of others in the same |
22 |
class) simply will not ever occur. This is a good thing. |
23 |
|
24 |
> ALSA guys do not support in-kernel stuff. |
25 |
|
26 |
ALSA guys being upstream alsa-project.org people? That's not correct, |
27 |
they are the people who put the code in the kernel. |
28 |
|
29 |
ALSA guys being downstream gentoo maintainers? That's true, since there |
30 |
is a separate team who maintain the kernel. |
31 |
|
32 |
> Kernel guys do not support alsa stuff. |
33 |
|
34 |
Upstream kernel guys? No, they support alsa, actually most of the bugs |
35 |
are handled by the alsa-project.org people who generally handle them |
36 |
very well. |
37 |
|
38 |
Downstream kernel guys (i.e. Gentoo kernel herd)? No, we support the |
39 |
sound subsystem and the ALSA drivers just like all other subsystems and |
40 |
drivers in the kernel. |
41 |
|
42 |
Thanks, |
43 |
Daniel |
44 |
-- |
45 |
gentoo-dev@g.o mailing list |