ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630)
Evaia63101 has quit [Quit: Hack the Gibson]
Evaia63101 has joined #aarch64-laptops
agl7 has quit [Quit: bis denne]
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
matthias_bgg has joined #aarch64-laptops
matthias_bgg has quit [Ping timeout: 480 seconds]
zjstraus has quit [Quit: Ping timeout (120 seconds)]
zjstraus has joined #aarch64-laptops
matthias_bgg has joined #aarch64-laptops
hightower3 has quit [Ping timeout: 480 seconds]
_xav_ has quit [Ping timeout: 480 seconds]
_xav_ has joined #aarch64-laptops
hightower2 has joined #aarch64-laptops
matthias_bgg has quit [Ping timeout: 480 seconds]
svarbanov has quit [Remote host closed the connection]
svarbanov has joined #aarch64-laptops
matthias_bgg has joined #aarch64-laptops
agl7 has joined #aarch64-laptops
agl7 has quit [Quit: bis denne]
agl7 has joined #aarch64-laptops
agl7 has quit [Quit: bis denne]
agl7 has joined #aarch64-laptops
init_x13s has joined #aarch64-laptops
hightower3 has joined #aarch64-laptops
hightower2 has quit [Ping timeout: 480 seconds]
init_x13s has quit [Remote host closed the connection]
init_x13s has joined #aarch64-laptops
hightower3 has quit [Ping timeout: 480 seconds]
<ajhalaney[m]>
I thought I had heard iommu.strict=0 or IOMMU_DEFAULT_DMA_LAZY=y would help with the USB speeds at agl7-x13s HdkR but I haven't used USB on this thing to verify any of that :)
hightower2 has joined #aarch64-laptops
matthias_bgg has quit [Quit: Leaving]
<steev>
jhovold: is your fix init-count imbalance patch needed, when bjorn's changes that in his patch 2 of the orientation switching stuff?
<jhovold>
steev: yes, bjorns patches should be rebased on top
<steev>
i'm sure he'll do that for v2 :)
<jhovold>
it's an old bug that has been there since forever, but we better fix it before building more stuff relying on that counter
<init_x13s>
I might have "improved" the internal keyboard responsivity by changing the keyboard interrupt to falling edge, but it's honestly hard to benchmark, fair chance it's better just in my head. It does not cause any problem however (i have been running my patch for a full week)
<init_x13s>
still, I feel like this won't get better.
<steev>
submit it upstream and see what people say :)
<init_x13s>
I lack the proper credentials to pretend I understand what I do.
<steev>
i have no idea what i'm doing 90% of the time... and got a bluetooth driver in (thanks to some wonderful code reviews), if i can do it, so can you
<init_x13s>
Modest patch here , if you want to try it
<init_x13s>
Anyways, it still seems insufficient to fully fix it. The difference between a external usb keyboard vs the internal one is still very noticeable. "aka" the external one never misses a single key. So it might need something different, and/or can't be fixed at all.
<init_x13s>
I don't trust my patch enough, and the results are imho, probably just better in my head
<HdkR>
ajhalaney[m]: My results were with using that option
<steev>
submit it anyway? worst case, they say it's wrong, best case, you improve it for everyone
<ajhalaney[m]>
HdkR: good to know, not good to hear :/
<init_x13s>
steev: alright, good advice.
<steev>
i've submitted stuff that is just "disable this for now til someone smart can look at it"