Age | Commit message (Collapse) | Author | |
---|---|---|---|
2017-12-20 | Use backticks around types/functions in docs | Bryant Mairs | |
2017-12-20 | Make numeric literals easier to read | Bryant Mairs | |
2017-12-04 | Stop reexporting `Errno` and its variants | Jonas Schievink | |
cc #664 (unsure if this is everything needed) | |||
2017-07-21 | Allow doc attributes in ioctl macro | roblabla | |
2017-07-19 | Refactor ioctl! for buffers | Bryant Mairs | |
Instead of relying on the macro user to calculate the length in bytes do that within the macro itself | |||
2017-07-19 | Add 'bad' prefixes for read, write_*, and readwrite ioctls | Bryant Mairs | |
2017-07-19 | Split ioctl!(write ...) into write_ptr and write_int | Bryant Mairs | |
There two different write semantics used with ioctls: one involves passing a pointer the other involves passing an int. Previously the ioctl! macro did not distinguish between these cases and left it up to the user to set the proper datatype. This previous version was not type safe and prone to errors. The solution here is to split the "write" variant into a "write_ptr" and "write_int" variant that makes the semantics more explicit and improves type safety by specifying arguments better. | |||
2017-07-19 | Unify argument names to generated ioctl functions | Bryant Mairs | |
2017-07-19 | Remove unnecessary constants | Bryant Mairs | |
2017-07-19 | Use the proper ioctl number type depending on target | Bryant Mairs | |
This also means that we need to properly mask off bits to the valid range of ioctl numbers. | |||
2017-07-19 | Remove ioc_* functions | Bryant Mairs | |
These are low-level functions that shouldn't be exposed | |||
2017-07-19 | Revise ioctl module documentation | Bryant Mairs | |
This refactors the examples to more directly address the exact use cases for the `ioctl!` macro that `nix` provides. Additionally other macros that should not be used by end users are no longer discussed. | |||
2017-07-19 | Remove unnecessary path aliasing | Bryant Mairs | |
2017-07-19 | Hide internal macros/types within ioctl | Bryant Mairs | |
2017-07-19 | Add a "bad none" variant to the ioctl macro | Bryant Mairs | |
2017-07-19 | Re-add bad variant of ioctl! | Bryant Mairs | |
2017-07-19 | Remove old workaround | Bryant Mairs | |
2017-07-08 | Enable ioctl on mips64 and s390x | Bryant Mairs | |
2017-07-05 | We need to pass by value and not by pointer for writing ioctls | Bastian Köcher | |
2017-06-19 | Support powerpc64 | Luca Barbato | |
The test_ioctl values are computed using ioctl-test.c | |||
2017-04-21 | remove test warnings | king6cong | |
2016-12-10 | Add ioctl support for BSD | Conrad Kramer | |
2016-12-10 | Change the readwrite buf ioctl call to use a *mut pointer | Conrad Kramer | |
2016-12-10 | Fix typo in documentation | Conrad Kramer | |
2016-01-28 | Errno::result() | arcnmx | |
2015-11-20 | netbsd support | Jeremy Fitzhardinge | |
2015-09-15 | ioctl: only run ioctl doctest under linux | Paul Osborne | |
2015-09-15 | ioctl: correct documentation and add example ioctl! code | Paul Osborne | |
2015-09-15 | ioctl: make ioctl functions public | Paul Osborne | |
Consumers of the API may control visibility by means of a module. The following is a useful pattern that may be used by implementors (here for a couple of i2cdev ioctl definitions): mod ioctl { ioctl!(bad set_i2c_slave_address with super::I2C_SLAVE); ioctl!(bad i2c_smbus with super::I2C_SMBUS); } This resolves #184. | |||
2015-09-15 | ioctl: clean up source file for ioctls | Paul Osborne | |
Readability was unecessarily impaired via a myriad of attributes to hide constants from the documentation. If these attributes are exposed publically, including them in the documentation makes sense. | |||
2015-08-14 | ioctl: fix bugs with op generation for writes | Paul Osborne | |
These had ior! rather than iow! previously. ior! is obviously not correct for write operations. | |||
2015-08-14 | ioctl: do not make macro generated functions public | Paul Osborne | |
if code incorporating these macros wants to publicly export the functions they may do so by doing the following: pub ioctl!(...); Since the functions are unsafe, in many cases exposing the functions publicly will not be desirable. | |||
2015-08-12 | ioctl: remove defunct readme for ioctl subsystem | Paul Osborne | |
2015-08-12 | ioctl: return result type rather than raw integer | Paul Osborne | |
This change also adds macro usages in the tests. Nothing is asserted but the use of the macros provides a basic compile-time check that is otherwise missing. Signed-off-by: Paul Osborne <osbpau@gmail.com> | |||
2015-08-12 | ioctl: reintroduce libc ioctl workaround until we can use updated liblibc | Paul Osborne | |
This PR fixes the issue upstream https://github.com/rust-lang/rust/pull/26809 but no version 0.2.0 of the crate has been published as of yet. Signed-off-by: Paul Osborne <osbpau@gmail.com> | |||
2015-08-12 | ioctl: remove all but command encoding | Corey Richardson | |
2015-08-12 | Merge mips into powerpc; rename Union_Unnamed16 to ff_effect_data | Corey Richardson | |
2015-08-12 | Update docs | Corey Richardson | |
2015-08-12 | Completely revamp sys::ioctl to use cmr/ioctl's approach | Corey Richardson | |
This is more type-safe. Also, the old code wasn't cross-platform at all even though it claimed to be. It wasn't even portable across architectures on Linux. |