** Description changed:

  [Impact]
  
- Upstream has good support for qcom410 and 820 chipsets, so enable the
- Dragonboard410c and db820c out of generic
+ Upstream / Linux 5.3 has good support for Qcom Snapdragon 410 and 820
+ SOCs, so enable the Dragonboard410c and Dragonboard820c out of it,
+ isolating all the changes in a 'snapdragon' generic flavour.
  
  [Fix]
  
- Apply the packaging and config changes in the below pull request
+ Apply the packaging and config changes in the pull request.
  
  [How to test]
  
- Boot the resulting kernel on the db410c / db820c boards
+ Boot the resulting kernel on the db410c / db820c boards.
  
  [Regression potential]
  
- No code changes are involved, it's all config work and everything has
- been isolated into its own 'snapdragon' flavour
+ No code changes are involved: it's all config work and everything has
+ been isolated into its own 'snapdragon' flavour.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1846704

Title:
  Enable the Dragonboards out of eoan/generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

  Upstream / Linux 5.3 has good support for Qcom Snapdragon 410 and 820
  SOCs, so enable the Dragonboard410c and Dragonboard820c out of it,
  isolating all the changes in a 'snapdragon' generic flavour.

  [Fix]

  Apply the packaging and config changes in the pull request.

  [How to test]

  Boot the resulting kernel on the db410c / db820c boards.

  [Regression potential]

  No code changes are involved: it's all config work and everything has
  been isolated into its own 'snapdragon' flavour.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to