Hi List,
I just wonder how an out-of-band condition is defined? QNX online docs state
that “the definition of out-of-band data depends on teh resource manager”.
But I don’t know how.
I am writing a resource manger for a serial printer. When the printer has
fault or error, I expect one or more units of out-of-band data should be
availabe. But it didn’t seem to happen as my client code
ionotify(fd, action, _NOTIFY_COND_OBAND, NULL)
didn’t get this condition.
Should I set up something to make out-of-band data happen? Thanks for your
help.
Best Regards,
Luke
As for devc-ser8250, AFAIK, out-of-band data are error codes from line
status register of UART
(may be shifted/masked somehow)
So, if any line error occures, driver puts nothing to input buffer, but
puts error code to out-of-band buffer
Then you can get it using devctl()
ionotify for out of band data is not implemented, i think, at least in that
ddk version
Artem
“Luke Wang” <luke.wang@transcore.com.au> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ
ÓÌÅÄÕÀÝÅÅ: news:b3ek6k$n1c$1@inn.qnx.com…
Hi List,
I just wonder how an out-of-band condition is defined? QNX online docs
state
that “the definition of out-of-band data depends on teh resource manager”.
But I don’t know how.
I am writing a resource manger for a serial printer. When the printer has
fault or error, I expect one or more units of out-of-band data should be
availabe. But it didn’t seem to happen as my client code
ionotify(fd, action, _NOTIFY_COND_OBAND, NULL)
didn’t get this condition.
Should I set up something to make out-of-band data happen? Thanks for your
help.
Best Regards,
Luke
Thanks for the info. So a resource manager programmer cannot really define
out-of-band data unless his code gets down to socket or chip register level.
Just wonder what QNX doco means by saying “the definition of out-of-band
data depends on the resource manager”…
“Artem Smolenkov” <artemDEL@DELmutex.ru> wrote in message
news:b3httk$hn3$1@inn.qnx.com…
As for devc-ser8250, AFAIK, out-of-band data are error codes from line
status register of UART
(may be shifted/masked somehow)
So, if any line error occures, driver puts nothing to input buffer, but
puts error code to out-of-band buffer
Then you can get it using devctl()
ionotify for out of band data is not implemented, i think, at least in
that
ddk version
Artem
“Luke Wang” <> luke.wang@transcore.com.au> > ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ
ÓÌÅÄÕÀÝÅÅ: news:b3ek6k$n1c$> 1@inn.qnx.com> …
Hi List,
I just wonder how an out-of-band condition is defined? QNX online docs
state
that “the definition of out-of-band data depends on teh resource
manager”.
But I don’t know how.
I am writing a resource manger for a serial printer. When the printer
has
fault or error, I expect one or more units of out-of-band data should be
availabe. But it didn’t seem to happen as my client code
ionotify(fd, action, _NOTIFY_COND_OBAND, NULL)
didn’t get this condition.
Should I set up something to make out-of-band data happen? Thanks for
your
help.
Best Regards,
Luke
\
“Luke Wang” <luke.wang@transcore.com.au> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ
ÓÌÅÄÕÀÝÅÅ: news:b3k0a5$s70$1@inn.qnx.com…
Thanks for the info. So a resource manager programmer cannot really define
out-of-band data unless his code gets down to socket or chip register
level.
Just wonder what QNX doco means by saying “the definition of out-of-band
data depends on the resource manager”…
Well, that was just an example. IMHO, one can use his own definition in his
resource manager,
doesn’t matter how close to hardware it is.
Or add something to existing for char devices, e.g. specific error codes.
Artem