I hate to cross-post, but it didn’t look like anyone was using
qdn.public.ddk
I’m modifying the UCB1300 touch driver (or any devi device/protocol combo
driver) to utilise the four extra a/d’s on the chip. To achieve this, I am
going to use devctl commands to return the current a/d value (and possibly
more exotic actions). So here’s my question:
The driver sets-up /dev/devi/touch0 and has DEVCTL_SPECIFIC_DCMD defined;
I execute:
fd = open ( /dev/devi/touch0 )
ret = devctl(fd, DEVCTL_SPECIFIC_DCMD, etc…)
but ret = ENOTTY - Inappropriate I/O control operation… what’s up?
Thanks in advance,
Mike Kadour
There was a bug where this (bogus) errno was returned in certain cases… I
forgot the details. It was supposedly fixed. What version you’re using?
“Mike Kadour” <mjkadour@uwaterloo.ca> wrote in message
news:amo6v9$qid$1@inn.qnx.com…
I hate to cross-post, but it didn’t look like anyone was using
qdn.public.ddk >
I’m modifying the UCB1300 touch driver (or any devi device/protocol combo
driver) to utilise the four extra a/d’s on the chip. To achieve this, I
am
going to use devctl commands to return the current a/d value (and possibly
more exotic actions). So here’s my question:
The driver sets-up /dev/devi/touch0 and has DEVCTL_SPECIFIC_DCMD defined;
I execute:
fd = open ( /dev/devi/touch0 )
ret = devctl(fd, DEVCTL_SPECIFIC_DCMD, etc…)
but ret = ENOTTY - Inappropriate I/O control operation… what’s up?
Thanks in advance,
Mike Kadour
\
Version 6.2.0. I’ve added a new devctl command, as indicated in the docs,
which simply prints a message to the standard out. I run the devi- with -v
which directs my other printf’s to the stdout. So the errno I’m recieving
from devctl might very well be correct - my devctl command isn’t
“recognised”.
When a devctl command is recieved by devi-, does the command somehow get
modified before being delivered to devctrl() ?
Thanks,
Mike
“Igor Kovalenko” <kovalenko@attbi.com> wrote in message
news:amp5dr$h5f$1@inn.qnx.com…
There was a bug where this (bogus) errno was returned in certain cases…
I
forgot the details. It was supposedly fixed. What version you’re using?
“Mike Kadour” <> mjkadour@uwaterloo.ca> > wrote in message
news:amo6v9$qid$> 1@inn.qnx.com> …
I hate to cross-post, but it didn’t look like anyone was using
qdn.public.ddk >
I’m modifying the UCB1300 touch driver (or any devi device/protocol
combo
driver) to utilise the four extra a/d’s on the chip. To achieve this, I
am
going to use devctl commands to return the current a/d value (and
possibly
more exotic actions). So here’s my question:
The driver sets-up /dev/devi/touch0 and has DEVCTL_SPECIFIC_DCMD
defined;
I execute:
fd = open ( /dev/devi/touch0 )
ret = devctl(fd, DEVCTL_SPECIFIC_DCMD, etc…)
but ret = ENOTTY - Inappropriate I/O control operation… what’s up?
Thanks in advance,
Mike Kadour
\