Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 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
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.)
shiecldk
@shiecldk
@kprinssu Thank you so much for pointing these out. I'll start looking into the code from here.
shiecldk
@shiecldk
Sorry for a stupid question. Could I ask what is wrapper in VoodooI2C and where does VoodooI2CMultitouchHIDEventDriver check for stylus and decide whether to disable multitouch functions?
Avery Black
@1Revenger1
I don't think that MultitouchHIDEvent checks for a stylus, it's a usage pair
though, I could be wrong
shiecldk
@shiecldk
Also I'm sure what wrapper means, I keep seeing it in MultitouchHIDEvent and StylusHIDEvent
https://github.com/VoodooI2C/VoodooI2CHID/blob/master/VoodooI2CHID/VoodooI2CMultitouchHIDEventDriver.cpp#L685-L699
shiecldk
@shiecldk
@1Revenger1 Is it possible compile VoodooI2C in Catalina or Big Sur? I see a compiling error "'IOKit/IOLib.h' file not found" in my Xcode.
zhen-zen
@zhen-zen
Clone MacKernelSDK to your project folder
zhen-zen
@zhen-zen
Is it inside the VoodooI2C folder?
➜  VoodooI2C git:(master) ls
Dependencies          Multitouch Support    VoodooI2C Satellites
Documentation         README.md             VoodooI2C.xcworkspace
LICENSE.txt           Utilities             docs
MacKernelSDK          VoodooI2C
shiecldk
@shiecldk
Yes I fixed it. However, there is another error I'm fixing now
/Users/username/Library/Developer/Xcode/DerivedData/VoodooI2C-brfmrnnidcznlxgxjrczhdfukmxm/Build/Intermediates.noindex/VoodooI2C.build/Release/VoodooI2C.build/Script-ACA4A00D21E25F0E00A91B61.sh: line 2: cpplint: command not found
Command PhaseScriptExecution failed with a nonzero exit code

you need to install cldoc from https://voodooi2c.github.io/ and other dependencies.

I'm trying to figure out how to install cldoc

Avery Black
@1Revenger1
tbh, I just built VoodooI2CHID alone by opening up that project within the satellite folder
don't need cpplint or cldoc for that
shiecldk
@shiecldk
Yes the build is successful now. Thanks for opening the door for me to this project
shiecldk
@shiecldk
I checked with the debug. It looks like VoodooI2CHID only detects one finger/one point how so ever I touch the secondary screen (with stylus function) with multiple fingers. Is this a bug in the VoodooI2CTouchscreenHIDEventDriver.cpp or/and VoodooI2CMultitouchInterface.cpp?
@zhen-zen I saw your commit in https://github.com/VoodooI2C/VoodooI2CHID/pull/36#issuecomment-643612068
Do you have any idea how to debug or fix this issue? Thank you.
shiecldk
@shiecldk
Also, I put some IOLOG to check which lines were loaded; it looks like VoodooI2CTouchscreenHIDEventDriver.cpp was able to detect whether the touch is triggered by finger or the stylus pen. However, it's always been recognized as one point contact no matter how many fingers I used to touch that screen.
shiecldk
@shiecldk
Actually it looks like VoodooI2CMultitouchInterface.cpp was not used even for the main touchscreen, which the multitouch gesture works. Does that mean it's actually the VoodooI2C.kext instead of the satellite driver VoodooI2CHID.kext handling multitouch service?
PS. Sorry for sending so many messages at the same time for this debug.