Bug#928642: release-notes: please mention improved support in buster for Rockchip RK3328 and RK3399 devices

[Andrei POPESCU]

Package: release-notes
Severity: wishlist
Tags: moreinfo
X-Debbugs-CC: debian-***@lists.debian.org


Hello,

According to http://opensource.rock-chips.com/wiki_Status_Matrix
mainline should have reasonable support for RK3328 and RK3399 as of
4.14.

Considering RK3399 is already used in some interesting devices
(ROCKPro64, Firefly-RK3399, Samsung Chromebook Plus) and more to come
(Pinebook Pro) it would probably be a good idea to say a few words about
it in the release notes (what's new chapter).

As I don't currently own any such devices input from Someone Else (tm)
is needed.

Thanks,
Andrei

[Paul Gevers]

Hi Andrei,

Post by Andrei POPESCU
According to http://opensource.rock-chips.com/wiki_Status_Matrix
mainline should have reasonable support for RK3328 and RK3399 as of
4.14.
Considering RK3399 is already used in some interesting devices
(ROCKPro64, Firefly-RK3399, Samsung Chromebook Plus) and more to come
(Pinebook Pro) it would probably be a good idea to say a few words about
it in the release notes (what's new chapter).
As I don't currently own any such devices input from Someone Else (tm)
is needed.

Probably worth mentioning indeed, but I am not that Someone Else.

Paul

[Debian Bug Tracking System]

Your message dated Sun, 18 Dec 2022 22:14:37 +0100
with message-id <0a0b2c77-521e-69fd-915b-***@debian.org>
and subject line Re: Bug#928642: release-notes: please mention improved support in buster for Rockchip RK3328 and RK3399 devices
has caused the Debian Bug report #928642,
regarding release-notes: please mention improved support in buster for Rockchip RK3328 and RK3399 devices
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)