cinap_lenrek | https://felloff.net/usr/cinap_lenrek/9reform-catclock.png | 00:55 |
---|---|---|
- S0rin (QUIT: Ping timeout: 256 seconds) (~S0rin@user/s0rin) | 01:25 | |
minute | cinap_lenrek: wow, nice! did you get a display to work? | 01:39 |
cinap_lenrek | nope. | 01:40 |
minute | ha | 01:40 |
cinap_lenrek | this is remote, i got the ethernet driver to work :) | 01:40 |
cinap_lenrek | the display will be the very last thing to work on | 01:40 |
minute | that's cool though! | 01:41 |
cinap_lenrek | in fact, i'd rather have a screen turn on in uboot | 01:41 |
cinap_lenrek | which already has the graphics driver afaik, just not the bits to initialize the mipidsi bridge | 01:42 |
cinap_lenrek | thay'd also be more usefull in the field, when something's wrong and theres no second computer with serial at hand | 01:43 |
+ S0rin (~S0rin@user/s0rin) | 01:48 | |
- chomwitt (QUIT: Ping timeout: 248 seconds) (~chomwitt@2a02:587:dc19:d600:88e2:8613:1b70:14d7) | 01:51 | |
- mtm (QUIT: Ping timeout: 260 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 02:02 | |
- Christoph_ (QUIT: Remote host closed the connection) (~Christoph@p4fe733a7.dip0.t-ipconnect.de) | 02:13 | |
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 03:01 | |
littlebobeep | minute: Did you ever see my questions about the video output on the LS1028A ? | 03:21 |
littlebobeep | cinap_lenrek: What OS is that? | 03:21 |
cinap_lenrek | plan9 / 9front :) | 03:23 |
ex-parrot | cinap_lenrek: amazing work | 03:43 |
ex-parrot | various people have tried getting the display working in u-boot, if you sorted that it would unblock a bunch of other projects | 03:43 |
littlebobeep | ex-parrot: Which SOC is the display broken in u-boot? | 03:47 |
ex-parrot | the standard imx8 one | 03:47 |
ex-parrot | I think if we could get u-boot display working it would make getting OpenBSD going a lot quicker too | 03:51 |
sl | also appreciated | 03:52 |
cinap_lenrek | yep. | 03:52 |
cinap_lenrek | any os really. | 03:52 |
- Guest6130 (QUIT: Ping timeout: 276 seconds) (~nicolas@83-49-142-46.pool.kielnet.net) | 03:52 | |
ex-parrot | oh you're back | 03:52 |
ex-parrot | I'll stop trying to mention you in two channels at once :) | 03:52 |
littlebobeep | Hmmm I am more interested in the LS1028A because it can have 16GB of RAM on the SOM and no proprietary blobs to boot.... I am just wanting to know about the blobs required for video out | 03:53 |
+ nsc (~nicolas@85-49-142-46.pool.kielnet.net) | 03:53 | |
ex-parrot | it will be nice to have a beefier option | 03:54 |
ex-parrot | for me the imx8 is quite sufficient tho | 03:54 |
ex-parrot | esp with 9front it should be nice | 03:54 |
littlebobeep | Also I am curious about the CM4-compatible options how do these cards fit in the motherboard when it normally uses SODIMM slot for the SOM cards? | 03:54 |
* nsc -> Guest6934 | 03:54 | |
ex-parrot | there's an adapter board | 03:55 |
cinap_lenrek | fuck raspbarrypis | 03:55 |
ex-parrot | I've got a RISC-V based CM4 compatible module on order (supposedly) | 03:55 |
ex-parrot | would be fun to have a very slow RISC-V Reform | 03:55 |
cinap_lenrek | at least nxp has some decent documentation | 03:55 |
littlebobeep | ex-parrot: Can you share a link or name of the module so I can research? | 03:59 |
ex-parrot | sure, I'm not sure how much official info there is but there have been some pictures released | 03:59 |
ex-parrot | https://www.mntmn.com/media/reform_md/2022-03-03-reform-march-update.html <-- was mentioned here | 04:00 |
littlebobeep | ex-parrot: also the blog post on mntre.com has no links to the CM4 adapter board where can i look at this item? | 04:00 |
ex-parrot | https://www.mntmn.com/media/reform_v2_images/20220303-mnt-rcm4-render-with-pi.png | 04:00 |
littlebobeep | ex-parrot: that blog post only talks aboutFPGA | 04:00 |
ex-parrot | "The most immediate, least expensive solution will be in the form of the RCM4 Raspberry Pi CM4 adapter." | 04:01 |
littlebobeep | ex-parrot: You ordered an FPGA or an actual RISC-V SOC ASIC? | 04:01 |
ex-parrot | the latter, from ClockworkPi | 04:01 |
littlebobeep | ex-parrot: great, what is the model? | 04:02 |
ex-parrot | I'll find a link hang on | 04:02 |
littlebobeep | thnx | 04:02 |
littlebobeep | cinap_lenrek: Yeah I don't like RPis either but can't you just have a CM4 module that has nothing to do with RPis? | 04:03 |
ex-parrot | https://mastodon.social/@mntmn/107837330047564462 <-- slightly more info on the CM4 | 04:03 |
ex-parrot | ok sorry I was incorrect, the RISC-V module I ordered is a Pi CM3 form factor not CM4 | 04:04 |
ex-parrot | but I imagine an adapter could still be made for the Reform | 04:04 |
ex-parrot | https://www.clockworkpi.com/product-page/copy-of-clockworkpi-core-r-01 <-- this is the module I have on order | 04:04 |
littlebobeep | ex-parrot: thanks for mastodon link, I needed that pic on the left to understand... so on the left is the SODIMM board that just has the CM4 hat on top connecting with those two long plastic black contacts? | 04:06 |
ex-parrot | yep thats the idea | 04:06 |
littlebobeep | what are the two tan connectors on the far right edge of the board and the small metal connector on the bottom? | 04:06 |
ex-parrot | I'd guess the bottom-most one is USB, not sure about the other two | 04:06 |
ex-parrot | the imx8 board has the wider flat flex cable as well | 04:07 |
ex-parrot | I forget what is carried over it | 04:07 |
littlebobeep | ex-parrot: that clockworkpi is not SM4 or SM3, it does SODIMM.... does this plug into Reform motherboard and magically work? | 04:07 |
+ mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 04:08 | |
ex-parrot | no, I thought it was a Pi3 Compute Module SIMM | 04:08 |
ex-parrot | I could be wrong, I just kind of bought it on a whim | 04:08 |
ex-parrot | the Pi compute module changed from the SIMM form factor to the board to board interconnects between 3 and 4 | 04:08 |
littlebobeep | Ahhh well what can you plug it into when it arrives? The only thing I ever used SODIMM for was DDR RAM modules :P | 04:09 |
ex-parrot | the Reform's motherboard slot is VERY DEFINITELY not CM3 compatible | 04:09 |
ex-parrot | so no, I won't be plugging it in there :P | 04:09 |
ex-parrot | the interface is specific to the reform | 04:09 |
ex-parrot | so to use the RISC-V board with the reform you'd need a similar adapter to the CM4 one | 04:09 |
littlebobeep | Ohhhh so you are saying CM3 is basically physically compatible to SODIMM (but maybe not logically)? | 04:09 |
ex-parrot | right it's the same connector but totally different signals / pinout | 04:10 |
ex-parrot | would likely damage the reform and the module if plugged in to the reform without an adapter board | 04:10 |
littlebobeep | Weird why choose SODIMM connector then that is confusing | 04:11 |
ex-parrot | well you could ask why did the Pi Foundation use the SODIMM connector for the CM3 when it was already used for RAM... | 04:12 |
ex-parrot | it's just a suitable connector that is available, has enough pins and can carry the appropriate signals | 04:13 |
littlebobeep | Hmmm someone on the forum says the MNT Reform only lasts ~3 hours on full battery charge? Is this true? | 05:54 |
ex-parrot | that sounds wrong | 06:28 |
ex-parrot | depends what you're using it for but I would say I get more like 5-6 hours | 06:29 |
ex-parrot | not amazing but not terrible | 06:29 |
littlebobeep | Ahhh okay just random forum user | 06:29 |
ex-parrot | you could probably kill it in 3 if you were compiling constanrtly and had the screen on high brightness etc | 06:29 |
ex-parrot | there are higher capacity batteries available now too, not sure how much that affects the runtime | 06:30 |
littlebobeep | Ohhh how many mAh are the cells compared to the original/default ones? | 06:32 |
josch_ | littlebobeep: 2000 mAh https://www.eremit.de/p/18650-3-2v-2-000mah-lifepo4 | 06:34 |
* josch_ -> josch | 06:34 | |
ex-parrot | ^ those were the ones | 06:34 |
ex-parrot | there was talk of changing the batteries included with theu nit but I don't know if that has happened | 06:34 |
josch | Boostisbetter said that those last about an hour longer than the default ones. | 06:41 |
littlebobeep | josch: thanks! | 06:45 |
ex-parrot | i switched from the included cells that I busted to some generic-ish ones from aliexpress | 06:46 |
ex-parrot | and the battery life seems about the same | 06:46 |
ex-parrot | which is good | 06:46 |
littlebobeep | ex-parrot: Were thye aliexpress ones different mAh? | 06:47 |
ex-parrot | no, advertised as 1800maH | 06:47 |
ex-parrot | mAh | 06:47 |
littlebobeep | ex-parrot: What is the motivation for buying a whole new set of batteries in this case? | 06:47 |
ex-parrot | I overdischarged my original ones, and while they kept working for a while one cell suddenly died | 06:48 |
ex-parrot | so I decided it was safer to replace them all with a new set | 06:48 |
ex-parrot | the overdischarge problem is improved with newer LPC firmware, and should be entirely fixed with the next revision battery boards | 06:48 |
littlebobeep | LPC is a family of 32-bit microcontroller integrated circuits by NXP Semiconductors (formerly Philips Semiconductors | 06:54 |
ex-parrot | josch: am I right in thinking the Debian experimental 5.17 firmware is almost ready to run on the Reform minus the LCD? | 06:54 |
littlebobeep | Had to look that up.... is a LPC armhf chip used for PMU? | 06:54 |
josch | ex-parrot: you mean the Debian 5.17 kernel? | 06:55 |
ex-parrot | littlebobeep: the "platform controller" if you like in the Reform is an NXP LPC chip | 06:55 |
ex-parrot | josch: err yeah, why did I write firmware | 06:55 |
littlebobeep | ex-parrot: What Debian firmware? | 06:55 |
ex-parrot | s/firmware/kernel/ | 06:55 |
littlebobeep | Ah okay sorry I can look this up, I guess the platform controller is used for PMU | 06:55 |
ex-parrot | yes | 06:55 |
josch | ex-parrot: well, it will run and give you a serial console (according to vagrantc) but it will not enable the internal display yet because those patches haven't been accepted upstream | 06:56 |
ex-parrot | right. that's what I was thinking, thanks for confirming | 06:56 |
josch | we can carry unreleased patches in Debian but for that those patches should at least be accepted in some upstream branch | 06:56 |
ex-parrot | yeah makes sense | 06:56 |
ex-parrot | I imagine it's only a matter of time before they get accepted upstream anyway | 06:56 |
ex-parrot | I thnk we never got there with the Novena but that platform was kind of a dead end anyway :( | 06:57 |
ex-parrot | littlebobeep: the keyboard and the LPC both are involved in the power management | 06:57 |
ex-parrot | I think on the Reform specifically it's an lpc11u24 | 06:58 |
littlebobeep | https://source.mnt.re/reform/reform/-/tree/master/reform2-lpc-fw | 06:58 |
ex-parrot | that's the one | 06:58 |
littlebobeep | am searching yesss | 06:58 |
ex-parrot | currently the higher level power management is done through the keyboard though | 06:58 |
littlebobeep | I do not understand what a keyboard has to do with a PMU | 06:59 |
ex-parrot | e.g. the keyboard tells the LPC to power on the machine | 07:00 |
josch | ex-parrot: well, currently lynxeye (lucas stach) is working on upstreaming those but but explained to me how their free time is limited right now, so upstreaming might still take a while | 07:00 |
ex-parrot | because the power button is on the keyboard | 07:00 |
ex-parrot | josch: understandable | 07:00 |
ex-parrot | and I believe currently the "power off" is done through a HID command sent to the keyboard, which then instructs the LPC to cut power | 07:01 |
ex-parrot | but I could be remembering that incorrectly. I still want to do a "proper" kernel driver for that when I have time / inclination | 07:01 |
littlebobeep | josch: if this is about display during bootloader is this patches bering merged into upstream u-boot you are talking about? | 07:01 |
josch | littlebobeep: no, i was talking about the kernel | 07:01 |
ex-parrot | littlebobeep: the u-boot display patches are a separate issue, we just straight up don't have that working yet | 07:01 |
littlebobeep | ex-parrot: really, just because the power button is there, the majority of the PMU logic is on the keybaord controller?? | 07:01 |
josch | we also don't have upstream u-boot working | 07:01 |
ex-parrot | littlebobeep: I believe at the moment the i2c comms between the SoM and the LPC are not working | 07:02 |
ex-parrot | tho there is prob more subtlety to this than I am aware of | 07:02 |
ex-parrot | the keyboard has to be informed anyway so it can display the power state etc, so it's not entirely unreasonable to route power control requests through there at the moment | 07:03 |
littlebobeep | ex-parrot: what effects does broken i2c have? | 07:03 |
ex-parrot | sorry it was SPI | 07:04 |
ex-parrot | so the LPC is connected to the SoM over SPI, but it's not currently working | 07:04 |
ex-parrot | which means that queries / commands to / from the LPC have to go through the keyboard | 07:04 |
ex-parrot | (someone correct me if I'm wrong here, it was months and months ago we discussed this last) | 07:04 |
littlebobeep | The LPC is on the motherboard right? So the SoM can speak SPI via the SODIMM connector to the LPC? | 07:04 |
ex-parrot | right, except it's not currently working | 07:05 |
ex-parrot | for reasons unknown | 07:05 |
ex-parrot | it would be nice to get it fixed at some point for tighter integration of power stuff | 07:05 |
littlebobeep | Hmmmm well the code is there, so.... | 07:05 |
ex-parrot | the problem was that no SPI activity was observable across the bus | 07:05 |
ex-parrot | so it's not clear if it's a software issue, configuration issue, electrical issue I think | 07:06 |
ex-parrot | I'm not sure anyone has put a lot of time in to it yet | 07:06 |
littlebobeep | I see | 07:06 |
littlebobeep | Well I am not familiar with SoMs or SODIMM being used for this | 07:07 |
ex-parrot | just forget about the connector being a SODIMM, the connector isn't important :) | 07:07 |
littlebobeep | ahhh well | 07:07 |
littlebobeep | maybe | 07:07 |
ex-parrot | SoM is the System-on-Module used, it's sort of a step up from an SoC in terms of what peripherals etc are included in the "package" | 07:08 |
littlebobeep | ex-parrot: what else besides LPDDR4 chips? | 07:38 |
- sl (QUIT: Remote host closed the connection) (~sl@beastie.sdf.org) | 07:48 | |
- littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 08:23 | |
+ chomwitt (~chomwitt@2a02:587:dc19:d600:24ae:3716:1088:6d4d) | 08:29 | |
- sigrid (QUIT: Ping timeout: 248 seconds) (~ftrvxmtrx@ftrv.se) | 09:41 | |
+ sigrid (~ftrvxmtrx@ftrv.se) | 09:48 | |
+ mtm- (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 11:54 | |
- mtm (QUIT: Ping timeout: 276 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 11:56 | |
- Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149-210-16-210.mobile.nym.cosmote.net) | 12:17 | |
+ Ar|stote|is (~linx@149-210-16-210.mobile.nym.cosmote.net) | 12:17 | |
+ littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 12:40 | |
littlebobeep | . | 12:40 |
+ MajorBiscuit (~MajorBisc@c-001-007-017.client.tudelft.eduvpn.nl) | 13:00 | |
+ Christoph_ (~Christoph@p4fe73fde.dip0.t-ipconnect.de) | 13:31 | |
- littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 13:58 | |
- mtm- (QUIT: Ping timeout: 260 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 14:02 | |
- S0rin (QUIT: Ping timeout: 276 seconds) (~S0rin@user/s0rin) | 14:36 | |
+ mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 16:08 | |
+ S0rin (~S0rin@user/s0rin) | 16:27 | |
- S0rin (QUIT: Ping timeout: 248 seconds) (~S0rin@user/s0rin) | 16:51 | |
+ sl (~sl@beastie.sdf.org) | 16:55 | |
- Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149-210-16-210.mobile.nym.cosmote.net) | 18:08 | |
+ Ar|stote|is (~linx@149-210-16-210.mobile.nym.cosmote.net) | 18:15 | |
- mtm (QUIT: Ping timeout: 248 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 18:21 | |
CliffyA | in the system image v3 thread, bnys mentions "GPU glitches/freezes can occasionally happen (due to a mesa/new kernel issue)." | 18:27 |
CliffyA | i was wondering if that's what's causing the flicker in Xwayland or if that's a different issue and i should create a report? | 18:28 |
CliffyA | A quick repro description for anyone wondering: Start reform-windowmanager. Then start xterm. Type some text in then start moving the mouse around over the screen. The new text will flicker like there are two video buffers and only one was updated. | 18:32 |
CliffyA | And I forgot to note that this does not happen with system image v2. I'll check back tomorrow thanks! | 18:42 |
cinap_lenrek | https://git.9front.org/plan9front/plan9front/fff070f2cbb01b7c0879e9dcb13ee4e3ed2497f0/commit.html | 19:04 |
+ mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 20:27 | |
+ S0rin (~S0rin@user/s0rin) | 20:48 | |
- MajorBiscuit (QUIT: Quit: WeeChat 3.4) (~MajorBisc@c-001-007-017.client.tudelft.eduvpn.nl) | 22:08 | |
cinap_lenrek | aaaand we have multiprocessor up! | 22:27 |
cinap_lenrek | https://felloff.net/usr/cinap_lenrek/9reform-multicore.png | 22:30 |
cinap_lenrek | https://felloff.net/usr/cinap_lenrek/9reform-multicore2.png | 22:31 |
cinap_lenrek | time for the beers :) | 22:33 |
minute | cinap_lenrek: cheers!! | 22:33 |
+ littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 22:42 | |
minute | cinap_lenrek: git.9front.org appears to be down now, though | 22:45 |
cinap_lenrek | haha | 22:45 |
cinap_lenrek | ok | 22:45 |
cinap_lenrek | aand its back | 22:54 |
cinap_lenrek | ran out of processes :) | 22:55 |
minute | nice | 22:59 |
- Christoph_ (QUIT: Remote host closed the connection) (~Christoph@p4fe73fde.dip0.t-ipconnect.de) | 23:59 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!