| sevan | BoostisBetter: thanks :) | 00:52 |
|---|---|---|
| - mtm (QUIT: Ping timeout: 246 seconds) (~textual@47.202.75.129) | 01:04 | |
| + mtm (~textual@47.202.75.129) | 01:06 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50) | 01:13 | |
| - cobra (QUIT: Ping timeout: 248 seconds) (~cobra@user/Cobra) | 01:57 | |
| + cobra (~cobra@user/Cobra) | 02:16 | |
| - paperManu (QUIT: Ping timeout: 272 seconds) (~paperManu@107.159.243.8) | 02:59 | |
| - midfavila (QUIT: *.net *.split) (midfavila@sdf.org) | 04:10 | |
| - dodo (QUIT: *.net *.split) (~dodo@user/dodo) | 04:10 | |
| - anuejn (QUIT: *.net *.split) (~quassel@46.101.193.235) | 04:10 | |
| - mesaoptimizer (QUIT: *.net *.split) (~mesaoptim@user/PapuaHardyNet) | 04:10 | |
| - BoostisBetter (QUIT: *.net *.split) (4a410829d7@irc.cheogram.com) | 04:10 | |
| - Twodisbetter (QUIT: *.net *.split) (2cc0e4ea1c@irc.cheogram.com) | 04:10 | |
| - SavagePeanut (QUIT: *.net *.split) (59eaa45ac7@irc.cheogram.com) | 04:10 | |
| - exark (QUIT: *.net *.split) (~exark@user/exark) | 04:10 | |
| - _rm (QUIT: *.net *.split) (johan@halin.me) | 04:10 | |
| - mrbcmorris_ (QUIT: *.net *.split) (~mrbcmorri@1513413-static.lxtnkya3.metronetinc.net) | 04:10 | |
| + dodo (~dodo@user/dodo) | 04:14 | |
| + _rm (johan@halin.me) | 04:19 | |
| + midfavila (midfavila@sdf.org) | 04:19 | |
| + mrbcmorris (~mrbcmorri@1513413-static.lxtnkya3.metronetinc.net) | 04:19 | |
| + exark (~exark@user/exark) | 04:20 | |
| + anuejn (~quassel@46.101.193.235) | 04:21 | |
| + jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 04:34 | |
| - mjw (QUIT: Ping timeout: 252 seconds) (~mjw@gnu.wildebeest.org) | 04:41 | |
| - erle (QUIT: Remote host closed the connection) (~erle@user/erle) | 05:35 | |
| + erle (~erle@user/erle) | 05:36 | |
| - jacobk (QUIT: Ping timeout: 276 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 06:19 | |
| + jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 06:29 | |
| + mesaoptimizer (~mesaoptim@user/PapuaHardyNet) | 08:01 | |
| - _rm (QUIT: Changing host) (johan@halin.me) | 09:50 | |
| - jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 10:04 | |
| + jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 10:04 | |
| - mtm (QUIT: Ping timeout: 276 seconds) (~textual@47.202.75.129) | 11:00 | |
| + mtm (~textual@47.202.75.129) | 11:02 | |
| * Guest9292 -> mjw | 12:05 | |
| grimmware | minute: so I've just taken a very quick look at generic forwarding of i2c over spi, and I think it's actually going to be pretty simple to implement naively (as in I have just "sketched it out" so to speak). The setup is essentially that there's the spi_command `i` followed by spi_arg1 which is the 7 bit address along with the 8th bit for r/w direction, then the rest of the buffer (which will | 12:32 |
| grimmware | need to be bigger) is the message. Pretty simple. I do think this is going to have performance implications tho because of all the back and forth, so I'm thinking that once I've got the naive implementation done it might make sense to actually be able to queue multiple messages in the same spi message, although I'm not really sure how well that will work with response packing on the way back. | 12:32 |
| grimmware | to be fair, I think if it comes with the caveat of "queue a write and a read to the same device if you like but if you do anything else don't expect good results" | 12:34 |
| hramrach | You could probably use netlink if you wanted more complex protocol. It provides functions for packing/unpacking packetized messages | 12:41 |
| hramrach | On the other hand, I do not think reading the lid switch state is performance critical | 12:41 |
| hramrach | Sure, if you wanted to use the Pocket as a nintendo nunchuck you might have a problem .. or maybe not because it would not get the bluetooth overhead. | 12:43 |
| + paperManu (~paperManu@107.159.243.8) | 12:45 | |
| grimmware | I'm talking about generic i2c forwarding over spi so that people can use devices on the qwiic header without having to maintain patches on the sysctl and lpc kernel module. There's some latency on reading the accelerometer anyway in my current setup that isn't a problem for my use case but I'm trying to produce something that's generically useful. | 12:53 |
| grimmware | I mean, it's a fair comment that if you want the easy route don't expect a high performance solution so point taken | 12:54 |
| grimmware | I definitely don't want a complex protocol, just wanna reduce the rtt. I'm no expert on this stuff though so it might be the way I've got the sensors set up | 12:55 |
| minute | grimmware: it's just a few bytes per command, right? | 13:02 |
| minute | grimmware: i think starting simple is good, and it can be optimized later for more throughput | 13:02 |
| grimmware | well technically no, it's implementation specific | 13:02 |
| + gustav28 (~gustav@c-78-82-53-73.bbcust.telenor.se) | 13:02 | |
| - mtm (QUIT: Ping timeout: 265 seconds) (~textual@47.202.75.129) | 13:03 | |
| grimmware | at any rate, the spi buffer on the rp2040 is like, 4k so there's headroom. I'll probably just choose a fairly low arbitrary size for the buffer and if people have issues they can submit a PR to grow it I guess (which probably won't happen) | 13:04 |
| grimmware | I think hramrach's fundamental point that I'm overcomplicating this is accurate | 13:05 |
| grimmware | at any rate, simple implementation will be simple :) | 13:05 |
| + mtm (~textual@47.202.75.129) | 13:06 | |
| minute | grimmware: sounds good | 13:12 |
| - MyNetAz (QUIT: Read error: Connection reset by peer) (~MyNetAz@user/MyNetAz) | 14:02 | |
| + MyNetAz (~MyNetAz@user/MyNetAz) | 14:13 | |
| Zaba | SPI can generally be much faster than I2C so I don't think performance is a concern at all, but you might want to have a look at how some existing I2C APIs operate and just copy that (for example, you probably want flags that control whether start/stop conditions get transmitted, to allow doing repeated starts etc) | 14:20 |
| josch | grimmware, mhoye: after four weeks in my shelf i popped my silicon nitride ball into my trackball cup again but nothing improved :( | 14:42 |
| grimmware | That is weird. | 14:44 |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 15:31 | |
| + BoostisBetter (4a410829d7@irc.cheogram.com) | 15:31 | |
| minute | interesting, since 6.7 we lost a line of the patch 0001-a311d-viu-fifo-lines-config.patch rendering it useless | 15:41 |
| josch | investigating... | 15:45 |
| minute | but strange that the display(s) still worked from 6.7 | 15:45 |
| minute | it probably conflicts with the older meson-g12b-bananapi-cm4-mnt-reform2/0013-meson-viu-hold-fifo-lines.patch | 15:47 |
| josch | i don't understand what made me drop that part of the patch | 15:47 |
| josch | the line that is getting patched doesn't seem to have changed between 6.6 and 6.7 | 15:48 |
| minute | no but i think it was supposed to replace meson-g12b-bananapi-cm4-mnt-reform2/0013-meson-viu-hold-fifo-lines.patch but that came back in 6.7, don't know why | 15:48 |
| minute | it was not in 6.6 | 15:48 |
| josch | interesting but it was in 6.5 o0 | 15:49 |
| josch | indeed that patch touches the same line... | 15:49 |
| josch | maybe that's why i changed this? | 15:49 |
| josch | unfortunately nothing helpful from me on irc either: https://mntre.com/reform-irc-logs/2024-03-15.log.html | 15:52 |
| josch | so.... something can be dropped from the patch stack but we don't know why? | 15:52 |
| minute | josch: the 0013 was intentionally dropped in 6.6 because it was superseded by 0001-a311d-viu-fifo-lines-config.patch | 15:52 |
| josch | ah okay | 15:52 |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 17:03 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 17:06 | |
| - vkoskiv (QUIT: Ping timeout: 244 seconds) (~vkoskiv@87-100-167-110.bb.dnainternet.fi) | 17:08 | |
| + vkoskiv (~vkoskiv@87-100-167-110.bb.dnainternet.fi) | 17:10 | |
| - glu (QUIT: Ping timeout: 272 seconds) (~glu@user/glu) | 17:33 | |
| + glu (~glu@user/glu) | 17:48 | |
| - ericsfraga (QUIT: Read error: Connection reset by peer) (~user@2a00:23cc:b43d:4b00::3ce) | 17:55 | |
| + ericsfraga (~user@2a00:23cc:b43d:4b00::3ce) | 17:58 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 18:20 | |
| + mark_ (~mjw@gnu.wildebeest.org) | 18:25 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 18:46 | |
| * mjw -> Guest509 | 18:59 | |
| - Guest509 (QUIT: Killed (copper.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c) | 18:59 | |
| * mark_ -> mjw | 18:59 | |
| + Guest509 (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c) | 18:59 | |
| + TwoDIsBooster (~booster@p5799fb79.dip0.t-ipconnect.de) | 19:01 | |
| josch | TwoDIsBooster: moin | 19:02 |
| TwoDIsBooster | josch: moin back, and danke! | 19:04 |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 19:09 | |
| - TwoDIsBooster (QUIT: Ping timeout: 248 seconds) (~booster@p5799fb79.dip0.t-ipconnect.de) | 19:10 | |
| + bkeys (~Thunderbi@45.134.140.153) | 19:18 | |
| + TwoDIsBooster (~booster@p5799fb79.dip0.t-ipconnect.de) | 19:22 | |
| - bkeys (QUIT: Ping timeout: 244 seconds) (~Thunderbi@45.134.140.153) | 19:35 | |
| minute | hmm i can't get the display v2 to work with a311d | 19:38 |
| TwoDIsBooster | minute: I do wonder how you don't pull your hair out with the constant string of things you are bravely fixing all the time. Much respect! | 19:39 |
| minute | well, this one i can't... | 19:39 |
| minute | i guess we'll need to discontinue a311d+pocket combination because we won't be able to supply working displays for this anymore | 19:39 |
| minute | i've tried around 150 times (with 150 kernel builds) | 19:40 |
| TwoDIsBooster | minute: I hear ya. I never really understood the appeal with the A331D and the IMX8Plus. The plus is a better fit in my opinion. Bummer that is off the table as well. | 19:40 |
| TwoDIsBooster | minute: still looking forward to the RK3385 in the Pocket. I'll probably just blast the whole system away and get back on a system image for it. | 19:41 |
| minute | the a311d is much faster and quite cool, so that was the appeal. otherwise the rk3588 is clearly superior | 19:41 |
| + bkeys (~Thunderbi@45.134.140.153) | 19:44 | |
| TwoDIsBooster | minute: The running cooler part is good, but I just really didn't like that you had less RAM than the IMX8 itself. | 19:44 |
| minute | yeah... | 19:45 |
| TwoDIsBooster | of course with the nvme as part of the equation you can mitigate it by just harnessing it as a swap and then it doesn't really matter much. NVME being as fast as they are. I have never been bounded on the Reform itself because of that swap. | 19:49 |
| josch | minute: 150??? OMG wow... | 19:51 |
| minute | yeah i was grinding on this for like 3 days and i just can't anymore | 19:51 |
| minute | neil who wrote this driver also doesn't know more | 19:51 |
| josch | clearly there is a point at which you should give up and spend your time on more fruitful tasks -- i don't think anybody can fault you for a situation that is out of your hands especially after spending considerable efforts into making it work anyways | 19:57 |
| - bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@45.134.140.153) | 19:57 | |
| minute | josch: yeah, i removed the a311d option from the shop now for new pocket reforms | 19:58 |
| minute | and there's only around 7-8 open orders with that combo, so we can still get some of the v1 displays for those | 19:59 |
| minute | ok, running a system image test pipeline with pocket-display-v2 reform-debian-packages branch | 20:01 |
| minute | ah, we also need this released josch https://source.mnt.re/reform/reform-tools/-/merge_requests/106/commits | 20:02 |
| - TwoDIsBooster (QUIT: Ping timeout: 252 seconds) (~booster@p5799fb79.dip0.t-ipconnect.de) | 20:03 | |
| ch | https://box86.org/2024/12/new-version-of-box64-v0-3-2-and-box86-v0-3-8/ | 20:41 |
| minute | ch: love it! | 21:21 |
| minute | box32 seems cool | 21:21 |
| + TwoDIsBooster (~booster@p5799fb79.dip0.t-ipconnect.de) | 22:03 | |
| - gustav28 (QUIT: Quit: Quit) (~gustav@c-78-82-53-73.bbcust.telenor.se) | 22:15 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 22:17 | |
| josch | minute: did you see the benchmarks, especially versus rosetta? https://box86.org/2024/12/new-version-of-box64-v0-3-2-and-box86-v0-3-8/ | 22:43 |
| josch | ah | 22:44 |
| josch | ch was faster than me XD | 22:44 |
| josch | minute: packaging up a new reform-tools release now | 22:44 |
| josch | box32 is disabled by default | 22:45 |
| josch | i asked the box64 developer whether they think it's a good idea to have it enabled in debian or not | 22:46 |
| minute | josch: cool! | 22:55 |
| josch | minute: while i'm at it, is there something to fix in reform-debian-packages regarding the lost line of 0001-a311d-viu-fifo-lines-config.patch? | 23:04 |
| - TwoDIsBooster (QUIT: Quit: leaving) (~booster@p5799fb79.dip0.t-ipconnect.de) | 23:18 | |
| + TwoDIsBooster (~booster@user/TwoDIsBooster) | 23:18 | |
| - TwoDIsBooster (QUIT: Client Quit) (~booster@user/TwoDIsBooster) | 23:18 | |
| + ktallett (~ktallett@90.196.184.225) | 23:26 | |
| - ktallett (QUIT: Ping timeout: 252 seconds) (~ktallett@90.196.184.225) | 23:32 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 23:32 | |
| + bkeys (~Thunderbi@195.sub-75-228-53.myvzw.com) | 23:33 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@195.sub-75-228-53.myvzw.com) | 23:34 | |
| + bkeys (~Thunderbi@45.134.140.153) | 23:36 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@45.134.140.153) | 23:37 | |
| + bkeys1 (~Thunderbi@45.134.140.153) | 23:37 | |
| * bkeys1 -> bkeys | 23:40 | |
| BoostisBetter | Any of you fine folks with a RK3385 able to speak on whether it uses more or less power and whether it is hotter or cooler? I'm guessing that it uses more power and runs hotter. | 23:48 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!