| - oomono (QUIT: Quit: Connection closed for inactivity) (uid328183@id-328183.tinside.irccloud.com) | 00:12 | |
| - bgs (QUIT: Remote host closed the connection) (~bgs@212-85-160-171.dynamic.telemach.net) | 00:32 | |
| - mtm (QUIT: Ping timeout: 252 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 01:03 | |
| - S0rin (QUIT: Ping timeout: 272 seconds) (~S0rin@user/s0rin) | 01:05 | |
| + S0rin (~S0rin@user/s0rin) | 01:11 | |
| - S0rin (QUIT: Ping timeout: 260 seconds) (~S0rin@user/s0rin) | 01:16 | |
| + S0rin (~S0rin@user/s0rin) | 01:17 | |
| - S0rin (QUIT: Ping timeout: 252 seconds) (~S0rin@user/s0rin) | 02:41 | |
| + S0rin (~S0rin@user/s0rin) | 02:48 | |
| + reform28684 (~bnys@c-73-239-119-220.hsd1.wa.comcast.net) | 02:54 | |
| * reform28684 -> bnys | 02:54 | |
| bnys | sorry to leave you in suspense josch I figured out reform-migrate and reform-boot-config...the syntax in the description was throwing me off with the [--emmc] stuff. I thought i had to do [--sd] but it seems like sd is the default when doing nvme boot | 02:55 |
|---|---|---|
| bnys | now a couple of weird notes: wifi network info doesn't seem to persist between boots, and I have to type my password in each time (no autoconnect) | 02:56 |
| bnys | region seems to reset as well...I'm back on CET instead of pacific time | 02:56 |
| bnys | also I'm seeing weird artifacts on boot, like black and white stripes at the stop of the screen that flicker before it starts reading out boot info | 02:56 |
| bnys | this is a fresh v3 system, updated, now booting on nvme (running on sd it didn't show the artifacts), and now with the new battery boards | 02:57 |
| bnys | oh the network issue is whether I use sway or gnome | 02:57 |
| bnys | whenever we redo the handbook for pocket reform it might be worth revisiting the migration documentation. seems like the script is pretty robust now, and we should tell users to use that instead of manually migrating | 02:59 |
| bnys | oh and the waybar config should have the battery module code too now that the lpc stuff is shipping as default. i had to reenter that to get waybar to show the battery info | 03:01 |
| + mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 03:09 | |
| - bnys (QUIT: Ping timeout: 246 seconds) (~bnys@c-73-239-119-220.hsd1.wa.comcast.net) | 03:27 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:40) | 03:44 | |
| - ajr (QUIT: Quit: WeeChat 3.7) (~ajr@user/ajr) | 05:08 | |
| + ajr (~ajr@user/ajr) | 06:08 | |
| - ajr (QUIT: Quit: WeeChat 3.7) (~ajr@user/ajr) | 07:14 | |
| josch | i guess i should pm bnys on the forum instead XD | 08:23 |
| josch | did anybody try building ffmpeg 5.2.1 with the v4l2 request and drmprime patches? | 08:23 |
| + bgs (~bgs@212-85-160-171.dynamic.telemach.net) | 09:03 | |
| Boostisbetter | bnys, wait we can get battery data now? Yet more reason to get on sys v3. | 09:46 |
| josch | Boostisbetter: yes, you have to upgrade your firmware though | 09:49 |
| josch | i wanted to do that during the holidays myself (now that i have to open up my reform to put in the new battery boards) but i forgot that to do so i need a second computer XD | 09:54 |
| josch | time to buy a second reform? ;) | 09:54 |
| josch | Boostisbetter: before you scrap your system, could you run the latest version of the reform-check utilty on it? | 10:30 |
| Boostisbetter | Yeah you bet. I'm not in a rush to blank it. I want to know what I am doing first. | 10:37 |
| - XYZ (QUIT: Ping timeout: 268 seconds) (~XYZ@89.24.40.5) | 10:38 | |
| - mlarkin (QUIT: Ping timeout: 255 seconds) (~mlarkin@047-036-074-225.res.spectrum.com) | 10:48 | |
| + mlarkin (~mlarkin@047-036-074-225.res.spectrum.com) | 10:50 | |
| josch | the good news: hardware decoding works with ffmpeg 5.2.1 -- completely smooth h264 playback without utilizing the cpu | 11:00 |
| josch | the bad news: the video is all tinged red... | 11:00 |
| josch | maybe something is wrong with the colorspace? but i really have no clue about this sort of stuff -- i can just apply patches i find and rebuild packages :D | 11:39 |
| josch | and h265 isn't working at all: "hevc: v4l2_request_queue_decode: request 38 timeout" | 12:10 |
| + XYZ (~XYZ@89-24-40-5.nat.epc.tmcz.cz) | 12:51 | |
| - XYZ (QUIT: Read error: Connection reset by peer) (~XYZ@89-24-40-5.nat.epc.tmcz.cz) | 12:56 | |
| + XYZ (~XYZ@89-24-40-5.nat.epc.tmcz.cz) | 12:57 | |
| - mtm (QUIT: Ping timeout: 268 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 13:04 | |
| + kremlin (~kremlin@ip124.ip-167-114-218.net) | 14:33 | |
| Boostisbetter | do anyone of you know a person or company that you can pay or commission to design enclosures or cases? | 14:39 |
| Boostisbetter | I'm working on making a UMPC using a Framework mainboard, but my fusion skills are just not up to snuff for what I need. | 14:40 |
| Boostisbetter | Hoping I can commission it or something. | 14:40 |
| + mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 15:11 | |
| - mjw (QUIT: Killed (NickServ (GHOST command used by wielaard!~mjw_@2001:1c06:2488:1400:9e5c:8eff:fe8f:a440))) (~mark@gnu.wildebeest.org) | 16:36 | |
| * wielaard -> mjw | 16:36 | |
| + mark_ (~mark@gnu.wildebeest.org) | 16:37 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:40) | 17:39 | |
| nsc | Is there somewhere a kind of MNT Reform firmware overview page, where the latest released versions of all firmware are listed? | 18:16 |
| minute | nsc: not yet unfortunately | 18:26 |
| minute | bonfire: this is another thing we could use some help in setting up | 18:26 |
| vkoskiv | The firmware versioning scheme could use some work | 18:26 |
| vkoskiv | Some kind of semantic versioning maybe? And git hashes for development versions? | 18:26 |
| minute | yeah, any versioning+tags really | 18:27 |
| nsc | ACTION is happy that not finding such a page was not caused by himself (alone) | 18:29 |
| vkoskiv | Colored kbd backlight on the pocket reform looks so fun :D | 18:32 |
| vkoskiv | Are the keys individually addressable? | 18:33 |
| vkoskiv | Looking at that one tweet, it seems so | 18:34 |
| vagrantc | minute: versioning would be simpler if the various firmwares were each in their own repository ... it would certainly make packaging for debian easier :) | 18:40 |
| minute | vagrantc: sorry, i really really prefer a monorepo for this... the reason is that they should always be kept compatible with each other | 18:46 |
| minute | but yeah, i will need to think more about it | 18:46 |
| minute | josch: i was thinking, could this be merged already and then reform-check be improved later? https://source.mnt.re/reform/reform-tools/-/merge_requests/30 | 18:46 |
| minute | josch: because there are a bunch of other goodies that we'd like to already have in any case, right? | 18:47 |
| - mjw (QUIT: Killed (NickServ (GHOST command used by mark_!~mark@gnu.wildebeest.org))) (~mjw_@2001:1c06:2488:1400:9e5c:8eff:fe8f:a440) | 18:59 | |
| * mark_ -> mjw | 18:59 | |
| + wielaard (~mjw_@2001:1c06:2488:1400:9e5c:8eff:fe8f:a440) | 19:00 | |
| vagrantc | minute: hrm. one repo for each firmware? | 19:07 |
| vagrantc | minute: er, rather ... one repo for allt he firmware? | 19:07 |
| + ajr (~ajr@user/ajr) | 19:21 | |
| - bgs (QUIT: Remote host closed the connection) (~bgs@212-85-160-171.dynamic.telemach.net) | 19:36 | |
| josch | minute: yes, i think reform-check can be release even though it might be incomplete. It certainly works and doesn't damage user's systems. The improvements from Boostisbetter running the current version on their reform can be added later. | 19:39 |
| josch | minute: i understand that you want to keep the firmware compatible with each other but can you not also do that by having the mono repo contain git subprojects? | 19:40 |
| josch | minute: this would have the best of both worlds: the firmware would each be in its own repo which would make tagging, releasing and packaging easier | 19:40 |
| josch | minute: at the same time, the big mono-repo integrating them as git subprojects would make sure that always the versions compatible with each other are included and no version that is too new for the other | 19:41 |
| josch | in that situation, those who use the git subprojects without the mono-repo are on their own but those who do will always get those versions that you deem compatible | 20:07 |
| vagrantc | as long as the subprojects can be built independently still | 20:16 |
| vagrantc | alternately, git subtrees instead of git subprojects might also work ... slightly different tradeoffs | 20:16 |
| vagrantc | the hacky firmware packages for debian i built actually end up just removing all the non-firmware bits ... but that will be a pain to maintain in the long-term | 20:18 |
| vagrantc | e.g. git conflicts all the time, etc. | 20:18 |
| sigrid | I'm gonna say from my own experience: whenever inter-dependencies occur, handling those in a git project with either submodules or subtrees becomes a huge pain in the ass | 20:18 |
| josch | vagrantc: this is also partly due to limitations in the Debian tooling. It would make things much simpler if there was an easy way to extract subdirectories of a git tree and ignore the rest. | 20:24 |
| josch | minute: if you end up keeping both firmwares in the same monorepo, does that mean that there will be one version covering *both* at the same time? Or will the firmwares be versioned and tagged independently? | 20:25 |
| vagrantc | i recall at the Seattle meetup one of the plan9 folks also really would like to see the firmware split out, fwiw | 20:44 |
| vagrantc | so not *just* a debian tooling issue :) | 20:45 |
| sigrid | was it smj? | 21:01 |
| sigrid | it's not like the firmware can be built on plan 9 anyway | 21:02 |
| sigrid | having it versioned, built and uploaded somewhere for easy updating is def would be appreciated though | 21:02 |
| vagrantc | sigrid: whoever it was was into sdf.org | 21:05 |
| sigrid | then it's smj :) | 21:06 |
| - mjw (QUIT: Quit: Leaving) (~mark@gnu.wildebeest.org) | 21:43 | |
| + mjw (~mark@gnu.wildebeest.org) | 21:49 | |
| + oomono (uid328183@id-328183.tinside.irccloud.com) | 22:25 | |
| - S0rin (QUIT: Ping timeout: 272 seconds) (~S0rin@user/s0rin) | 22:25 | |
| + S0rin (~S0rin@user/s0rin) | 22:37 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!