cinap_lenrek | bluerise: http://felloff.net/usr/cinap_lenrek/lcd.c | 00:03 |
---|---|---|
cinap_lenrek | bluerise: its more self contained (sans the i2c and clock stuff) | 00:04 |
cinap_lenrek | bluerise: in this driver, the dsi configuration is static. only dpi and the bridge need the mode info. | 00:10 |
cinap_lenrek | bluerise: well, dpi, bridge and the lcdif of course | 00:10 |
cinap_lenrek | so shouldnt be too hard to roll this out | 00:10 |
cinap_lenrek | and just have a big run of register writes hammering away | 00:11 |
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20) | 00:24 | |
vkoskiv | I didn't get anything out of the LPC serial line when doing screen /dev/ttymxc2 57600 | 00:26 |
vkoskiv | The blender build that comes with sysv3 seems to be missing some facilities. It doesn't have Cycles, and the settings window is missing a lot of options. | 00:28 |
vkoskiv | Like the input pane doesn't contain anything | 00:28 |
vkoskiv | So I can't enable 'emulate numpad', for instance | 00:29 |
minute | vkoskiv: serial is 115200 baud | 00:41 |
minute | ah sorry | 00:41 |
minute | i overlooked "LPC" | 00:41 |
vkoskiv | Are the docs accepting merge requests? | 00:41 |
vkoskiv | Same for firmware repos | 00:41 |
minute | sure | 00:41 |
minute | go ahead! | 00:42 |
vkoskiv | I'm interested in working on both. Probably more firmware, but small doc fixes as well :D | 00:42 |
minute | nice | 00:42 |
minute | cinap_lenrek: that's a plan9 driver, right? i wonder how hard it'd be to hack this into u-boot also | 00:43 |
vkoskiv | I also just hit circle+1 while messing with the thing to see messages :D | 00:44 |
vkoskiv | I'll see about adding a 'sure?' prompt to those | 00:44 |
minute | oop | 00:46 |
minute | i think circle 1 shouldn't do anything if power is already on. that would fix this | 00:46 |
vkoskiv | Yeah. Probably better. | 00:46 |
vkoskiv | Looks like it just reset the thing. | 00:46 |
minute | yep | 00:46 |
minute | it does a quick off, on | 00:46 |
vkoskiv | Still wondering what these nvme QID timeouts are about | 00:46 |
vkoskiv | I found this today: https://www.funkyspacemonkey.com/mpv-youtube-dl-stop-wasting-resources | 00:56 |
vkoskiv | I learned that you can config profiles for mpv | 00:56 |
vkoskiv | So now I can just do mpv --profile=1080p <url> and it does what I want | 00:56 |
minute | neat | 01:08 |
vkoskiv | Is the chromium shipping with v3 of the | 01:14 |
vkoskiv | 'ungoogled' variant?* | 01:14 |
vkoskiv | I'm still getting used to the en-us layout :D Keep hitting return when I meant to type ' | 01:15 |
vkoskiv | Overall I really like this, much nicer for programming than the se/fi layout I've used for ages. | 01:15 |
- mjw (QUIT: Quit: Leaving) (~mark@gnu.wildebeest.org) | 01:54 | |
- mtm (QUIT: Ping timeout: 244 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 02:02 | |
vkoskiv | I stuck a bluetooth dongle in, obtained firmware and it's working now :D | 02:14 |
vkoskiv | On my Arch desktop this dongle just worked, but on debian I had to download the manufacturer driver package to extract the firmware | 02:15 |
vkoskiv | Are there any extra internal USB ports in addition to the two for the keyboard/mouse? | 02:17 |
- Christoph_ (QUIT: Remote host closed the connection) (~Christoph@p54bf66aa.dip0.t-ipconnect.de) | 03:58 | |
+ mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 04:09 | |
- erle (QUIT: Ping timeout: 246 seconds) (~erle@ip5f5af7b3.dynamic.kabel-deutschland.de) | 04:11 | |
vkoskiv | I wrote a fix for the circle+1 oopsie and tested it on my hardware. I made it so if the system is powered up, it does nothing. | 05:00 |
vkoskiv | I submitted a registration to the gitlab server. Firefox didn't save my password though so I'll have to reset that tomorrow | 05:02 |
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 05:03 | |
vkoskiv | Actually it might have saved it. | 05:03 |
+ erle (~erle@95.90.247.179) | 05:46 | |
- Gooberpatrol66 (QUIT: Ping timeout: 248 seconds) (~Gooberpat@user/gooberpatrol66) | 05:50 | |
josch | vkoskiv: what is the filename of the firmware you downloaded for your bluetooth dongle? usually these firmware bits are also distributed by debian but only as part of the non-free repository. | 07:07 |
+ Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 08:00 | |
+ littlebo1eep (~alMalsamo@gateway/tor-sasl/almalsamo) | 09:13 | |
- littlebo1eep (QUIT: Quit: leaving) (~alMalsamo@gateway/tor-sasl/almalsamo) | 09:24 | |
+ littlebo1eep (~alMalsamo@gateway/tor-sasl/almalsamo) | 13:17 | |
- littlebo1eep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 13:22 | |
- iank (QUIT: Quit: ZNC 1.8.2+deb2+b1 - https://znc.in) (~iank@fsf/staff/iank) | 13:25 | |
+ iank (~iank@fsf/staff/iank) | 13:27 | |
+ Christoph_ (~Christoph@p54bf632f.dip0.t-ipconnect.de) | 13:35 | |
- mtm (QUIT: Ping timeout: 255 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 14:03 | |
vkoskiv | josch: I followed these instructions verbatim: https://gist.github.com/ssledz/69b7f7b0438e653c08c155e244fdf7d8 | 14:51 |
vkoskiv | The author has the exact hardware I do. | 14:51 |
vkoskiv | So BCM20702A1-0b05-17cb.hcd | 14:52 |
vkoskiv | Oddly enough, I didn't find this file on my arch system, but it has to be in there somewhere | 14:52 |
josch | vkoskiv: you are right, that firmware seems to be missing from Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801084 | 15:00 |
+ littlebo1eep (~alMalsamo@gateway/tor-sasl/almalsamo) | 15:11 | |
- littlebo1eep (QUIT: Quit: leaving) (~alMalsamo@gateway/tor-sasl/almalsamo) | 15:17 | |
- Christoph_ (QUIT: Remote host closed the connection) (~Christoph@p54bf632f.dip0.t-ipconnect.de) | 15:30 | |
+ Christoph_ (~Christoph@p54bf632f.dip0.t-ipconnect.de) | 15:32 | |
vkoskiv | Oh well. Was easy enough to install. | 15:34 |
vkoskiv | I seem to be missing apt-listbugs | 15:35 |
josch | vkoskiv: that's not yet merged: https://source.mnt.re/reform/reform-system-image/-/merge_requests/49 | 15:38 |
josch | but even once it's merged the image can currently not be built because the CI is broken | 15:38 |
josch | minute: since you merged the sysimage-v3 branch to main, maybe this is an opportunity to use a different CI runner based on some container? That way, each job/pipeline would be ephemeral as well as independent from each other and thus unable to break other CI builds. | 15:40 |
vkoskiv | So if I understand correctly, the v3 img is using the normal debian unstable repos, but with a reform-specific 'layer' on top to intercept packages that need tweaks, right? | 15:41 |
josch | vkoskiv: yes | 15:42 |
vkoskiv | Very cool! I am absolutely in love with this distribution. All the defaults just perfectly map to the way I want them :D | 15:42 |
vkoskiv | I've added some stuff from my dotfiles for vim and bash, and that's basically it. | 15:42 |
vkoskiv | I think I'll take a look at tweaking the blender package, it seems to be partially broken | 15:43 |
vkoskiv | I know it required some tweaks for Reform, but it's missing a bunch of settings in the settings panel | 15:43 |
vkoskiv | I'd also like to see if I can include Cycles there, I know 2.79 had it already. Not sure if it depends on OpenCL though. | 15:44 |
josch | vkoskiv: please go ahead! I've kept it alive for the past months but I'm not a blender user so I just kept it compiling and checked that it starts but i have no idea how it should look or what it should do. | 15:44 |
vkoskiv | I still need to write the blender integration code for my raytracer, since that one runs on pretty much any computer from the last 30ish years. | 15:44 |
vkoskiv | josch: Cool, will do. I'm also really interested in working on the firmware. Already did a small fix :D | 15:45 |
josch | Yup, I saw that, nice! :) | 15:45 |
josch | vkoskiv: I also took your comments three days ago about my explanations about how the boot process works to heart and started writing a more comprehensive guide: https://source.mnt.re/reform/reform-handbook/-/issues/2 | 15:46 |
vkoskiv | That looks like some solid documentation to me! | 15:48 |
vkoskiv | Right now my setup is actually using the boot partition from my emmc, so the only thing I need the sd card for is u-boot, I think. | 15:49 |
josch | not handbook-quality though, so somebody else has to do those adjustments :) | 15:49 |
+ mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 16:09 | |
verx | josch: thank you for that documentation! I’ve been dual-booting Gentoo on nvme and Debian on SD, and struggling since the sysimage-v3 changes… this helps | 17:04 |
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20) | 18:00 | |
josch | verx: how are you booting gentoo? | 18:10 |
minute | josch: yeah, originally it wasn't possible to build in a container because of... some filesystem generation foo in the container that didn't work; don't quite remember. maybe it's possible again with the new build | 18:32 |
minute | vkoskiv: cycles was cpu based/i tried it once with the 4 cores | 18:32 |
minute | josch: i can go over the docs change during the workweek | 18:33 |
minute | i have to keep down my work activities on weekends to prevent burnout | 18:33 |
josch | minute: since you don't need to be root anymore to generate an image, it should work inside a container even if the container doesn't give you all the privileges of root | 18:35 |
minute | josch: cool, then we should def. try that | 18:36 |
josch | the mmdebstrap stuff definitely works inside lxc or docker -- if it doesn't then that's a bug that i can probably fix | 18:36 |
cinap_lenrek | minute: the mnt-reform can also boot completely off usb, no? | 18:37 |
cinap_lenrek | like without sdcard? | 18:37 |
minute | cinap_lenrek: not that i know of. only via emmc->usb | 18:38 |
minute | the imx bootrom doesn't have a usb stack | 18:38 |
cinap_lenrek | ah, ok | 18:38 |
minute | well, that's not entirely true | 18:38 |
cinap_lenrek | at work, we have a powerpc based machine from nxp and that is crazy | 18:39 |
cinap_lenrek | its bootrom can boot from usb iirc | 18:39 |
minute | there is cable based usb debug/boot mode that is tied to running the usb in gadget mode | 18:39 |
minute | yeah, i was wrong. but i think the bootrom can't access usb ~storage~ on its own | 18:39 |
cinap_lenrek | makes sense, thank you! | 18:39 |
minute | there's something called mfgtool | 18:40 |
cinap_lenrek | motherfuckingtool | 18:41 |
minute | uuu https://github.com/NXPmicro/mfgtools | 18:41 |
minute | yes | 18:41 |
minute | > uuu (universal update utility) for nxp imx chips -- libuuu-1.0.1-gffd9837 | 18:41 |
minute | lol > Download u-boot.imx via HID device | 18:41 |
minute | why HID | 18:41 |
cinap_lenrek | hahahaha | 18:41 |
cinap_lenrek | minute: so they'r robo-typing and mashing the keys just very fast | 18:42 |
minute | pretty baroque https://github.com/NXPmicro/mfgtools/blob/master/uuu/uuu.cpp | 18:43 |
minute | > Generally iMX ROM will fail back to usb serial download mode if boot failure | 18:45 |
minute | i'm not sure which or if both of the usb hosts support this | 18:50 |
minute | on mnt reform, USB1 is connected to the hub and USB2 goes directly to the usb port next to the HDMI | 18:51 |
minute | not sure if USB2 can be used for uuu | 18:51 |
cinap_lenrek | is here a way to chnage the bootcmd? | 18:52 |
cinap_lenrek | it seems to get ignored for saveenv | 18:52 |
cinap_lenrek | i ust want it to pxe boot by default | 18:57 |
cinap_lenrek | it seems the only way is to modify that boot script permanently? | 18:57 |
cinap_lenrek | well | 18:58 |
cinap_lenrek | or make another script | 18:58 |
cinap_lenrek | called netboot.scr | 18:58 |
cinap_lenrek | and change the script variable? | 18:58 |
cinap_lenrek | nope. | 19:00 |
cinap_lenrek | so both $script and $bootcmd are locked down? | 19:01 |
minute | maybe josch knows more? | 19:01 |
+ mjw (~mark@gnu.wildebeest.org) | 19:04 | |
sigrid | you can make a script that sources another one if it exists | 19:05 |
sigrid | so to disable netboot you'd just rename it | 19:05 |
Boostisbetter | Just curious: but are we at a point where we can simple run apt upgrade and not break anything on the Reform? | 19:08 |
Boostisbetter | not in a rush myself, I am very happy with my Reform. | 19:08 |
minute | funny, the imx8 processors page on nxp is 404 now | 19:09 |
minute | Boostisbetter: normally this should be the case with systemimage v3... we agreed to put debian-listbugs in there so you can see the risks up front | 19:09 |
cinap_lenrek | the issue is i cant easily modify files from uboot | 19:10 |
cinap_lenrek | if i screw this up i lock myself out | 19:10 |
cinap_lenrek | this is just stupid | 19:10 |
cinap_lenrek | let me instead build my own uboot without that nonsense | 19:11 |
cinap_lenrek | i mean, if you screw up the uboot env, you can always reset it | 19:11 |
cinap_lenrek | but some file on the sdcard you cant easily once you screwed your linux somehow | 19:11 |
minute | cinap_lenrek: in the past i would just put changes here https://source.mnt.re/reform/reform-boundary-uboot/-/blob/f66054591dfa8712581de4869eac7d022ed42789/board/boundary/nitrogen8m_som/nitrogen8m_som.c#L328 | 19:13 |
minute | and build my own version of uboot | 19:13 |
cinap_lenrek | yeah | 19:14 |
Boostisbetter | ok, if I am not on systemimagev3, is there a way for me to get there with out having to start all over? You know, bring my system up to that point? | 19:14 |
cinap_lenrek | thanks for the link | 19:14 |
minute | Boostisbetter: yes, i did that. it was a bit complicated though and there is no guide for it yet | 19:18 |
minute | Boostisbetter: it might be easier to just backup your home folder (and maybe some etc stuff), start over and restore your home folder and configs | 19:18 |
cinap_lenrek | ah | 19:19 |
cinap_lenrek | i see now | 19:19 |
cinap_lenrek | yeah | 19:19 |
Boostisbetter | minute: is it bad if I just keep what I have, and not update? I mean overtime I know that is not wise, but in the hopes that a guide might be produced. The reason I'm not keep on it, is I had to get a lot of stuff working (boxes, etc.) and I would rather not having to set that all up again. | 19:20 |
cinap_lenrek | in the stock it always hard overrides $script and $bootcmd | 19:20 |
cinap_lenrek | and in your image it doesnt | 19:20 |
cinap_lenrek | makes sense | 19:20 |
cinap_lenrek | in fact | 19:22 |
cinap_lenrek | i can just remove the call to set_env_vars() from board_late_init() no? | 19:22 |
cinap_lenrek | its fine to have this as a default | 19:22 |
minute | Boostisbetter: well, you're free to run your system how you like, that's one of the benefits of reform | 19:32 |
minute | cinap_lenrek: idk, i'd just try :D | 19:33 |
cinap_lenrek | didnt work :( | 19:33 |
vkoskiv | minute: what do you do for leisure on weekends? | 19:33 |
vkoskiv | For me it's kinda weird. I write code both for my dayjob and as a hobby :D | 19:33 |
vkoskiv | I've made it work by doing very different types of programming in the two. | 19:34 |
minute | vkoskiv: since this year i spend most of the weekend with my partner, we watch movies or nerd about videogames, cook and go to the park and stuff | 19:35 |
minute | i used to do more coding on weekends too yup | 19:35 |
minute | but reform is my dayjob and i usually work more than 40h a week on it | 19:35 |
minute | (or, MNT) | 19:35 |
vkoskiv | Yeah it's important to balance that out to prevent burnout | 19:35 |
minute | yep | 19:36 |
vkoskiv | Cool job though, right? :D | 19:36 |
minute | hobby turned into job means you need different stuff as a hobby | 19:36 |
minute | yes, i would really like to keep this job | 19:36 |
vkoskiv | I can't put to words how much I enjoy this thing. Thank you and the team for making it happen! | 19:36 |
minute | depends on how well pocket reform + reform next version(s) will go, sales wise | 19:36 |
minute | a lot of pocket design work will go back into big reform though | 19:37 |
minute | (some new glue chips etc that are sourceable) | 19:37 |
vkoskiv | Yeah, what's the lead time on AVR stuff now? | 19:37 |
minute | summer 2023 | 19:37 |
vkoskiv | Geez. | 19:37 |
minute | so we're phasing avr out | 19:37 |
minute | i must say the new trackball is great so far | 19:38 |
minute | i'm astonished how well rev 1 just works with rp2040 | 19:38 |
minute | so i'm gonna put that in the keyboard too | 19:38 |
minute | and on the motherboard instead of lpc | 19:38 |
minute | the sdk is very sane also | 19:38 |
vkoskiv | Any big code changes in the firmware? Lots of ifdefs or mostly the same? | 19:38 |
vkoskiv | Or is it a new firmware completely | 19:38 |
minute | well, the trackball is a rewrite | 19:38 |
minute | mostly | 19:38 |
minute | but the keyboard will need to be some modular thing i guess, not sure 100% yet | 19:39 |
minute | good that i recently split it up into a bunch of .c files | 19:39 |
minute | also, there will be a different usb hub | 19:39 |
minute | and maybe different power supply stuff | 19:39 |
minute | and maybe i.mx8mp | 19:39 |
minute | (plus) | 19:40 |
cinap_lenrek | set_env_vars()switch to partitions #0, OK | 19:40 |
vkoskiv | An extra internal usb port would be fun if possible | 19:40 |
cinap_lenrek | hmmmmm | 19:40 |
cinap_lenrek | this is not the uboot i'm looking for | 19:40 |
vkoskiv | I have a busted up bluetooth dongle I'd like to solder in permanently | 19:40 |
minute | vkoskiv: what form factor of port? | 19:40 |
minute | vkoskiv: you could hack nanohub in there | 19:40 |
vkoskiv | Not sure. I can solder, so anything works. | 19:41 |
vkoskiv | And true! I might go with that | 19:41 |
vkoskiv | Just hook it up to the trackball port and trackball to nanohubn | 19:41 |
minute | https://muxtronics.nl/nanohub.html | 19:41 |
minute | https://www.tindie.com/products/mux/nanohub-tiny-usb-hub-for-hacking-projects/ | 19:41 |
minute | i tried this a long time ago, it's great | 19:41 |
cinap_lenrek | its not enougth to override /boot/flash.bin? | 19:41 |
vkoskiv | That looks good for what I want! | 19:41 |
Boostisbetter | There is also the retrocution 2 or 4 port hub | 19:42 |
Boostisbetter | https://www.retrocution.com/shop/ | 19:42 |
minute | cinap_lenrek: u-boot needs to be written to a certain sector on the raw disk | 19:42 |
cinap_lenrek | oh | 19:42 |
Boostisbetter | I'm currently trying to use a 4 port one of those for the Penkesu that I have. | 19:42 |
minute | see https://mntre.com/reform2/handbook/advanced.html#system-boot | 19:43 |
cinap_lenrek | ok | 19:43 |
minute | > The resulting file, processed to be in the correct format loadable by the i.MX8MQ processor is flash.bin. This file has to be written to the boot medium at an offset of 33kB (33792 bytes). | 19:43 |
minute | that's why the first partition has to be at an offset | 19:43 |
minute | (to not conflict with the bootloader) | 19:43 |
cinap_lenrek | 33792 | 19:44 |
cinap_lenrek | god it | 19:44 |
vkoskiv | What sorts of CPU temps are y'all seeing when in use? | 19:45 |
vkoskiv | I'm wondering if my repeated heatsink removal/replacement has affected the thermal paste distribution such that it gets warmer | 19:45 |
vkoskiv | At 60C now just chilling in a terminal | 19:45 |
vkoskiv | With firefox and telegram open in another workspace | 19:45 |
cinap_lenrek | whats mmcblk0boot0? | 19:46 |
cinap_lenrek | is here a way to get the offsets of these partitions? | 19:48 |
Boostisbetter | In the 50s under my normal workload, which is about 10 programs running at one. | 19:49 |
Boostisbetter | 52 is normal after the laptop has been on for a couple of hours. It does depends on the room ambiance though. | 19:49 |
Boostisbetter | Summer in Germany is usually without AC and so things will be hotter then. | 19:49 |
Boostisbetter | It can get so bad that I don't use my desktop and try to only use a laptop where I heavily monitor the heat readings. | 19:50 |
minute | vkoskiv: 59 deg | 19:50 |
minute | cinap_lenrek: that's a emmc boot partition | 19:50 |
minute | cinap_lenrek: you can unlock it in linux with some echo to sysfs | 19:51 |
minute | (unlock for writing i mean) | 19:51 |
vkoskiv | I slammed this thing with my raytracer and it was still in reasonable temperatures, so it should be fine | 19:51 |
vkoskiv | I suspect my SSD draws more current than the recommended one. I rarely see <0.3A current draw when in light use | 19:51 |
vkoskiv | I remember someone mentioned averaging 250mA | 19:52 |
cinap_lenrek | so iirc, should be dd if=flash.bin of=/dev/mmcblk0 seek=66 | 19:52 |
vkoskiv | Betting it's my intel SSD that is the difference | 19:52 |
Boostisbetter | vkoskiv: I hardly ever see anything greater than .280A | 19:52 |
cinap_lenrek | lets try | 19:53 |
Boostisbetter | I have the wifi card and nvme (transcend) populated. | 19:53 |
vkoskiv | minute: How do you feel about an automatic refresh every N seconds when the battery/status views are open? | 19:53 |
Boostisbetter | right now my system has been up for 2 hours and I'm at 46C | 19:53 |
cinap_lenrek | nope. | 19:54 |
cinap_lenrek | was it like oseek? | 19:54 |
minute | vkoskiv: if cleanly implementable, sure! | 19:58 |
minute | cinap_lenrek: wait, i have a script somewhere | 19:58 |
cinap_lenrek | its odd | 19:58 |
cinap_lenrek | why didnt that work? | 19:58 |
minute | cinap_lenrek: you sure bs is 512? | 19:58 |
minute | yeah i use sudo dd if=flash.bin of=/dev/sda bs=1024 seek=33 | 19:59 |
cinap_lenrek | i tried reading with skip before | 19:59 |
cinap_lenrek | ah! | 19:59 |
cinap_lenrek | jesus | 19:59 |
minute | but mmcblk0 might be wrong | 19:59 |
minute | maybe it's mmcblk0boot0 | 19:59 |
cinap_lenrek | didnt work | 20:00 |
cinap_lenrek | where the hell does that go | 20:00 |
minute | for me there is a bootloader at hex 8400 on mmcblk0boot0 | 20:01 |
minute | 00008400 d1 00 20 41 00 00 c1 32 00 00 00 00 00 00 00 00 |.. A...2........| | 20:01 |
cinap_lenrek | d: error writing '/dev/mmcblk0boot0': Operation not permitted | 20:01 |
cinap_lenrek | yeah | 20:02 |
minute | yeah, the sysfs thing i mentioned comes into play there | 20:02 |
cinap_lenrek | i thought mmcblk0 was ok because when i dumped it it looked fine | 20:02 |
minute | https://www.kernel.org/doc/Documentation/mmc/mmc-dev-parts.txt | 20:02 |
cinap_lenrek | ok | 20:02 |
minute | echo 0 > /sys/block/mmcblkXbootY/force_ro | 20:02 |
minute | looks like that's a hardware feature of emmc | 20:03 |
cinap_lenrek | ok | 20:04 |
cinap_lenrek | that wrote | 20:04 |
cinap_lenrek | but thats still not my uboot | 20:04 |
cinap_lenrek | so it is in boot1? | 20:06 |
cinap_lenrek | whats the difference? | 20:06 |
cinap_lenrek | also no | 20:07 |
cinap_lenrek | what the hell | 20:07 |
cinap_lenrek | the way i know its not my uboot is because i changed the set_env_vars() print | 20:09 |
cinap_lenrek | and with strings i can show its in the binary or not | 20:09 |
cinap_lenrek | root@reform:~# strings /boot/flash.bin | grep nope | 20:11 |
cinap_lenrek | set_env_vars(); nope! | 20:11 |
cinap_lenrek | so out of ideas | 20:14 |
cinap_lenrek | is it possible to flash u-boot from u-boot maybe? | 20:15 |
cinap_lenrek | at least u-boot is able to write the environment block fine | 20:15 |
minute | i know that writing to emmc def. works because we flash the rescue image onto every reform | 20:17 |
minute | you are flipping the BOOT switch to eMMC yes? | 20:17 |
minute | i mean the dip switch | 20:17 |
minute | on the SOM | 20:17 |
minute | (has to be turned OFF) | 20:18 |
cinap_lenrek | uhm | 20:18 |
cinap_lenrek | no | 20:18 |
cinap_lenrek | what dip switch? | 20:18 |
cinap_lenrek | oh | 20:19 |
minute | :D | 20:19 |
cinap_lenrek | you mean i was like booting some kind of rescue system all the time? | 20:19 |
cinap_lenrek | which is located in a different address? | 20:19 |
minute | no you were booting from SD card i guess | 20:19 |
cinap_lenrek | yeah | 20:20 |
minute | that's the default | 20:20 |
minute | eMMC is the rescue system | 20:20 |
minute | enabled only by flipping the dip switch on the SOM off | 20:20 |
minute | is there a reason you don't want to boot via SD card? | 20:20 |
minute | (i prefer SD because easier to fix from another computer) | 20:21 |
cinap_lenrek | jesus | 20:21 |
cinap_lenrek | its probably mmcblk1 | 20:21 |
cinap_lenrek | yeah | 20:21 |
minute | yeah, that's the SD card | 20:21 |
cinap_lenrek | thats also where /boot is from | 20:21 |
cinap_lenrek | m( | 20:21 |
minute | yep | 20:21 |
cinap_lenrek | everything makes sense | 20:21 |
minute | cool | 20:21 |
cinap_lenrek | yeah | 20:22 |
cinap_lenrek | and the sdcard shouldnt have any protections | 20:22 |
minute | yeah | 20:24 |
cinap_lenrek | WORKS | 20:25 |
cinap_lenrek | thanks for your patience! | 20:25 |
minute | great | 20:30 |
- XgF (QUIT: Remote host closed the connection) (~quassel@2001:19f0:5001:1174:5400:2ff:fef2:1fa2) | 20:30 | |
+ XgF (~quassel@2001:19f0:5001:1174:5400:2ff:fef2:1fa2) | 20:32 | |
josch | i was pinged earlier but from the backlog I was reading I guess the problem got solved? | 21:23 |
- ggoes (QUIT: Ping timeout: 258 seconds) (~gregf@fsf/staff/ggoes) | 22:05 | |
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 22:15 | |
vkoskiv | josch: Are you able to approve my gitlab acct, perhaps? | 22:31 |
josch | vkoskiv: nope, pinging minute who has the required permissions | 22:32 |
vkoskiv | But they are off work today...! | 22:32 |
vkoskiv | I still can't seem to get the firmware side of suspend working. | 22:34 |
vkoskiv | I flashed the kbd and lpc with the latest firmware and I still get 'no response from LPC' when invoking the wake cmd | 22:34 |
- Gooberpatrol66 (QUIT: Quit: Leaving) (~Gooberpat@user/gooberpatrol66) | 22:53 | |
vkoskiv | Interesting observation! The trackball on my Powerbook 100 is the exact same size as the Reform trackball. But it has this light gray surface, and the sensor has a really hard time tracking it. | 22:56 |
vkoskiv | So it seems like the sensor likes a darker surface? | 22:56 |
minute | it just needs some texture, probably | 23:18 |
vkoskiv | Yeah the pb100 ball is a bit more shiny. And the bigger PB150 ball is very polished. | 23:19 |
minute | vkoskiv: approved your account | 23:20 |
vkoskiv | Thank you! | 23:21 |
vkoskiv | https://source.mnt.re/reform/reform/-/merge_requests/27 | 23:31 |
vkoskiv | The little check in the kbd firmware is optional really. It just prevents the bootup animation from running if the power-on command didn't actually do anything | 23:32 |
vkoskiv | On the other hand, the animation is very cool, so it would be okay to drop that check. | 23:32 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!