Re: Maintaining a custom out-of-tree patched Debian kernel for specific hardware
- Date: Wed, 24 Jan 2018 03:35:14 +0530
- From: Kumar Appaiah <a.kumar@xxxxxxxxxxxxxxxxx>
- Subject: Re: Maintaining a custom out-of-tree patched Debian kernel for specific hardware
On Tue, Jan 23, 2018 at 02:08:48PM +0000, Ian Campbell wrote:
> > > Also, the patches being that small, what's stopping them from
> > > being upstreamed?
> > This is something beyond my understanding. Other distributions, such
> > as Linux Mint, Ubuntu etc. also do not possess those patches and
> > config changes. My hunch is that the Cherry Trail processors may not
> > be considered popular enough for inclusion in mainline at least
> > yet. So, we are going with this approach for now. Naturally, when
> > that's done, we'll offer a migration path to the stock Debian kernel
> > and the need for this hack will be gone.
> The patches appear to be one new ACPI match and some changes to some
> debug messages (marked with a ".optional" suffix, so probably not
> really needed). Forking the kernel packages for those trivial changes
> is _way_ overkill for a first response. If those patches had been
> submitted them upstream then I would expect them to be quickly and
> easily merged into the relevant maintainer tree and thus be elligible
> for application to the Debian kernels.
> I don't know if the kernel config changes/requirements in  are
> complete but if they are then they seem equally trivial and certainly
> worth of a discussion with the Debian kernel maintainers before
> deciding to fork.
> Even simple forks are deceptively hard to back away from so avoiding
> forking for trival reasons is usually a good default, or else you could
> easily find yourself stuck with it for an extended period of time.
> Googling around suggests that Cherry Trail is supported in mainline
> Linux today, with some last issues having been resolved in 4.11 (see
> e.g. ).
Thanks for pointing this out. Indeed, I would agree that this is the
case. However, the current timeline doesn't permit me to wait for this
process to happen, though I'll try to do it in parallel. My
expectation is that the fork will be short lived, and eventually, the
repository will provide a transition to the general Debian kernel and
be removed soon. However, I'll try my best to avoid it in the first
place, if time permits.
>  https://github.com/sundarnagarajan/kernel_build/blob/master/patches/001_rfkill_bluetooth_rtl8723bs_bt.patch
>  https://github.com/sundarnagarajan/kernel_build/blob/master/patches/002_rtl8723bs_nolinked_power_save_enter.patch.optional
>  https://github.com/sundarnagarajan/kernel_build/blob/master/config.prefs
>  https://liliputing.com/2017/03/linux-4-11-brings-improvements-intel-atom-pcs-bay-trail-cherry-trail.html
Linux: the operating system with a CLUE... Command Line User Environment.
-- seen in a posting in comp.software.testing