| - patsavoura (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.8.163) | 00:16 | |
| + Ar|stote|is (~linx@149.210.8.163) | 00:18 | |
| + jacobk (~quassel@129.110.242.224) | 00:49 | |
| - mjw (QUIT: Ping timeout: 255 seconds) (~mjw@gnu.wildebeest.org) | 00:59 | |
| - mtm (QUIT: Ping timeout: 264 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 01:04 | |
| - Gooberpatrol66 (QUIT: Read error: Connection reset by peer) (~Gooberpat@user/gooberpatrol66) | 01:29 | |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 01:31 | |
| abortretryfail | ACTION uses USB B-B cables | 01:45 |
|---|---|---|
| mhoye | Would someone in here know why terminal blanking timeouts are so quick these days? | 01:54 |
| violet | blanking timeouts? | 01:54 |
| violet | what is that | 01:54 |
| mhoye | Well, I'm in a terminal window - tty, no gui running - and the screen blanks itself pretty often | 01:55 |
| violet | ah interesting | 01:56 |
| abortretryfail | swaylock? | 01:57 |
| abortretryfail | er wait, no gui... | 01:57 |
| hramrach | https://unix.stackexchange.com/questions/8056/disable-screen-blanking-on-text-console | 01:58 |
| abortretryfail | i guess you can configure logind to do that | 01:58 |
| abortretryfail | but i didnt think it does by default | 01:59 |
| mhoye | hramrach: it's not a setterm thing that I can see, unfortunately | 01:59 |
| hramrach | there is a sysfs file as well | 01:59 |
| hramrach | if you can't see that either then something is fishy | 02:00 |
| mhoye | I'll look for that... deblanking reliably dumps the "atomic post disable skipped", imx-dcss error in my logs too. | 02:00 |
| mhoye | /sys/module/kernel/parameters/consoleblank is set to 60 but that number should mean minutes | 02:03 |
| hramrach | seconds | 02:03 |
| mhoye | hmm. setterm --blank=X, docs say X is minutes, but this is not that I guess | 02:07 |
| hramrach | Documentation/admin-guide/kernel-parameters.txt says it's seconds | 02:08 |
| mhoye | I guess that's set in my boot params somewhere. | 02:08 |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 02:08 | |
| mhoye | Thanks for pointing me to that, next step is figure out where I set boot params in a uboot world | 02:09 |
| hramrach | boot parameters can change th default, boot scripts can change it again. The stakexchange has the boot parameter | 02:09 |
| mhoye | I guess I also need to figure out of setterm intends minutes and sets something to seconds and file that somewhere | 02:09 |
| hramrach | it would be in u-boot.scr I suppose | 02:09 |
| hramrach | setterm probably translates it | 02:10 |
| hramrach | if you have a .scr file there was a tool in u-boot-tools for unpackging and re-packing it but I don't remember what it was | 02:11 |
| mhoye | I can hand-modify boot.scr - it doesn't currently say anything about that parameter but I can see where to add it. | 02:12 |
| mhoye | interesting that the stackoverflow says "defaults to 600" but I'm seeing it default to 60 | 02:13 |
| mhoye | Well, off to reboot and see if I broke anything important. | 02:13 |
| hramrach | there is some crc or something so it won't work just editing the file | 02:15 |
| mhoye | I've just figured out how to recover from that! | 02:35 |
| mhoye | thankfully I had the foresight to copy boot.scr to a backup file and setenv boot_scripts boot.scr.bak saved me | 02:36 |
| mhoye | haha, like 45 minut how I can set my console timeout and now I'm figuring out how to correctly modify a uboot config file to pass a crc check | 02:39 |
| mhoye | thanks linux | 02:39 |
| mhoye | 45 minutes ago, I asked, rather. | 02:39 |
| - chomwitt (QUIT: Ping timeout: 268 seconds) (~chomwitt@2a02:587:7a10:2a00:1ac0:4dff:fedb:a3f1) | 02:45 | |
| - XYZ (QUIT: Ping timeout: 276 seconds) (~XYZ@37-48-35-0.nat.epc.tmcz.cz) | 03:08 | |
| + mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 03:09 | |
| + XYZ (~XYZ@37-48-35-0.nat.epc.tmcz.cz) | 03:26 | |
| - nsc (QUIT: Ping timeout: 268 seconds) (~nicolas@229-97-142-46.pool.kielnet.net) | 03:59 | |
| + nsc (~nicolas@240-48-142-46.pool.kielnet.net) | 04:00 | |
| - jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@129.110.242.224) | 05:01 | |
| + jacobk (~quassel@129.110.242.224) | 05:12 | |
| - Gooberpatrol66 (QUIT: Ping timeout: 245 seconds) (~Gooberpat@user/gooberpatrol66) | 05:36 | |
| - BoostisBetter (QUIT: Ping timeout: 255 seconds) (4a410829d7@irc.cheogram.com) | 05:38 | |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 05:51 | |
| - eibachd (QUIT: Remote host closed the connection) (~eibachd@p200300dcf73d8b00af7dbf8d349916aa.dip0.t-ipconnect.de) | 06:26 | |
| + eibachd (~eibachd@p200300dcf73d8b00af7dbf8d349916aa.dip0.t-ipconnect.de) | 06:26 | |
| + chomwitt (~chomwitt@2a02:587:7a10:2a00:1ac0:4dff:fedb:a3f1) | 07:00 | |
| - Gooberpatrol66 (QUIT: Ping timeout: 256 seconds) (~Gooberpat@user/gooberpatrol66) | 07:19 | |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 07:22 | |
| - Gooberpatrol66 (QUIT: Remote host closed the connection) (~Gooberpat@user/gooberpatrol66) | 07:24 | |
| - jacobk (QUIT: Ping timeout: 240 seconds) (~quassel@129.110.242.224) | 07:44 | |
| - eibachd (QUIT: Ping timeout: 240 seconds) (~eibachd@p200300dcf73d8b00af7dbf8d349916aa.dip0.t-ipconnect.de) | 07:45 | |
| + eibachd (~eibachd@2a01:599:230:c8b:f1d8:5ad4:9b03:fe1b) | 07:45 | |
| + BoostisBetter (4a410829d7@irc.cheogram.com) | 07:53 | |
| - BoostisBetter (QUIT: Ping timeout: 260 seconds) (4a410829d7@irc.cheogram.com) | 08:01 | |
| + BoostisBetter (4a410829d7@irc.cheogram.com) | 08:02 | |
| josch | hrm... interesting, i never noticed any blanked with the stock sysimage on the reform. I'm sure i would've noticed with such a low timeout. | 08:03 |
| josch | my /sys/module/kernel/parameters/consoleblank is 0 | 08:03 |
| josch | i wonder what has set that because my /proc/cmdline just says: ro no_console_suspend cma=512M@3G cryptomgr.notests console=tty1 | 08:04 |
| josch | mhoye: even if you made boot.scr work by using mkimage, your changes will be overwritten the next time flash-kernel runs as boot.scr is auto-generated | 08:07 |
| josch | mhoye: do you think a big warning at the top of boot.scr could've stopped you from trying to edit it manually without running mkimage? | 08:08 |
| josch | mhoye: if you want to be able to just edit a text file, consider using an extlinux.conf which can be auto-generated by u-boot-menu | 08:09 |
| josch | for persistent changes to boot.scr write them to /etc/default/flash-kernel | 08:09 |
| + mjw (~mjw@gnu.wildebeest.org) | 08:13 | |
| + reform28288 (~kpulp@2600:1017:a410:d2df:5f42:de5a:842e:70c6) | 08:26 | |
| - reform28288 (QUIT: Client Quit) (~kpulp@2600:1017:a410:d2df:5f42:de5a:842e:70c6) | 08:27 | |
| + jacobk (~quassel@utdpat242016.utdallas.edu) | 08:33 | |
| - jacobk (QUIT: Ping timeout: 245 seconds) (~quassel@utdpat242016.utdallas.edu) | 08:46 | |
| + jacobk (~quassel@64.189.201.150) | 09:06 | |
| hramrach | I think it would be advisable to ship extlinux.conf rather than boot.scr by default. However, boot.scr can do anything, it uses documented u-boot commands. On the other hand, it's not entirely clear how the pxelinux documentation translates to what u-boot does with the file, and how one can, for example, load a device tree with pxelinux.conf | 10:02 |
| hramrach | I kind of gave up on figuring this out because the default on the distribution I currently use is to build u-boot with EFI support, and load grub.efi which is identical across all systems | 10:04 |
| josch | since our u-boot prefers extlinux.conf over boot.scr (if booth exist) installing u-boot-menu is all that is needed to enable it | 10:04 |
| hramrach | enabling it is one thing, making use of it another | 10:04 |
| josch | true but then i probably missed the point you wanted to make | 10:05 |
| hramrach | boot scr is hard to deal with but at least documented. pxelinux.conf support is undocumented bodge | 10:06 |
| josch | i thought we were talking about extlinux.conf? | 10:06 |
| hramrach | whatever the file is named | 10:06 |
| josch | yes, it being poorly documented already bit me in the butt as i was not aware that it supports variables using the ${varname} syntax | 10:06 |
| hramrach | and also not needed if you make u-boot load grub | 10:07 |
| josch | sure | 10:08 |
| hramrach | that does provide a ducumented syntax for making menus | 10:08 |
| josch | does grub have access to the ${bootargs} values set by u-boot? | 10:08 |
| hramrach | I don't think so | 10:09 |
| hramrach | but I have not looked at the details | 10:09 |
| josch | then that makes loading grub.efi a non-started for the official reform system image because each SoM needs some special kernel cmdline values which are known and set by u-boot and have to be passed on to whoever loads the kernel | 10:09 |
| hramrach | why does it need special kernel cmdline values? | 10:10 |
| hramrach | also these values can be dumped into a config file so they are included in the grub menu | 10:11 |
| josch | yes, but that config file has to be different for each different SoM | 10:11 |
| josch | so we cannot have one configuration that works on all platforms | 10:11 |
| hramrach | so back to the questio: why kernel commandline parameters? | 10:11 |
| hramrach | can't the kernel detect it, can't it be built into the specific driver? | 10:12 |
| hramrach | or into the device tree | 10:12 |
| josch | i cannot tell you as i do not do kernel stuff | 10:13 |
| josch | minute can probably give you a good answer | 10:13 |
| hramrach | also EFI has variables but the support for these is poor in u-boot | 10:14 |
| minute | i believe an alternative is to embed most of the cmdline args in the dtb file | 10:18 |
| josch | minute: but should the patches and dtbs that we ship not be made in a way so that they become upstream-able? For example for ls1028a, one can just use the upstream kernel without patches (right?) but we still need to set iommu.passthrough=1 arm-smmu.disable_bypass=0 | 10:23 |
| minute | josch: why the kernel does not work without parameters as advertised is above my paygrade still | 10:27 |
| minute | this reminds me to try to turn off mitigations on a311d and compare performance | 10:28 |
| hramrach | The iommu stuff is indeed problematic. The default can be patched in the kernel but it's not clear what would be a default that works. Can try to dig up some distro discussion about this | 10:41 |
| - mjw (QUIT: Ping timeout: 264 seconds) (~mjw@gnu.wildebeest.org) | 10:46 | |
| hramrach | hm, depends on the PCI topology, no gneral default | 11:07 |
| hramrach | there is a kconfig option for setting the iommu options but with enough different SoCs some will need different settings | 11:09 |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 11:28 | |
| - GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon) | 12:23 | |
| + GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) | 12:24 | |
| * mark_ -> mjw | 12:57 | |
| - mtm (QUIT: Ping timeout: 255 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 13:03 | |
| - buckket (QUIT: Quit: buckket) (~buckket@vps.buckket.org) | 13:21 | |
| + buckket (~buckket@vps.buckket.org) | 13:21 | |
| hramrach | why do you need iommu.passthrough=1? | 13:28 |
| hramrach | there is discussion of arm iommu eg. here https://lore.kernel.org/lkml/ZK_-IHPEv_DNbKPd@orome/ | 13:37 |
| mhoye | josch: so, if my opinion is worth anything, I did waste bunch of time believing that editing boot.scr would be useful. The documentation you can find on the subject was pretty opaque and sometimes contradictory. | 13:50 |
| josch | mhoye: yes, that's also my experience | 13:51 |
| mhoye | I mean, it calls itself a script but if you cat it to a terminal the binary junk in the header breaks my terminal output, so... | 13:52 |
| mhoye | there's difficulty-in-depth here, from a first-contact perspective. | 13:53 |
| josch | hrm... sadly vagrantc is currently offline | 13:54 |
| josch | i bet it would already help a lot if the top of boot.scr would give some pointers of where to look if one wants to make changes | 13:55 |
| mhoye | Certainly I think a few breadcrumbs would be helpful, something like "this file is automatically generated, and will be overwritten when [something happens]. To make durable changes to your kernel boot options, [do the following]. | 13:56 |
| josch | yes, i put that on my todo list to make this happen | 13:57 |
| mhoye | One of the things we worked on a lot while I was at Mozilla was something we thought of as "codebase accessibility". Adding notes to the documentation and comments saying things like "We expect this process to work for you; if it doesn't, we consider that a bug, please email us at [bug address] with the details." | 14:02 |
| mhoye | Once we started doing that, we started finding a _ton_ of places where our documentation was misleading, subtly wrong, etc etc. | 14:03 |
| mhoye | But since it was all in the "getting set up, first contact with the project" stages, anyone working on the project full time would just never encounter it more than once, and once we were preinstalling dev environments on new-hire laptops, never. | 14:04 |
| mhoye | We have _no idea_ how many smart kids bounced off those documents. We can't know, but the moment we started putting in those breadcrumbs - that is, turning the failure modes of the process into easy ways to help improve them - contribution numbers started going up pretty quickly. | 14:06 |
| mhoye | I still want to know where it's getting set to 60 seconds, though, when the kernel default claims to be 600. I can't see it, wherever it is. | 14:10 |
| josch | mhoye: i looked into the latter problem and couldn't find it -- are you running the stock reform system image or something else? | 14:11 |
| mhoye | Far as I can tell, stock. | 14:12 |
| josch | uh then that's interesting | 14:12 |
| mhoye | I agree. I just put the stopwatch to it a moment ago though, and it's consistent. Stop typing, 60 seconds, screen blanks. I hit a key, it wakes up and shows the debug message I mentioned a few days ago, that minute filed | 14:14 |
| mhoye | curiously, in dmesg I am seeing an imx-dcss error | 14:15 |
| mhoye | "pixel clock set to 118800 kHz instead of 162000 kHz" right after the ti_sn_bridge_atomic_post_disable_skipped report | 14:16 |
| josch | mhoye: are you on imx8mq? | 14:17 |
| mhoye | How would I find out? | 14:18 |
| josch | cat /proc/device-tree/model | 14:18 |
| mhoye | that returns "MNT Reform 2" | 14:18 |
| josch | okay, then let me write a system image to an sd card and try to see what happens | 14:19 |
| josch | mhoye: you are on kernel 6.5? | 14:19 |
| mhoye | uname -a says 6.5.0-4 | 14:20 |
| mhoye | back in 5 | 14:21 |
| josch | seems i don't have an sd-card with me. i can only continue investigating in ~8 hours | 14:22 |
| mhoye | No rush for me, I'll help when I can. | 14:31 |
| minute | mhoye: this is not an error @ dcss. just an info | 14:56 |
| minute | sorry i didn't search the scrollback before, you tried setterm -blank 0 yes? | 14:57 |
| minute | and setterm -powersave off | 14:57 |
| minute | (apparently those don't work inside of tmux) | 14:57 |
| + mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 15:09 | |
| mhoye | minute: nor in xterm-256colors | 16:05 |
| - jjbliss (QUIT: Remote host closed the connection) (~jjbliss@1464766-static.elnsmiaa.metronetinc.net) | 16:29 | |
| + jjbliss (~jjbliss@1464766-static.elnsmiaa.metronetinc.net) | 16:33 | |
| minute | mhoye: you are using xterm on the linux console? how is that possible | 16:44 |
| - eibachd (QUIT: Read error: Connection reset by peer) (~eibachd@2a01:599:230:c8b:f1d8:5ad4:9b03:fe1b) | 17:33 | |
| + eibachd (~eibachd@p200300dcf73d8b0098db64f9ebbeee79.dip0.t-ipconnect.de) | 17:33 | |
| - colinsane (QUIT: Ping timeout: 268 seconds) (~colinunin@97-113-140-33.tukw.qwest.net) | 17:58 | |
| + colinsane (~colinunin@97-113-159-4.tukw.qwest.net) | 18:13 | |
| + amk (~amk@user/amk) | 18:13 | |
| - GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon) | 18:21 | |
| + GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) | 18:22 | |
| - jacobk (QUIT: Ping timeout: 255 seconds) (~quassel@64.189.201.150) | 18:33 | |
| + jacobk (~quassel@129.110.242.224) | 18:49 | |
| - jacobk (QUIT: Ping timeout: 268 seconds) (~quassel@129.110.242.224) | 18:57 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20) | 18:58 | |
| + jacobk (~quassel@utdpat241106.utdallas.edu) | 19:04 | |
| + mark_ (~mjw@gnu.wildebeest.org) | 19:04 | |
| - jacobk (QUIT: Ping timeout: 240 seconds) (~quassel@utdpat241106.utdallas.edu) | 19:35 | |
| mhoye | xterm-whatever as in the terminal-capabilities list, not the program | 19:51 |
| abortretryfail | there's a different termcap/terminfo for the Linux console | 19:51 |
| mhoye | I can just set it to "linux" and retry, but I don't think that changes any visible behavior | 19:53 |
| mhoye | But let me set them and restart here, see if that brings me any novelty | 19:53 |
| + jacobk (~quassel@129.110.242.224) | 20:07 | |
| minute | mhoye: ah i see | 20:07 |
| Zaba | https://github.com/util-linux/util-linux/blob/master/term-utils/setterm.c#L756 | 20:10 |
| Zaba | it outputs a hardcoded escape sequence to set the blanking timeout | 20:10 |
| Zaba | but that needs to be processed by the kernel virtual terminal to have an effect | 20:11 |
| Zaba | https://github.com/torvalds/linux/blob/master/drivers/tty/vt/vt.c#L1907 literally a 'setterm command' in the kernel | 20:14 |
| - mjw (QUIT: Killed (NickServ (GHOST command used by mark_!~mjw@gnu.wildebeest.org))) (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae) | 20:27 | |
| * mark_ -> mjw | 20:28 | |
| + mark_ (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae) | 20:28 | |
| minute | nice | 20:33 |
| - leonardo (QUIT: Quit: WeeChat 4.0.1) (leonardo@user/leonardo) | 20:53 | |
| - eibachd (QUIT: Ping timeout: 252 seconds) (~eibachd@p200300dcf73d8b0098db64f9ebbeee79.dip0.t-ipconnect.de) | 20:56 | |
| + eibachd (~eibachd@p200300dcf73d8b0074380750dd4bc002.dip0.t-ipconnect.de) | 20:57 | |
| mhoye | !! | 21:14 |
| mhoye | Zaba: thank you, good find. | 21:14 |
| - jacobk (QUIT: Ping timeout: 245 seconds) (~quassel@129.110.242.224) | 21:20 | |
| + jacobk (~quassel@129.110.242.224) | 21:29 | |
| hramrach | whn not running on the console directly you can use something like TERM-linux setterm ... </dev/tty0 >/dev/tty0 | 21:29 |
| hramrach | they recommend appending the output to /etc/issue so it gets printed on every terminal - portable to pretty much any init system ;-) | 21:33 |
| hramrach | but the question why the value differen across systems in the first place remains | 21:33 |
| - jacobk (QUIT: Ping timeout: 268 seconds) (~quassel@129.110.242.224) | 22:14 | |
| + jacobk (~quassel@utdpat241106.utdallas.edu) | 22:31 | |
| - jacobk (QUIT: Ping timeout: 245 seconds) (~quassel@utdpat241106.utdallas.edu) | 22:54 | |
| josch | vagrantc: hi there! Earlier today we talked about how it woulud be useful if boot.scr had a big fat warning in the top which: | 23:07 |
| - Gooberpatrol66 (QUIT: Remote host closed the connection) (~Gooberpat@user/gooberpatrol66) | 23:07 | |
| josch | a) explained how the file should not be edited by hand because of the binary checksum blob at the beginning | 23:07 |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 23:08 | |
| josch | b) explained what to edit to make persistent or temporary changes to it | 23:08 |
| * tadeus_brick -> TadeusTaD | 23:08 | |
| - Gooberpatrol66 (QUIT: Remote host closed the connection) (~Gooberpat@user/gooberpatrol66) | 23:08 | |
| josch | vagrantc: what are your thoughts about a patch that i can send you against the packaging git for flash-kernel which implements this for bootscript/all/bootscr.uboot-generic? | 23:08 |
| vagrantc | seems a bit overkill, but not expensive to implement | 23:10 |
| josch | vagrantc: what do you see as the downside of such a change? | 23:10 |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 23:10 | |
| josch | vagrantc: i now saw it happen repeatedly that people tried to hand-edit the file and made their system unbootable in the process | 23:11 |
| vagrantc | I don't expect to be able to edit /boot/vmlinuz* manually and have it work, or /boot/initrd, etc ... | 23:11 |
| vagrantc | is it just because it doesn't look binary enough? | 23:12 |
| josch | vagrantc: yes | 23:12 |
| vagrantc | josch: not opposed ... i guess it might prevent people from shooting themselves in the foot ... we already include plenty of comments, a few more lines won't hurt. :) | 23:13 |
| josch | cool! i'll cook something up then :) | 23:13 |
| vagrantc | josch: tricky is explaining all the various .d directories that might be affecting the result | 23:14 |
| vagrantc | but maybe the instructions can be general enough | 23:14 |
| - chomwitt (QUIT: Ping timeout: 268 seconds) (~chomwitt@2a02:587:7a10:2a00:1ac0:4dff:fedb:a3f1) | 23:14 | |
| josch | yes, i don't plan to dump the man page into boot.scr :) | 23:14 |
| josch | mhoye: progress ^ | 23:16 |
| flowy | josch: i've been learning gitlab by pulling the reform repos to a local instance and getting CI going. i might have found a tiny bug? not sure | 23:25 |
| flowy | reform-debian-packages/.gitlab-ci.yml:128, the grep for 'kernel/drivers/gpu/drm/imx/cdns/cdns_mhdp_imx.ko' doesn't find anything for bookworm's 6.1 kernel, as the module is located in a different path | 23:29 |
| flowy | returning 1 and spoiling the build even though the module is there | 23:30 |
| josch | flowy: oh interesting! On reform.d.n where I'm building linux 6.1 from bookworm I'm not making use of .gitlab-ci.yml so this went under the radar and was only ever tested for 6.5 | 23:32 |
| flowy | i just changed it to egrep 'cdns_mhdp_imx.ko$' but will take a while for the build to get there again ;) | 23:32 |
| josch | flowy: you tried setting BASESUITE to bookworm and see what happens? | 23:32 |
| flowy | yeah, that's why i'm hitting this. cause i'm trying to build bookworm rn | 23:33 |
| flowy | ok g2k i guess i should compare w the orchestrator script if there are other anomolies | 23:34 |
| flowy | somewhere between bookworm and bookworm-backports kernel, that module got put into this cdns/ subdir | 23:35 |
| josch | flowy: you know what the best part is? | 23:35 |
| flowy | ? | 23:37 |
| josch | it was me who moved the module into the cdns subdirectory XD | 23:37 |
| flowy | oh haha | 23:37 |
| flowy | funny loop | 23:38 |
| josch | reason was that when i rebased the patch I found that one of the reasons it had to be adapted was, that other stuff in drivers/gpu/drm/imx also moved into its own subdirs | 23:38 |
| flowy | appreciate the work, having fun and learning a lot digging through | 23:38 |
| josch | so i copied that pattern for cdns as well | 23:38 |
| josch | flowy: i have this diff locally which should fix it: https://paste.debian.net/hidden/b1e8dae1/ | 23:41 |
| flowy | cool i'll test it and let you know tomorrow | 23:45 |
| josch | flowy: thank you for finding and reporting this! :) | 23:46 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!