What steps will reproduce the problem?
1. calls on kernel 2.6.31.12-0.1-desktop on Suse 11.2
with glibc-2.10.1-10.5.1.x86_64 fails to pass ioctl's with command value 2
to the driver; the problem seemed to be fixed by making a transition to
more canonical ioctl definitions, but I still need to check that this
solves the problem. It is not clear where the ioctl call was trapped, but
there seems to be a conflict with the 'letter' x00 for the ioctl
definitions. Also, the parameter passing to ioctl seems not to what is
referred to as customary (i.e. passing a pointer to something only), but it
says nowhere that the exisiting usage (mostly using arg as a long int)
breaks any definitions/specifications.
What is the expected output? What do you see instead?
In a diagnostic version of the driver, it appeared that ioctls with cmd=2
never reached the driver code..
Please use labels and text to provide additional information.
Original issue reported on code.google.com by
christia...@gmail.comon 22 Feb 2010 at 4:53