Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jul 18 15:33
    @kprinssu banned @whatnameisit
  • Sep 08 2021 12:53
    @kprinssu banned @sqlsec
  • Feb 01 2021 20:01
    @kprinssu banned @kdmitrienko
  • Nov 18 2020 13:40
    @kprinssu banned @PredatorAlpha777
  • Nov 15 2020 16:16
    @kprinssu banned @nikhil19rathore99
blankmac
@blankmac
I do but I'm not at home at the moment.
Ben Raz
@ben9923
I asked him for another log with keepsyms=1 in the meantime
blankmac
@blankmac
If he has Xcode installed he could just build a release version real quick.
Ben Raz
@ben9923
He's not available for now anyway :P
CoolStar
@coolstar
@ben9923 @blankmac I can confirm btw that VoodooGPIO 2.4.0 works perfectly here, whereas even 2.4.3 was having issues with sleep/wake breaking the touchpad after some time
Ben Raz
@ben9923
@coolstar I have a fix for the cannot be used as IRQ after sleep issue
Not sure if it's the one you're referring to tho
isi95010
@isi95010
Hi all. I mentioned in the main chat that I'd like to get the Cypress running on my C720. I feel honored to be added to this chat but I'll mention that as tech savvy of an end-user as I am, I have close to 0 coding skills. As Ben suggested I plan to use the Elan satellite as an example, and somehow port the device from 1.0.4 of voodooi2c. The plan makes sense in my mind, but I don't want to bother anyone to walk me through things - perhaps if you can suggest some online learnings I could check out to put me in a position to do this effectively, I would appreciate it. On the other hand, if anyone does have time to do it, I am available to test.
Ben Raz
@ben9923

Read the IOKit reference as a start, make sure you're familiar with C/C++
Then read the old Cyapa code, make sure you understand it
Then read the VoodooI2CELAN code and understand how a satellite works (Might want to read device nub code either?)
You might want to look at the old ELAN code for reference...

Finally, port the code. Looking at the ELAN diff should give you a better idea on how it should work.

isi95010
@isi95010
Thanks!
Ben Raz
@ben9923
Sure :)
blankmac
@blankmac
@coolstar no issues here with any version.
granted, my touch pad is USB tho.
@isi95010 Don't be discouraged or overwhelmed. I started at ground zero myself in the code department with the VoodooI2C project a few years ago.
krycho74
@krycho74
@blankmac Hi, are you developing your alps touchpad project? Would you have some time now and would like to experiment with my touchpad?
blankmac
@blankmac
@krycho74 All I did was update it to comply with the changes in VoodooInput. I'm really not too interested in trying to develop for hardware I don't have on hand, sorry. Hackintoshing, as a whole, is reaching the end of the road with Apple's move back to proprietary chips.
blankmac
@blankmac
Hey guys, seems the old methods of live logging to the console from the kernel don't work anymore (ie - IOLog). I'm trying to chase down this problem and would like to output some of the input data live -- blankmac/AlpsT4USB#7
Any advice?
Avery Black
@1Revenger1
I was having a similar issue with VoodooRMI - I ended up adding a prefix to all the logging data using a pre-processor macro so that all my debug statements began with "VRMI - " and then used sudo dmesg
you generally will want to use the boot-arg msgbuf=1548576 as well to increase the max size of the dmesg buffer. That's the best way I've found, though I would like iolog to work again ;-;
oops, msgbuf should be 1048576, not the number I gave before
Ben Raz
@ben9923
@blankmac I’ve been asking users to attach dmesg logs for a while now
An alternative to the boot arg should be injecting DebugEnhancer.kext. IIRC it allows an even bigger buffer for logs (it’s patching the kernel after all).
We should add it to our docs.
zhen-zen
@zhen-zen

Any advice?

Honestly, life could be much easier debugging with Catalina. Specifically the live monitor part. The dmesg don't support -w and the watch command is still unsatisfying.

