group.of.nepali.translators team mailing list archive

[Adam Conrad <adconrad@xxxxxxx>]

** Also affects: linux-raspi2 (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Undecided
       Status: New

** Also affects: linux-raspi2 (Ubuntu Zesty)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1693250

Title:
  raspi2 config diverges from master/generic armhf

Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Xenial:
  Fix Committed
Status in linux-raspi2 source package in Yakkety:
  New
Status in linux-raspi2 source package in Zesty:
  New

Bug description:
  [SRU Justification]

  Over the course of time, the config used for the raspi2 branch,
  diverged from the config used for master/generic, and that could to
  different behaviours for kernel that should have the same (or largely
  the same) set of features/options ([1] is an example of this). What
  follows is the manual sync between the config of master/generic and
  the raspi2 branch.

  After this config the number of kernel modules increased from 3332 to
  3547, and the size of the kernel deb package increased from 35.4MB to
  37.2MB, but since many non boot essential options were factored out as
  modules, the kernel itself went down from 6.7MB to 5.7MB - ~1MB of
  code was shaved.

  1: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1683505

  [Fix]

  Manually diff the config between master/generic and raspi2, split it
  for built-in options and modules, apply the sets by making sure none
  of the boot essentials or desiderata options are turned off - finally,
  review the resulting config and in case of errors go back to square
  one.

  [Testcase]

  The resulting kernel was testes on rpi2/3 in ubuntu classic, and
  ubuntu core, in headless and video output setup, all the main
  components were excercised: network, video, usb, cpu freq, etc.

  People should probably test it on their own setup under their
  workloads and report any issue found.

  [Regressione potential]

  With such a change there's always potential for regression, but i
  tried to smoke test it on as many diverse setups as possible, and i've
  reviewed every config change, checking that we weren't changing
  anything fundamental.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1693250/+subscriptions