Sebastian Krzyszkowiak @dos@librem.one

@kornel Pity it doesn't seem to exist - though it looks like the trailer has managed to go somewhat viral, so in the end its development may actually start one day ;)

@aanee What I'd recommend is to get an already working device and to find a component with available datasheet and missing functionality in its kernel driver. There should be plenty of such bite-sized low hanging fruits out there, which will let you gain enough experience to work on and debug more complex stuff with devices that aren't ported yet.

I don't know how a "porting for dummies" guide could even look like, this kind of stuff tends to be highly device-specific.

@filiplachert @jon It's clearly an attempt to make the lives of people who messed with them harder. There's not much more to it.

@mntmn In fact, there should be no need to copy anything; seems like all you'd need is exposed in libphosh, so you may be able to do it with just a few lines of glue code.

@mntmn I guess you could cut PhoshBackground out of phosh and end up with just that.

"The Art and Secrets of #Karambola" - a digital 92-page #artbook heavily illustrated with yet unpublished sketches, drawings, paintings and locations from the game - is now out!

Agata (@holypangolin) reveals her thoughts on the curious fruity characters’ personalities and backstories, as well as some difficult decisions she had to make during the design process.

Buy on #Steam or @itchio:

https://store.steampowered.com/app/3172920/The_Art_and_Secrets_of_Karambola/

https://holypangolin.itch.io/the-art-and-secrets-of-karambola

#gamedev #indiedev #art #mastoart #indiegame #itchio

@whitequark @hailey ah gotcha

@whitequark @hailey I had been there many years ago, confused about why shouldn't I keep debian/ dir upstream even though I was the one packaging my own thing in Debian. Only after getting more familiar with how things work I realized it makes perfect sense given the Debian's processes. I don't think it's fair to characterize it as "hostile".

It may still be valuable to maintain debian/ upstream though, but distinct from the distro packaging (usually for CI or for self-compiled dev builds).

hiya! #shotonlibrem5

@AmpBenzScientist @lupyuen To be fair, PocketCHIP had a 480x272 display and the same GPU as the PinePhone (with fewer cores though). Even Neo Freerunner was fast in QVGA mode.

@gnarf @fasterthanlime @sdr_pod > a 768kHz DAC

DAC for audiophile dolphins?? 🤔 🐬

@thejackimonster @linmob @Blort @martijnbraam It's certainly optimized for quality rather than performance ;)

For the phone use-case, I see it as a stop-gap. I used darktable because it was there; that's what I used for manual RAW handling so I knew how to make it output something nice. I bet you could write a much more performant and suited-for-mobile processing pipeline with good enough results, but that's a bit more involved than some UIs and glues 😜

@thejackimonster @linmob @Blort @martijnbraam darktable uses OpenCL when available.

@linmob @Blort @martijnbraam BTW. Doing what Glowup does directly from Millipixels/Megapixels is literally a one-liner which you can put there without even recompiling anything. You'll just have to deal with >30 seconds of 100% CPU usage and plenty of RAM being eaten each time you shoot a photo, which personally I don't find to be a very appealing idea 😂

@linmob @Blort @martijnbraam Martijn also mentioned remote postprocessing some time ago, which makes sense too - my laptop does in 4 seconds what my phone does in 30.

The hard parts are there, what's left is some simple glue. I'm trying to encourage people to do this kind of nice entry-level tasks. Writing glowup.py took me just a few hours of fiddling with libadwaita in total, which would be better done by someone who'd like to learn this stuff and actually take it somewhere further.