• 2 Posts
  • 61 Comments
Joined 11 months ago
cake
Cake day: July 20th, 2023

help-circle
rss
  • I can’t honestly recall or put my finger on it what I did wrong.

    Choose fedora because it used my laptop subwoofer and wasn’t a rolling release. I remember each time (x2) reading about how to update the distro and each time my system was completely borked. I went to debian, read upon alsa, made my subwoofer work with a homegrown script and never looked back.

    To this day I am wondering if people recommending redhat are trolls or paid.




  • Graphics driver for sc8280xp are already a thing. There are more issues in convenience daily driving linux, currently. From the top of my head:

    • firmware update path
    • dtb update/loading path
    • no virtualization
    • no universal dock compability
    • missing HDMI/DP features

    I suspect that these issues are common between their ARM chips and will be addressed for both chips almost simultaneously. But I have no real idea on kernel development. And their documentation is only shared with linaro so one can only guess.






  • It is bearable but feature complete. Every month linaro and the community add functionality. The most recent things include a custom power-domain mapper implementation and apparently camera support.

    If you are running wayland you can simply install any os and its working oob.

    The laptops weight and heat production is awesome. Very practical. Also the body is exceptional sturdy and worth mentioning (even in comparsion to a T14, e.g.).

    But:

    • external monitors are not detected at boot
    • no hibernation
    • battery time is very depended on the task. It ranges from 4 to 13 hours.
    • no virtualization support, so one is stuck with tiny code generator runtime when using kvm
    • audio is pretty quiet, so depending on the environment an external source is required.

    I followed almost all patches on the lkml. It appears to me that the upcoming chip can benefit from the sc8280xp hugely. It sufficies for my use cases but I promised myself a little better, yet.







  • I think he’s coming from here:

    As an developer you create a solution to a problem from yours. You release it under a FOSS license.

    Your job is done - You shared your work. The community may find your project useful and builds upon it. Their interest is to get their changes upstream. You have no obligation to help with onboarding and implementing features for others.

    So if they are requesting a merge you may reject it since it does not meet your standards. Maybe you have to make your stance clear and create a CONTRIBUTION alongside your code.

    With this mindset you wouldn’t hang out on a non-indexable platform.

    Your project mostlikely is requesting explicit participation. Maybe this is the point in between you guys.

    Now go on with the discussion :)