At Fri, 22 Aug 2014 19:09:37 +0400, Matwey V. Kornilov wrote:
22.08.2014 17:33, Jeff Mahoney пишет:
Hi all -
I'm doing the integration work for 3.17-rc1 and, as usual, there are a ton of drivers that are typically only used for embedded devices. Generally, I'd prefer to just disable them, but there are always a few people who want to run openSUSE on things like tiny Atoms.
Do we want to consider moving uncommon drivers into something like kernel-default-uncommon and save disk space on most every other system? Of course, then there's also the concept of kernel-default-base again, where it would probably contain typical file systems (xfs/ext4/btrfs) and drivers for devices most commonly offered by qemu-kvm. I understand it doesn't cover cases like device assignment, but those are more advanced use cases in which the full kernel-default package would be used.
The problem I'm looking to solve is "what would work well for several major use cases?" I'd define those as typical desktop/server/notebook hardware and KVM instances without device assignment. (Xen is a different conversation since dom0 and domU have different requirements WRT drivers.) The fallback for not fitting into one of the nice boxes is just installing another package which uses as much disk space as the old kernel package used to, so it's not a huge inconvenience.
OTOH, having multiple kernel sub-packages has been somewhat of a PITA WRT updates and dependencies, so I thought I'd solicit opinions.
-Jeff
Imagine, I have the usb device with the uncommon driver from staging/ moved far away to the separate package. Then I plug it and found that there is no driver. How should I know that it exists in the separate package?
In theory, kernel-uncommon can give supplements list like KMP, so that zypper can pick it up automatically. Takashi -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org