Sebastian Krzyszkowiak @dos@librem.one

@awai @janvlug @okias @purism A good chunk of those should be trivially upstreamable, though personally I'm holding up with doing it until we're back on current trees, as that will make testing much easier.

Some of this stuff will still need a solid cleanup before going upstream though. There's also a handful of commits that add things that have been explicitly rejected by upstream, such as cpuidle, so I don't expect to ever be able to get to less than 10 commits or so.

@awai @janvlug @okias @purism FYI just did a quick clean up to get some better numbers - dropping patches that are later reverted, squashing downstream driver commits, dropping debug/obsolete/devkit/packaging/CI stuff, things backported from upstream etc. - but not very thoroughly.

Ended up with 174 commits.

133 files changed, 33472 insertions(+), 1541 deletions(-)

When ignoring Cadence and Redpine drivers:

68 files changed, 5908 insertions(+), 369 deletions(-)

https://source.puri.sm/sebastian.krzyszkowiak/linux-next/-/commits/6.6.118-rebase

@okias @awai @janvlug @purism It's progressing again, but there's lots of catch up to play until it's current again 😭

@awai @janvlug @okias @purism Commit count is misleading - there are 86 commits just for the big cam sensor driver, which is rather small and these all would be squashed down into a single one if upstreamed; and further 20 commits on the Redpine driver are later nullified by importing its newer version.

Also, you only need a handful of commits to have a kernel that boots into something usable: https://source.puri.sm/martin.kepplinger/linux-next/-/commits/6.12.11/librem5_light

@grzgrz ED74, aka Pesa Bydgostia, aka Edyta. Mamy też Aliny, aka turbokible, aka EN57AL 😜

@pecet Może i Linux, ale gdzież tam GNU??