evdev support has been added to FreeBSD recently, so tslib now can be used there. This pull requests contains following changes:
input-raw plugin and executables were tested on both Linux and FreeBSD and found no regression.
Unfortunately I don't have hardware to test galaxy-raw and touchkit-raw plugins.
Hi @gonzoua There's no need to have the hardware for the hardware-plugins. I can't test it, but this is great!
I want to schedule this for tslib 1.3. I plan to do a 1.3-rc release not too long after 1.2 and this would be a good addition there.
which of your branches is appropriate to merge for freebsd support? freebsd or freebsd-support-pr?
Thanks for merging this pull request. freebsd-support-pr is the branch with cleaned-up version.
I resolved conflict with upstream master so the branch now can be merged automatically
Fix printing struct timeval on FreeBSD
Do not use format that assumes the type of tv_sec and tv_usec,
instead use %jd and cast those fields to intmax_t
Remove unused headers
Fix path to input.h on FreeBSD
Set c_line only on Linux
Add fbutils support for FreeBSD
- Rename fbutils.c to fbutils-linux.c to indicate that it's
- Add fbutils-freebsd.c that implements fbutils API for
- Add autoconf conditional to compile either of fbutils
implementation based on target OS
sorry, your pull request doesn't apply anymore. I know you put work into it to update it. I'm no so sure about FreeBSD support right now. I think we got more Linux-dependent with my latest additions, and your fbutils seems like quite some code duplication (without going into details, I might be wrong too).
In general, FreeBSD would be nice to have if it'd be a little "cheaper". But I have the feeling it's more work now.
Most of the newly introduced conflicts/incompatibilities are easy to solve. I'll look into it and I will try to reduce code duplication in fbutils
i took one more of your changes and added some more include paths.
It seems that there's mainly fbutils to take care of, if you want freebsd.
I applied your fbutils-bsd addition anyways, in a slightly updated way. I hope that's fine with you. Thanks again!
Thanks a lot Martin. I apologize for dropping the ball on this one. I will check what's there left to merge/fix, and open new pull request when code is ready.