Thanks amit,
this can't be the problem. I exchanged the second parameter of the first
and the third call. The first works as before, the third does also
return EINVAL. I also changed the first '&' to some other, no change.
Any further suggestions?
Am Mi, den 09.06.2004 schrieb aksingh@hss.hns.com um 14:36:
>
>
> Hi,
>
> I think EINVAL is returned when the command code is not unique in the
> kernel, it has to be unique across all modules, so maybe you coud check if
> that is the case for your thrid command.
>
> HTH
> Amit
>
>
>
>
> Danilo Reinhardt <Danilo.Reinhardt@de.bosch.com>@nl.linux.org on 06/09/2004
> 05:27:06 PM
>
> Sent by: kernelnewbies-bounce@nl.linux.org
>
>
> To: Kernel Newbies <kernelnewbies@nl.linux.org>
> cc:
>
> Subject: ioctl and _IOx macros
>
>
> Hi folks,
>
> just a question, now i dont know what else i can do... thats the
> problem:
>
> These are the ioctl commands defined by me:
>
> #define TIS_IOC_FIRST _IOW('&', 0, struct st_cmd_createBridge)
> #define TIS_IOC_SECOND _IOW('&', 1, __u32)
> #define TIS_IOC_THIRD _IOW('&', 2, __u32)
>
> The first to are working. If i use the third, ioctl returns immediatelly
> with an error EINVAL. The drivers ioctl function ist not called.
>
> I call ioctl the same way as the second one... no difference for me...
> any ideas?
>
> Bye Dan
>
>
> --
> Kernelnewbies: Help each other learn about the Linux kernel.
> Archive: http://mail.nl.linux.org/kernelnewbies/
> FAQ: http://kernelnewbies.org/faq/
>
>
>
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/
