| - S0rin (QUIT: Ping timeout: 260 seconds) (~S0rin@user/s0rin) | 00:43 | |
| + S0rin (~S0rin@user/s0rin) | 00:46 | |
| - S0rin (QUIT: Ping timeout: 264 seconds) (~S0rin@user/s0rin) | 01:05 | |
| + S0rin (~S0rin@user/s0rin) | 01:09 | |
| - GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon) | 01:26 | |
| + GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) | 01:27 | |
| - erle (QUIT: Ping timeout: 276 seconds) (~erle@89.205.140.249) | 01:45 | |
| + erle (~erle@89.205.129.254) | 01:58 | |
| - nsc (QUIT: Ping timeout: 260 seconds) (~nicolas@51-49-142-46.pool.kielnet.net) | 03:09 | |
| + nsc (~nicolas@75-98-142-46.pool.kielnet.net) | 03:11 | |
| - skipwich (QUIT: Quit: DISCONNECT) (~skipwich@user/skipwich) | 04:03 | |
| + skipwich (~skipwich@user/skipwich) | 04:05 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50) | 04:21 | |
| - eery (QUIT: Ping timeout: 255 seconds) (~eery@172.97.103.152) | 05:46 | |
| + eery (~eery@172.97.103.152) | 05:47 | |
| - laumann__ (QUIT: Changing host) (~quassel@2a0a:e5c0:2:2:0:c8ff:fe68:bef1) | 06:08 | |
| + laumann__ (~quassel@user/laumann) | 06:08 | |
| * laumann__ -> laumann | 06:08 | |
| + mjw (~mjw@213.246.238.195) | 08:25 | |
| - mjw (QUIT: Ping timeout: 268 seconds) (~mjw@213.246.238.195) | 08:40 | |
| + mjw (mjw@151.216.131.124) | 09:38 | |
| - mjw (QUIT: Ping timeout: 255 seconds) (mjw@151.216.131.124) | 09:56 | |
| - eibachd (QUIT: Ping timeout: 256 seconds) (~eibachd@p200300dcf7353e004db9183dd5e5388e.dip0.t-ipconnect.de) | 10:19 | |
| + eibachd (~eibachd@2a01:599:314:4fcd:2618:2815:557a:ed00) | 10:19 | |
| + mjw (mjw@151.216.131.124) | 10:25 | |
| - mjw (QUIT: Ping timeout: 256 seconds) (mjw@151.216.131.124) | 10:39 | |
| + mjw (mjw@151.216.131.124) | 10:54 | |
| - mjw (QUIT: Remote host closed the connection) (mjw@151.216.131.124) | 10:58 | |
| + mjw (mjw@151.216.131.124) | 10:58 | |
| - eibachd (QUIT: Ping timeout: 256 seconds) (~eibachd@2a01:599:314:4fcd:2618:2815:557a:ed00) | 11:14 | |
| - mjw (QUIT: Ping timeout: 260 seconds) (mjw@151.216.131.124) | 11:31 | |
| + doctorhoo (~hanno@90-224-126-102-no600.tbcn.telia.com) | 11:39 | |
| + eibachd (~eibachd@p200300dcf7353e01e7255597302fbcb6.dip0.t-ipconnect.de) | 11:48 | |
| jfred | There's been some very cool info about Linux on ARM in the "FOSS on mobile devices" devroom this year at FOSDEM. I hadn't realized how far Qualcomm support had gotten | 11:50 |
|---|---|---|
| josch | jfred: i think neil armstrong gave a talk? is it worth watching the recording? | 12:02 |
| jfred | Yeah his talk just ended, I'd say it's worth watching | 12:04 |
| jfred | though I'm also a relative newbie when it comes to ARM stuff haha | 12:04 |
| - eibachd (QUIT: Ping timeout: 268 seconds) (~eibachd@p200300dcf7353e01e7255597302fbcb6.dip0.t-ipconnect.de) | 12:19 | |
| + eibachd (~eibachd@p200300dcf7353e0068492dc87d9ff554.dip0.t-ipconnect.de) | 12:20 | |
| doctorhoo | I have noted that recently the TPC does not seem to switch off correctly when issuing "sudo halt": the keyboard LEDs are still on, even after waiting for a while, and I have to use circle-0 to power off the system. This is on TPC version 2023-11-24 with an A311D and an updated debian system. Seems to be very reproducible but I am not quite sure since when.. Anyone else has seen this yet? | 12:23 |
| - ethulhu (QUIT: Excess Flood) (ethulhu@nora.ethulhu.co.uk) | 12:25 | |
| hramrach | doctorhoo: you should use 'sudo poweroff' to power off, halt is not supposed to. It did in the past, that was a bug. | 12:26 |
| hramrach | sounds like an item to put into some FAQ somewhere | 12:28 |
| + mjw (mjw@151.216.131.124) | 12:40 | |
| + ethulhu (ethulhu@nora.ethulhu.co.uk) | 12:42 | |
| - mjw (QUIT: Ping timeout: 255 seconds) (mjw@151.216.131.124) | 12:45 | |
| doctorhoo | hramrach: wow, I always thought that was a symlink to the same command -- but I just realized that systemctl to which the symlink points to actually handles the two commands differently, just as you describe. Thanks for the tip, will try that tonight! :) | 12:45 |
| digitalrayne | halt -p or systemctl poweroff should also make the right syscalls so they might be good to test as well | 12:56 |
| jfred | josch: Oh, the talk before Neil's was also pretty interesting to me: https://fosdem.org/2024/schedule/event/fosdem-2024-1716-u-boot-for-modern-qualcomm-phones/ | 13:37 |
| jfred | Apparently folks are chainloading u-boot from Android's bootloader now, and it seems to work with a universal OS image? It's got me wondering if there'd be a way to get the Reform booting from arbitrary ARM distro images | 13:42 |
| + mjw (mjw@151.216.131.124) | 14:25 | |
| Twodisbetter | so the Reform doesn't really use Gnome's backend anymore? Or it is not really present when using Sway? I can't get Fractal to open up, because it is getting a org.freedesktop.portal.Settings missing erro | 14:29 |
| Twodisbetter | so the Reform doesn't really use Gnome's backend anymore? Or it is not really present when using Sway? I can't get Fractal to open up, because it is getting a org.freedesktop.portal.Settings missing error | 14:29 |
| - mjw (QUIT: Ping timeout: 256 seconds) (mjw@151.216.131.124) | 14:30 | |
| + mjw (mjw@151.216.131.124) | 14:46 | |
| - eibachd (QUIT: Ping timeout: 264 seconds) (~eibachd@p200300dcf7353e0068492dc87d9ff554.dip0.t-ipconnect.de) | 14:55 | |
| + eibachd (~eibachd@2a01:599:314:4fcd:2618:2815:557a:ed00) | 14:55 | |
| - mjw (QUIT: Ping timeout: 260 seconds) (mjw@151.216.131.124) | 15:33 | |
| + mjw (mjw@151.216.131.124) | 15:39 | |
| + ggoes (~gregf@fsf/staff/ggoes) | 15:50 | |
| + chomwitt (~chomwitt@2a02:587:7a0b:b500:1ac0:4dff:fedb:a3f1) | 16:05 | |
| josch | Twodisbetter: what is "gnome's backend"? | 16:07 |
| josch | jfred: what is an "arbitrary arm distro image"? What would be the advantage? | 16:08 |
| - mjw (QUIT: Remote host closed the connection) (mjw@151.216.131.124) | 16:19 | |
| + mjw (mjw@151.216.131.124) | 16:19 | |
| jfred | josch: I'm thinking of booting non-device-specific installer images over USB in the same way an x86 PC would. The main advantage there is that distros can publish only one image rather than one per device, which makes it more likely especially for niche devices that you'll have a variety of options available | 16:38 |
| jfred | For example the Thinkpad X13s can apparently now boot from a generic aarch64 Debian Installer image: https://wiki.debian.org/InstallingDebianOn/Thinkpad/X13s | 16:42 |
| jfred | (It looks like there are some device-specific quirks still, but not that many) | 16:43 |
| jfred | In particular I'd like to run Guix System on my Reform, but I get the feeling the intersection of a311d Reform users + Guix users is very very small | 16:45 |
| minute | this is an interesting patch enabling egl 1.5 on a311d (panfrost) https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/26811 | 16:50 |
| minute | support for mali csf/rk3588 gpu is almost in mesa mainline https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/26358 | 17:02 |
| Twodisbetter | josch: don't know it was talking about unlocking a keychain, which I thought was already opened, because everytime I launch Brave or Thunderbird on a fresh boot it asks me to unlock it. | 17:03 |
| minute | Twodisbetter: does Seahorse (the gnome keyring gui) work for you? | 17:05 |
| - GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon) | 17:30 | |
| + GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) | 17:30 | |
| josch | jfred: even when changing out u-boot for something else, your debian-installer still has to somehow be told about the device tree to use, so you again require manual intervention to create a device-specific boot medium, no? | 17:33 |
| - chomwitt (QUIT: Remote host closed the connection) (~chomwitt@2a02:587:7a0b:b500:1ac0:4dff:fedb:a3f1) | 17:36 | |
| josch | oh the egl 1.5 thing for panfrost is to enable kicad on a311d -- nice! | 17:38 |
| - mjw (QUIT: Ping timeout: 256 seconds) (mjw@151.216.131.124) | 17:40 | |
| jfred | josch: What's interesting about the X13s case is that you seemingly only need to drop the dtb on the EFI system partition once, and then the installer image presumably reads it from there. I'm not sure if that's standardized | 17:45 |
| jfred | it doesn't look like the boot medium is device-specific | 17:46 |
| jfred | The Reform having multiple CPU modules and eventually multiple chassis might complicate things, but the CPU modules do have eMMC storage that could hold u-boot + the dtb for your current hardware configuration if they need to have separate device trees | 17:52 |
| + mjw (mjw@151.216.131.124) | 17:56 | |
| hramrach | josch: I can boot generic EFI OS image that is device agnostic on an Orange Pi Zero - after writing the u-boot that includes the device tree into the SPI NOR in the board | 18:06 |
| hramrach | that kind of experience is something that enables much more options for the user. There is separation of concerns: a distribution providing an OS image, a board vendor (in this case the user) providing the firmware required to boot the OS image | 18:07 |
| hramrach | does not work particularly well for Reform because of the downstream drivers and hardware-specific tools but getting an OS to boot should be viable in some way | 18:08 |
| - eibachd (QUIT: Read error: Connection reset by peer) (~eibachd@2a01:599:314:4fcd:2618:2815:557a:ed00) | 18:18 | |
| + eibachd (~eibachd@p200300dcf7353e00ae4cf3dff9ae9ed1.dip0.t-ipconnect.de) | 18:20 | |
| josch | hramrach, jfred: in case of the reform we had to change the dtb during some kernel version upgrades -- how does that work? I'm not very knowledgable on the topic but i think i heard that dtbs *should* survive multiple kernel versions but in practice (with the reform) some changes were required sometimes. I think identifiers changed in the kernel. | 18:23 |
| josch | and don't get me wrong: i'd love if i could just plug in a usb stick with debian installer iso dd-ed onto it and things would just work | 18:26 |
| - eibachd (QUIT: Ping timeout: 260 seconds) (~eibachd@p200300dcf7353e00ae4cf3dff9ae9ed1.dip0.t-ipconnect.de) | 18:34 | |
| + eibachd (~eibachd@p200300dcf7353e00e69a18e44d3fe466.dip0.t-ipconnect.de) | 18:35 | |
| - mjw (QUIT: Ping timeout: 240 seconds) (mjw@151.216.131.124) | 18:37 | |
| jfred | It may be one of those things that's more stable in theory than in practice. In theory device trees are supposed to even be OS-independent though from my understanding | 18:51 |
| - eibachd (QUIT: Ping timeout: 276 seconds) (~eibachd@p200300dcf7353e00e69a18e44d3fe466.dip0.t-ipconnect.de) | 18:52 | |
| + eibachd (~eibachd@2a01:599:314:4fcd:2618:2815:557a:ed00) | 18:54 | |
| - doctorhoo (QUIT: Remote host closed the connection) (~hanno@90-224-126-102-no600.tbcn.telia.com) | 19:09 | |
| Zaba | sometimes a device tree has a mistake in it and you want to update it | 19:24 |
| Zaba | sometimes you might, say, add support for a new device for which there wasn't a driver in an older kernel | 19:24 |
| Zaba | etc | 19:24 |
| + murphnj (~murph@user/murphnj) | 20:04 | |
| hramrach | josch: if identifiers change in the dtb between kernel versions it's a bug. It's understandable during delopment but should be avoided once the driver hit mainline - wihihc did not happen for some Reform drivers. | 20:58 |
| hramrach | tecnically the fact that the dtb is part of Linux is a bug as well, it's supposed to be os-independent | 21:04 |
| digitalrayne | speaking of dtbs, does anyone have the dts/dtsi files used to build the openbsd-support/imx8mq-mnt-reform2.dtb file in reform-boundary-uboot? | 21:07 |
| - erle (QUIT: Read error: Connection reset by peer) (~erle@89.205.129.254) | 21:26 | |
| + jacobk (~quassel@utdpat241106.utdallas.edu) | 21:30 | |
| + erle (~erle@89.205.129.254) | 21:43 | |
| hramrach | How do you find out what's on a specific pin of a connector? On traditional devboards you would have correspondenco to a SoC ball but with Reform there are so many levels of indirection I get lost. | 21:58 |
| - hairu (QUIT: Remote host closed the connection) (m-uotkmd@user/hairu) | 22:09 | |
| + hairu (m-uotkmd@user/hairu) | 22:13 | |
| + mjw (~mjw@213.246.238.195) | 22:27 | |
| - eibachd (QUIT: Read error: Connection reset by peer) (~eibachd@2a01:599:314:4fcd:2618:2815:557a:ed00) | 23:07 | |
| + eibachd (~eibachd@p200300dcf7353e00dc96bf172f1d280a.dip0.t-ipconnect.de) | 23:08 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@45.134.140.153) | 23:24 | |
| - eibachd (QUIT: Ping timeout: 264 seconds) (~eibachd@p200300dcf7353e00dc96bf172f1d280a.dip0.t-ipconnect.de) | 23:49 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!