[Kernel/Drive] 内核包为何要放在non-free里?
Tofloor
poster avatar
Red54
deepin
2022-03-21 20:39
Author

Screenshot_select-area_20220321123556.png
你们的打包相当混乱,内核元包linux-image-deepin-amd64放在main里,这是应该的,但是内核元包依赖的具体内核包linux-image-5.10.101-amd64-desktop却放在non-free里,这是为什么?一个内核包竟然放在non-free里,一个main包竟然要依赖non-free包,你们就是这样来打包的?

Reply Favorite View the author
All Replies
Breeze
deepin
2022-03-21 22:28
#1

有理

Reply View the author
Rubbish
deepin
2022-03-21 22:42
#2

non-free应该是因为内核集成了安卓(uengine)的binder和ashmem

Reply View the author
SamLukeYes
deepin
2022-03-22 02:38
#3
Rubbish

non-free应该是因为内核集成了安卓(uengine)的binder和ashmem

Debian 内核没启用 ashmem 和 binder 吗confused

Reply View the author
Rubbish
deepin
2022-03-22 19:03
#4
SamLukeYes

Debian 内核没启用 ashmem 和 binder 吗confused

没,这俩就是non-free

Reply View the author
SamLukeYes
deepin
2022-03-22 23:58
#5
Rubbish

没,这俩就是non-free

我看到的情况是 Debian 在 4.17 的时候就启用了 ashmem 和 binder:
https://github.com/linux-surface/linux-surface/issues/144
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901492
难道 Debian 自己就是把内核放在 non-free 里的confused

Reply View the author
Red54
deepin
2022-03-23 05:44
#6
Rubbish

没,这俩就是non-free

https://github.com/torvalds/linux/blob/master/drivers/staging/android/ashmem.c

https://github.com/torvalds/linux/blob/master/drivers/android/binder.c

ashmem和binder都是GPL的,不存在是non-free这说法。

Reply View the author
Rubbish
deepin
2022-03-24 07:56
#7
Red54

https://github.com/torvalds/linux/blob/master/drivers/staging/android/ashmem.c

https://github.com/torvalds/linux/blob/master/drivers/android/binder.c

ashmem和binder都是GPL的,不存在是non-free这说法。

欸搞错了,我以为之前需要自己编译是因为non-freetail

Reply View the author