blankmac
@blankmac
Ok, that was enough to get me the info I needed. Thanks guys.
Leonard Church
@343iChurch
Hiya. So I have a unique scenario in which my laptop has a PS/2 keyboard but an I2C touchpad. I cannot get them both working consistently due to conflicts between the kexts -- when the touchpad works, the keyboard is disabled until a wake/sleep cycle. Is there a way to properly use both VoodooI2C and VoodooPS2?
Kishor Prins
@kprinssu
@343iChurch wrong channel, please use VoodooI2C, there really isn't an issue with a PS2 keyboard and a I2c trackpad, there's probably something else going on
Leonard Church
@343iChurch
@kprinssu gotcha, thanks. Sorry, thought I was in the other channel.
Kishor Prins
@kprinssu
@zhen-zen CI is broken due to cldoc not being maintained any more and cpplint requires Python 3
it's dependency hell
zhen-zen
@zhen-zen
lol, that also blocks Xcode build for beginner
Kishor Prins
@kprinssu
@ben9923 put up a fix for the CI, builds should be working
Avery Black
@1Revenger1
https://github.com/VoodooI2C/VoodooI2CHID/pull/52/files
Not sure how you guys feel about gotos, but this seems like a weird usage of them. Don't know if you guys want them or not
Ben Raz
@ben9923
@1Revenger1 Code should probably refactored into a different event driver anyway.
It's basically a copy-paste of VoodooI2C/VoodooI2CHID#3, that wasn't merged due to code style (and maybe the fact it's in the multitouch code) issues
Avery Black
@1Revenger1
@ben9923 I updated the PR again reworking the I2C section: https://github.com/dortania/Getting-Started-With-ACPI/pull/42/files
I ended up just going back to _OSI to XOSI or creating your own OSYS variable within I2C0/1/2 or whatever
We weren't able to figure out any other better way to do. I'd make a Lilu plugin for it, but this occurs way too early for me to use Lilu with it
Andrea Somaini
@thegoldgoat
Hello everyone, I wanted to write a devide driver for a virtual multitouch touchpad on macOS. I’ve been prompted to take a look at VoodooInput, but I still don’t understand how to build/test a kext effectively. After disabling SIP it looks like I need to reboot every time I rebuild a kext, is there a faster way to install/test during development? Thanks in advance :)
Avery Black
@1Revenger1
Do it in Catalina, you can live load/unload kexts
Big Sur is just a giant pain to develop in tbh because of the newer kernelcache
Andrea Somaini
@thegoldgoat
Oh I see, that’s really unfortunate
Thanks a lot ;)
Andrea Somaini
@thegoldgoat
Another thing: my goal was to eventually be able to distribute some user-installable app, should I use DriverKit instead of a kernel extension? Maybe the whole process would be easier that way
Avery Black
@1Revenger1
DriverKit is only going to work for 10.15+, so if you want to support 10.11-10.14, you have to use IOKit
I don't have much experiance with DriverKit tbh, I know VoodooInput is in kernel space though
Andrea Somaini
@thegoldgoat
Alright, thanks again :)
Kishor Prins
@kprinssu
@thegoldgoat VoodooI2C, VoodooRMI, and VoodooSMBus all have working examples of VoodooInput integrations
if you want to look driver development, look at Apple's IOKit development docs (though it's deprecated now and will be removed as Apple pushes people to use DriverKit)
Andrea Somaini
@thegoldgoat
@kprinssu Yeah Apple is really pushing DriverKit, indeed that's what I ended up using. The difference with IOKit in terms of API looks very subtle to me BTW
shiecldk
@shiecldk
Hello, I'm trying to fix the stylus issue in VoodooI2C. Could someone point me which portion of the code I can work on? I am hoping to contribute to VoodooI2C with my programming experience if no one can fix it. I found the multitouch gesture is not working on the touchscreen with the stylus pen on the secondary screen in my ASUS ZenBook Pro Duo 15 (has the main 4k and secondary touchscreens. Only the cursor and click functions work. (multi touch, scroll, and hold to drag/right click functions are not available.) The secondary touchscreen comes with stylus pen and support multi touch in Windows 10 and Ubuntu). I have tried disconnected the main touchscreen (unplug the eDP connector from MB), and had only the secondary screen in macOS 10.15.7. However, the issue remains the same. (only the cursor and click functions work.)