Am 22.08.2014 17:40, schrieb Jeff Mahoney:
On 8/22/14, 11:09 AM, 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
Imagine, I have the usb device with the uncommon
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?
USB devices aren't what I had in mind since they can be plugged in
anywhere. I mean uncommon in terms of using an SoC or the like. Like
SPI, GPIO drivers, LCDs, Power Management ICs.
Or, we can make the choice to disable these drivers for the -default
kernel and use something else to enable those. I'd be ok with either
Could you clarify: Are you talking about x86 only or all architectures?
In the ARM world where there's little in common, save for USB devices,
such a change would make our life of building JeOS images harder.
Building more ARM flavors would be even worse, as building Kernel:HEAD
with two flavors plus obs-build is already a challenge in build time.
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org