| + robin (~robin@user/terpri) | 00:08 | |
| - robin (QUIT: Remote host closed the connection) (~robin@user/terpri) | 00:38 | |
| - Christoph_ (QUIT: Remote host closed the connection) (~Christoph@p54bf60ca.dip0.t-ipconnect.de) | 00:40 | |
| - Gooberpatrol66 (QUIT: Quit: Leaving) (~Gooberpat@user/gooberpatrol66) | 01:01 | |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 01:06 | |
| - kitty3 (QUIT: Ping timeout: 256 seconds) (~kitty@096-039-147-043.res.spectrum.com) | 01:06 | |
| smoothduck | @minute I just received DIY #208 (sans trackball) from CS on Tuesday. | 01:09 |
|---|---|---|
| - chartreuse (QUIT: Read error: Connection reset by peer) (~chartreus@node-1w7jr9ql2247t9azo97sze19g.ipv6.telus.net) | 01:15 | |
| smoothduck | oh @ signs, you can tell I'm stuck in slack all day | 01:15 |
| minute | smoothduck: huh, interesting that they don't send it together with the TB | 01:23 |
| smoothduck | They said they were out of stock on trackballs, but should be getting more in soon | 01:24 |
| minute | curious because we sent them 100 and less than that were sold according to my numbers | 01:26 |
| minute | we'll send them 20 more soon | 01:26 |
| + chartreuse (~chartreus@node-1w7jr9ql2247t9azo97sze19g.ipv6.telus.net) | 01:27 | |
| smoothduck | They did ask my permission to send without. | 01:28 |
| smoothduck | No worries, It is totally usable in the interim. | 01:29 |
| smoothduck | They probably have them, I can only imagine what process they have to make their way through before they are ready to ship on their end. hah | 01:31 |
| minute | ha! cool, thanks for the info. always interesting what happens to the machines we build | 01:34 |
| + mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 01:35 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 01:44 | |
| swivel | anyone have experience with this chipset in linux? particularly the GPU https://en.t-firefly.com/product/industry/itx3588j | 01:59 |
| - mtm (QUIT: Ping timeout: 272 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 02:03 | |
| - chomwitt (QUIT: Ping timeout: 272 seconds) (~chomwitt@2a02:587:dc0d:4a00:5f16:ac72:f625:5e79) | 02:23 | |
| - GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon) | 03:33 | |
| + GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) | 03:34 | |
| chartreuse | grubman, yes those were the pins I was referring to , they're ground or 3.3v pins on the m.2 socket (depending on which way is up | 03:36 |
| chartreuse | vkoskiv, and yes the earth ground isn't required to be on the output side of the PSU, IIRC it's using it more for EMI reasons inside the PSU. | 03:37 |
| + mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 04:09 | |
| - Gooberpatrol66 (QUIT: Quit: Leaving) (~Gooberpat@user/gooberpatrol66) | 04:15 | |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 04:28 | |
| - Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149-210-4-98.mobile.nym.cosmote.net) | 05:57 | |
| + Ar|stote|is (~linx@149-210-4-98.mobile.nym.cosmote.net) | 05:57 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20) | 06:08 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 06:29 | |
| - GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon) | 10:16 | |
| + GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) | 10:17 | |
| - chartreuse (QUIT: Remote host closed the connection) (~chartreus@node-1w7jr9ql2247t9azo97sze19g.ipv6.telus.net) | 10:56 | |
| + Christoph_ (~Christoph@p54bf607c.dip0.t-ipconnect.de) | 10:59 | |
| + chomwitt (~chomwitt@2a02:587:dc0d:4a00:5774:9752:fb9b:46d2) | 11:19 | |
| - GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon) | 13:12 | |
| + GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) | 13:12 | |
| + robin (~robin@user/terpri) | 13:22 | |
| - mjw (QUIT: Killed (NickServ (GHOST command used by wielaard!~mjw_@2001:1c06:2488:1400:9e5c:8eff:fe8f:a440))) (~mark@gnu.wildebeest.org) | 13:43 | |
| * wielaard -> mjw | 13:44 | |
| + mark_ (~mark@gnu.wildebeest.org) | 13:44 | |
| + dustfinger (~user@d75-159-228-218.abhsia.telus.net) | 13:46 | |
| minute | we still have some trouble with ls1028a, if someone knows someone with experience on this stuff: https://community.nxp.com/t5/Layerscape/How-to-debug-dysfunctional-SERDES-PCIe-SATA-SGMII-on-LS1028A/m-p/1490299#M10894 | 13:50 |
| - mtm (QUIT: Ping timeout: 244 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 14:02 | |
| - GNUmoon (QUIT: Ping timeout: 268 seconds) (~GNUmoon@gateway/tor-sasl/gnumoon) | 14:18 | |
| + GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) | 14:21 | |
| - GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon) | 14:30 | |
| + GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) | 14:30 | |
| cinap_lenrek | minute: i had once worked with a 10gig phy troubleshooting xfi issues | 14:32 |
| cinap_lenrek | minute: there where status registers on the phy where i could sample the status, and detect that the highspeed connection wasnt stable | 14:33 |
| cinap_lenrek | tho i guess you already know that | 14:33 |
| cinap_lenrek | pcie controller also might have a status register for the link negotiation state machine you can sample | 14:34 |
| cinap_lenrek | but really, you better ask nxp | 14:34 |
| cinap_lenrek | good luck | 14:35 |
| minute | yeah, there ought to be LTSSM status somewhere | 14:37 |
| minute | just weird that not even sgmii works | 14:37 |
| minute | never had problems with that on any chip | 14:37 |
| cinap_lenrek | we had on another nxp system issue with that, and it turned out to be that the clock was in spread spectrum mode | 14:38 |
| cinap_lenrek | and that didnt work | 14:38 |
| cinap_lenrek | all this is guessing tho | 14:38 |
| minute | huh! | 14:38 |
| minute | i did measure the refclks with an osc and they looked pretty stable 100mhzy though | 14:38 |
| minute | but idk if spread spectrum is visible like that | 14:39 |
| cinap_lenrek | its probably not your issue even | 14:47 |
| + MajorBiscuit (~MajorBisc@2a02-a461-129d-1-6d4c-38a4-18b7-4b48.fixed6.kpn.net) | 14:59 | |
| + S0rin_ (~S0rin@user/s0rin) | 15:00 | |
| - S0rin (QUIT: Ping timeout: 256 seconds) (~S0rin@user/s0rin) | 15:02 | |
| - S0rin_ (QUIT: Ping timeout: 240 seconds) (~S0rin@user/s0rin) | 15:06 | |
| + S0rin_ (~S0rin@user/s0rin) | 15:20 | |
| - MajorBiscuit (QUIT: Quit: WeeChat 3.5) (~MajorBisc@2a02-a461-129d-1-6d4c-38a4-18b7-4b48.fixed6.kpn.net) | 15:58 | |
| + mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 16:08 | |
| - dustfinger (QUIT: Quit: rebooting) (~user@d75-159-228-218.abhsia.telus.net) | 16:24 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:40) | 17:01 | |
| smoothduck | Does the current OLED battery monitor refresh at all on its own? | 18:11 |
| Boostisbetter | no, it is a one time poll, and you have to circle + b it again to get an update | 18:11 |
| minute | there's a PR for this but untested/unmerged | 19:03 |
| Boostisbetter | 💪️ automatic repolling could be nice, but I actually like the way it works now. It is more of a snapshot of your batteries at that exact moment. | 19:33 |
| josch | Boostisbetter: what would speak against updating that snapshot 10 seconds later after you've read it? | 19:35 |
| Boostisbetter | I guess for me, that would be fine. I tend to exit the OLED screens as soon as I see the information presented. I don't want to "waste" power keeping it lit. | 19:36 |
| josch | I agree. My idea was to let it auto-update only if plugged in. This makes sense for me because I want to watch how it charges. | 19:36 |
| Boostisbetter | Also for me, the power draw for the device is pretty linear. Which is to say, if I see the batteries at a certain percentage, I know the rough amount of time I still have with them. | 19:37 |
| josch | And when plugged in it would not waste battery power. | 19:37 |
| Boostisbetter | josch: yeah that sounds great. I'd love that. | 19:37 |
| Boostisbetter | but at the same time, I'm good with it as it is | 19:37 |
| kfx | logging the SPI data would surely be a better way to monitor charging behavior than staring at it? | 19:46 |
| josch | kfx: "logging the spi" doesn't work when my reform is off | 20:08 |
| cinap_lenrek | surely, one could modify the firmware to keep updating the battery status continuously | 20:42 |
| cinap_lenrek | and even make it blink or something once you'r low on battery | 20:42 |
| cinap_lenrek | i have a modern thinkpad for a work laptop and one needs to run stupid software that shows the battery status | 20:43 |
| cinap_lenrek | i rather have that done independently of the main cpu... | 20:44 |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:40) | 20:54 | |
| josch | thinkpads had a feature in software that they'd stop charging at 80% (by default that functionality was off but it was configurable in their windows software) -- do lifepo4 batteries also last longer when one doesn't charge them fully but only up to 80%? | 20:56 |
| minute | josch: i don't think lifepo batteries have this kind of effect | 21:15 |
| josch | okay, cool! :) | 21:15 |
| minute | reform had a blinky battery status thing initially | 21:15 |
| minute | but it was also showing when the status was ???% (bug) and people got annoyed | 21:16 |
| minute | i changed the feature but then because of a new bug it did not actually alert at all anymore... | 21:16 |
| minute | and they lived happily ever after. | 21:17 |
| klardotsh | there's still degradation at deeper DoD (assuming you're draining 100% to 0%), and no lithium batteries are completely happy at 100% for long periods (storage, etc), but LiFePO4 seems more forgiving than, say, traditional laptop batteries | 21:17 |
| klardotsh | eg https://community.victronenergy.com/questions/10779/official-depth-of-discharge-recommendations-for-li.html | 21:17 |
| minute | bottom line: the blink alert feature exists, it just never shows | 21:17 |
| minute | one would need to fix the bug | 21:18 |
| kfx | I prefer it to just shut off mysteriously. Less stress. | 21:23 |
| minute | hehe | 21:24 |
| - GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon) | 21:29 | |
| - mjw (QUIT: Killed (NickServ (GHOST command used by mark_!~mark@gnu.wildebeest.org))) (~mjw_@2001:1c06:2488:1400:9e5c:8eff:fe8f:a440) | 21:29 | |
| * mark_ -> mjw | 21:29 | |
| + wielaard (~mjw_@2001:1c06:2488:1400:9e5c:8eff:fe8f:a440) | 21:30 | |
| + GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) | 21:35 | |
| - GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon) | 21:45 | |
| + GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) | 21:45 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20) | 21:47 | |
| + chartreuse (~chartreus@node-1w7jr9ql2247t9azo97sze19g.ipv6.telus.net) | 21:55 | |
| minute | would you people be interested in an imx8mplus upgrade module for reform, with 1.8ghz and 8gb ram, and integrated wifi+bt module? | 22:12 |
| minute | (the wifi probably needs firmware) | 22:13 |
| minute | the cores are still cortex-a53 but it's a 14nm instead of 28nm chip and thus higher clock freq and less heat | 22:13 |
| technomancy | if it had a gpu that worked with xorg i'd be all over it =) | 22:14 |
| minute | well, the current gpu works with xorg, just someone needs to fix xorg | 22:15 |
| cinap_lenrek | minute: i wonder, is it alot of work on the hw side? | 22:15 |
| minute | the GPU is GC7000UL | 22:16 |
| minute | cinap_lenrek: well it will be the default for pocket reform so i will do it in any case | 22:16 |
| minute | and pocket reform takes the same kind of modules as reform | 22:16 |
| cinap_lenrek | minute: oh | 22:16 |
| minute | there is only one drawback, which is that there's only one PCIe (gen3) controller, not two. but you don't need the wifi card anymore, as there would be wifi on the module. | 22:17 |
| minute | there's also a third display output but i'm not sure if it can really drive 3 displays in parallel | 22:18 |
| minute | there's also a hifi dsp, an npu and a cortex-m7... don't know what those are useful for | 22:19 |
| cinap_lenrek | so its really about designing a new som for both pocket and classic reform? | 22:24 |
| minute | no, the som exists (again by boundary), but it's a board-to-board connector thing similar to cm4 | 22:26 |
| minute | so i'll make a card for it that plugs into our existing SODIMM slot | 22:27 |
| cinap_lenrek | OH | 22:27 |
| minute | https://boundarydevices.com/product/nitrogen8m-plus-som/ | 22:27 |
| klardotsh | minute: WiFi being on-board and now not replaceable over PCIe would be a huge downgrade for me sadly. when the motherboard is back, the wifi card I have to put in mine is an AX200NGW, a WiFi 6 + BT5 chip, and I can later upgrade to new wifi specs if I ever want. onboard SOM WiFi precludes that :\ | 22:27 |
| klardotsh | the 8gb RAM is absolutely **clutch** though (I've been eagerly awaiting that 16GB SOM you're working with NLNet on, despite its fewer CPU cores, for example) | 22:28 |
| minute | klardotsh: alright! yeah, there are pros and cons. | 22:28 |
| minute | yeah, the ls1028a is still in debugging phase | 22:28 |
| minute | i mean, there will always be more upgrades. | 22:28 |
| minute | there's also an almost-working rpi cm4 adapter. the cm4 has other pros and cons again... quad a72 but videocore, no usb3, one pcie... | 22:29 |
| klardotsh | since I've been looking at ITX boards with this chip, I'll throw one more on your radar, as if you needed a longer todo list ;) RK3588 looks bananas. not quite at the level of M1/8cxg3, but looks very performant, and up to 32GB RAM for those of us stuck working on, well... rails apps to pay the bills :) (and for browser tabs...) | 22:30 |
| klardotsh | minute: oh yeah. all things in tradeoff for sure. didn't know CM4 had no USB3, that surprises me a bit. is that CM4 pinout problem or just the RPi CM4 (meaning some other CM4-pinout-compat board (I see some starting to exist) could add it)? | 22:31 |
| minute | klardotsh: i have 2 rk3588 modules on my desk | 22:31 |
| minute | that's a thing for later | 22:31 |
| klardotsh | !!!!!!! eek! | 22:31 |
| minute | will need a new motherboard though | 22:31 |
| minute | so nothing to plug into the old motherbaord | 22:31 |
| minute | klardotsh: on the regular rpi4, the usb3 is realized by a controller chip that uses pcie | 22:32 |
| minute | klardotsh: on the cm4, pcie is exposed | 22:32 |
| klardotsh | ohhhhhh neat. TIL1 | 22:37 |
| klardotsh | minute: as for the new motherboard, curious, **how** different is rk3588? like how bad of a mobo overhaul would it be? | 22:37 |
| minute | klardotsh: the module i want to use has the same connector like MXM, 314 pins instead of 200 | 22:38 |
| minute | also i want to offer some usb-c connectors and possibly split the motherboard into som carrier + charger board, like on the pocket | 22:39 |
| minute | so, some design i'm doing now for pocket will probably go back into a next-gen reform motherboard | 22:39 |
| minute | there might then be different carrier board variants to accomodate a variety of soms | 22:40 |
| Boostisbetter | minute: any idea when beta pocket's might be available for testing? not rushing. Quality takes time. | 22:40 |
| minute | Boostisbetter: it really depends on how well things go in the next two weeks when the first pcbs are coming in | 22:41 |
| minute | also we're doing a lot of work on the case design atm | 22:41 |
| Boostisbetter | minute: I'm super excited about it all. I would test the heck out of the thing. | 22:43 |
| Boostisbetter | 👍️ | 22:43 |
| minute | oh yeah, we're excited as well | 22:43 |
| klardotsh | minute: ohhhhh you're doing the charging daughterboard thing I alluded to?! exciting! yeah, that plus USB-C (even if just PD spec, but the DP alternate mode would also be great if it's ever possible) would be an instant mobo upgrade purchase for me | 23:03 |
| minute | good to know, thanks for the feedback! | 23:04 |
| klardotsh | I don't have the time or (currently?) KiCAD, SMD, etc. skills to do what Jacqueline did and swap the charge port on the one in your shop, so for now I have two of the USB-PD to barrel jack adapters the forum linked | 23:05 |
| klardotsh | the ability to single-port dock a Reform (Power + Display) would basically obviate the need for me to ever have a second laptop machine laying around once the rooted-with-Linux chromebook I keep around finally dies | 23:06 |
| minute | interesting! | 23:06 |
| - Christoph_ (QUIT: Remote host closed the connection) (~Christoph@p54bf607c.dip0.t-ipconnect.de) | 23:36 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!