Re: Interacting with a input kernel driver from user space

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Now that i'm copying the proper amount of data I have another
> problem. I'm actually reading this attribute constantly when I open
> my control panel, however it seems that I can only have reading
> results from second to second. Is there anything that limits the
> amount of times I can push attribute data per second? I would
> definitily need at least 40 readings per second in order to have my
> data visualized in control panel.

I had overcome this problem using binary attributes. It's blazing fast now.

First I tried with a 4096 length attribute. But when I tried to transfer the whole state variable, the one that size is 40k length, I got kernel error at the middle of the transfer. My guess in that case is that the operation is not atomic and the variable was written between bin attribute read calls. Does this make sense?

Having such an attribute would really spare me a lot of time doing the control panel interaction and it would make me windows version and linux version very similiar, therefore I would use the very mechanisms.

With this said, i'm not discarding all the thing that you guys I have been telling me in the last emails and with the time I can make my head clear for structural changes in order to make this become better with the time in both OS's.

Thanks,

Nuno
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media Devel]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Linux Wireless Networking]     [Linux Omap]

  Powered by Linux