]>
Commit | Line | Data |
---|---|---|
675e15e5 TG |
1 | 09:10 < j`ey> Glanzmann: `git rev-list 6f59bc24287..smc/work` that might work, not sure how it deals with merges. git rebase is the better way. but if you do that youre on your own! |
2 | 09:19 < _jannau_> Glanzmann: git rebase --onto 5.17-rc3 6f59bc24287 | |
3 | 09:23 < j`ey> if you add -p it can also preserve the merges | |
37f23338 TG |
4 | |
5 | 19:13 < j`ey> but there's also CONFIG_OF_DMA_DEFAULT_COHERENT, which makes of_dma_is_coherent always return true | |
6 | ||
7 | 21:02 < jannau> mps: you need https://lore.kernel.org/u-boot/20220208210215.8612-1-j@jannau.net/ for extlinux | |
6189d624 TG |
8 | |
9 | ARCH: 23:29 < ah-[m]> yep, exactly. I had to grub-mkconfig -o /boot/grub/grub.cfg, and move my Image.gz to /boot, otherwise it was just what was on the wiki page | |
e70d320b TG |
10 | |
11 | https://lore.kernel.org/linux-arm-kernel/20211011165707.138157-1-marcan@marcan.st/ | |
12 | 19:02 < jannau> I think based on this branch https://github.com/AsahiLinux/linux/tree/cpufreq/v1 | |
0c4f408e TG |
13 | |
14 | 23:41 < kov> Glanzmann, hmm interesting, I'll try upgrading libinput firs then, see if that fixes it | |
15 | 23:42 < kov> it's weird because I remember the trackpad working a while ago | |
16 | 23:45 -!- mtjzh (~mtjzh@2a02:8388:1742:9b80:658f:93d3:ec68:d60e) has joined #asahi | |
17 | 23:46 < kov> yep, just upgrading to testing's libinput makes it work heh thanks Glanzmann! | |
f6f13b9e TG |
18 | |
19 | Chromium 16KB patch: https://tg.st/u/Set-kernal-page-size-to-16K-on-loongson-MIPS-archtec.patch | |
bc854271 | 20 | 10:10 < jannau> see the commit message for 64k on ppc64 https://chromium.googlesource.com/chromium/src.git/+/445c099c6486b8e5ff8dafaefcd812a7ea4bdfff%5E%21/ |
aa2187f5 TG |
21 | 15:26 < tpw_rules> Glanzmann: https://pastebin.com/NzJEQJDW - https://tg.st/u/NzJEQJDW |
22 | 15:26 < tpw_rules> last i checked the built chromium only worked with the flags --in-process-gpu --no-sandbox --no-zygote but that may have been a kernel config problem | |
f5e7256a | 23 | Upstream BUG: https://bugs.webkit.org/show_bug.cgi?id=236564 |
6de0ead9 TG |
24 | |
25 | 22:39 < jannau> `dtc -I fs -O dts -o - /proc/device-tree` will output the device-tree as seen by linux | |
54350e1e TG |
26 | |
27 | 19:11 < Glanzmann> axboe: Could you explain how to mark a device as write-through? Does that mean if I issue a sync in Linux that no flush will happen. Because this would be helpful for the m1 notebook owners to improve performance. | |
28 | 19:11 < axboe> I just do: `echo "write through" > /sys/block/nvme0n1/queue/write_cache"` for now... | |
29 | 19:11 < axboe> Glanzmann: ^^ | |
30 | 19:12 < axboe> Glanzmann: and yes, that's what it means | |
31 | 19:12 < Glanzmann> axboe: Thanks. | |
32 | 19:12 < axboe> Glanzmann: it'll bump your test case from 56 iops to 14k or something like that :) | |
33 | 19:12 < axboe> alternatively, some sort of time based hack might make sense | |
34 | 19:13 < axboe> "only issue flush if X seconds has passed since last issue" | |
35 | 19:13 < axboe> kinda nasty, but safer |