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)
<harvestz[m]>
does anyone use binary ninja or ida pro on the x13s?
<harvestz[m]>
or I guess, ghidra
<steev>
ghidra, here and there, by no means an expert
<harvestz[m]>
how does it run on there? I use the collab feature for work but generally use ida pro or binary ninja
<harvestz[m]>
and import my work into ghidra to commit
<harvestz[m]>
wasn't too happy about function detection for ghidra and didn't want to learn how to write plugins in it
<steev>
if you're asking in windows, no idea, in linux... it seems to work fine for my needs
<harvestz[m]>
yeah in linux of course - I don't have windows on there :p
<Caterpillar>
[19:52] <steev> Caterpillar: what is PAC? || jlinton knows that well
<Caterpillar>
from #fedora-arm Libera.chat channel
<steev>
that.... doesn't help at all
<steev>
who is jlinton and why should i go ask them what pac is when you asked?
<harvestz[m]>
I likely found their GitHub since they use the same username in multiple places https://github.com/jlinton
<steev>
that still doesn't get closer to the answer of "what is PAC?"
<harvestz[m]>
not at all lol, I looked around there too
<HdkR>
I doubt Binja or Ida will work on Linux. Do they even provide ARM64 binaries?
<harvestz[m]>
I mean I know they work on linux but was wondering about he arm part of it lol - like what people's setup was
<HdkR>
I know FEX-Emu can run them, but I doubt you'd be happy with the performance currently
<harvestz[m]>
if anyone has asked for a linux arm build (from binja) - I'm in the binja slack and a discord with Jordan
<HdkR>
Tell Andrew that Ryan Houdek would also want an ARM64 Linux build
<harvestz[m]>
I'm not familiar with Andrew only Jordan from binja lol
<harvestz[m]>
but I can let you know the response I get!
<steev>
as a kali dev, an arm64 linux build of binja would be nice
<harvestz[m]>
okay here's their response: "There is no public release yet; but we have been playing with Linux arm build internally and it is promising!"
<HdkR>
Hopefully they don't do a silly thing and hardcode a 4k page size requirement :P
<steev>
maybe they're waiting on PAC
<harvestz[m]>
the main reason I'm asking about this is because I'm looking to grab a personal license for personal work at home (I don't want to use my work license on my personal machines)
<harvestz[m]>
trying to figure out which to get!
<harvestz[m]>
binja wins lol, sounds like linux arm will get a public release eventually
<steev>
well, ghidra doesn't require any at all
<HdkR>
Ghidra's UI is so ugly that I'm fine with paying for Binja
<HdkR>
Binja also almost always is maxing out my desktop's 128GB of ram
<harvestz[m]>
yeah the main draws for binja > ghidra for me is the ui and api
<steev>
kali's arm64 build now has all the natives built too
<steev>
wifi is very meh for me on 6.2.0-rc1, i'm going back to -next
<steev>
hopefully, new year, new firmware
<HdkR>
steev: How's Ghidra's multithreaded analysis? That's one of the major selling points of Binja
<HdkR>
I upgraded my desktop's CPU and it cut the ELF analysis time to a quarter
<steev>
i don't have anything to compare it to, so i can't say :D
<HdkR>
I should install it just to see how long it takes
<steev>
i don't run it on the thinkpad, only on my rock-5b
<jhovold>
steev: the latest next was released about the same day as 6.2-rc1 so there should not really be anything of worth in next which isn't already in rc1. The diff is small and nothing stands out in the logs based on a quick look.
SSJ_GZ has quit [Ping timeout: 480 seconds]
<HdkR>
steev: Seems like Ghidra hardly threads at all. Its disassembler is burning about 1.4 cores on my system. Will probably take a day to analyze libLLVM
<HdkR>
For comparison's sake, it took 56 minutes for Binja to analyze livLLVM-15.so fully
<HdkR>
Curiously it does spin up 10 decompilers later on, which doesn't seem to be an option that can be configured.
systwi has quit [Read error: Connection reset by peer]
systwi has joined #aarch64-laptops
SSJ_GZ has joined #aarch64-laptops
Vectorboost has joined #aarch64-laptops
Vectorboost has quit [Quit: Leaving]
<steev>
jhovold: i'm not sure why it is either, and i looked over the wireless patchwork just to see and nothing stood out there either, i just know with 6.2 rc1 i have a hell of a time connecting to my wifi network, and have to remove and re-insert ath11k_pci multiple times to get a connection and it still randomly stops passing traffic. have tried with both limiting it to 2.4GHz only as well as letting it decide which to connect to
<steev>
maybe when kalle comes back from vacation this time, he'll finally find us a board file that works :)
<jhovold>
steev: fingers crossed :)
<steev>
jhovold: and i really dunno how i went down the ivo m133 wormhole
<bamse>
jhovold: not sure how i didn't realize before...but i apparently have "alternative touchpad" on both my x13s
<bamse>
jhovold: seems like your irq improvements work :)
<steev>
jhovold: your and abel's thing is really bothering me, and now i'm wanting to know how i was so far off
<steev>
just checked the flex5g thinking maybe it was that, but that's a B140HAN06.4
<steev>
oh, i think i might have mixed up the c630 and the thinkpad; because the c630 starts with M133NW
<steev>
mixed up/transposed?
<jhovold>
bamse: yeah, the irq-mapping race is quite easy to trigger if you drop those patches
<jhovold>
steev: or you just looked at the wrong line in that table abelvesa found?
<steev>
jhovold: actually, i looked on panel-look for IVO M133NW4 and found the one that was 1920x1080 and wasn't touch screen (back when I thought they'd sent me one without touchscreen but it turns out it's just that something isn't right with our touch screen and we have to manually bind it)
<steev>
and also matte, not glossy
<jhovold>
steev: yeah, that's low prio bug we need to look closer at at some point. hopefully noone uses touchscreen anyway. :)
<steev>
only clover complains about it :P
<steev>
i tested the i2c patches that someone had posted (i can't recall name, Brian?) but that didn't change the status quo
<steev>
didn't break things further though :)
<jhovold>
steev: yeah, that was just a rename of the buses. May need to update the instruction on that wiki page if the controller id changed
<jhovold>
because of the i2c aliases Brian added
<steev>
hm, i'll have to re-apply and double check, but i'm pretty sure i followed the wiki instructions when the touchscreen didn't work on its own
<steev>
i also need to go back through the backlog and find where bamse said check in my XXXXXX trees for possible usb-c flippy issues fix
<bamse>
steev: which flippy issue?
<steev>
Where usb c devices only work when flipped 1 way
<bamse>
ahh...
<bamse>
i shuffled my desk...and i have one of those really thick usb-c cables...and it doesn't want to twist 180...so i guess i have to fix that now...
<steev>
Was gonna see if that would help with the usb c devices flipped wrong way block Wi-Fi from working
<steev>
I should shuffle my desks around
<bamse>
i'll try to shuffle them control bits for you in the meantime ;)
<bamse>
although first i need lunch and play some video games
<steev>
heck yes
<steev>
although all i've been playing lately is lost ark, mostly because i can login, do things and then log out