Hi,
I have been reading about linux kernel development and ioctl seems to be
discouraged by kernel developers.
However ioctl is precisely what i'm looking for to mimic what I have in
my Windows driver version.
Should I consider an option to implement ioctl's to change my device
settings?
Thanks,
Nuno
On Tuesday 15 November 2011 10:04 PM, Nuno Santos wrote:
Hi,
I have been reading about linux kernel development and ioctl seems to
be discouraged by kernel developers.
However ioctl is precisely what i'm looking for to mimic what I have
in my Windows driver version.
Should I consider an option to implement ioctl's to change my device
settings?
What kind of settings?
By the way give sysfs a thought.
Thanks,
Nuno
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Nuno,
On Tue, Nov 15, 2011 at 04:34:26PM +0000, Nuno Santos wrote:
Hi,
I have been reading about linux kernel development and ioctl seems
to be discouraged by kernel developers.
However ioctl is precisely what i'm looking for to mimic what I have
in my Windows driver version.
Because Linux not Windows mimicking one platform's behavior on another
is usually not the best option. We actually discouraging driver- and
vendor-specific interfaces between kernel and userspace and striving
towards drivers (both kernel- and user-space) that are able to handle
multitude of devices from different vendors.
Maybe if you provided more details about your device (what it is
exactly, what the protocol is, what exact issues you are trying to
solve) people could direct you towards some of existing solutions.
Thanks.
--
Dmitry