We need to connect some our device to the LPT port of a QNX v4.25G host.
When we boot the host on windows - everything works fast and reliable.
Does Dev32.par v4.25A support EPP, ECP or just legacy output-only hardware?
I’m looking into
ftp://ftp.qnx.com/usr/free/qnx4/os/samples/Dev_drivers/Dev.par.tgz, this
version does not use hardware interrupts at all.
What is the proper way of achieving the maximun throughput on LPT without
burdening the CPU? Should I write the driver of my own?
“Tony” <mts.spb.suxx@mail.ru> wrote in message
news:opr67qi6woo93ri4@inn.qnx.comnews.mail.ru…
We need to connect some our device to the LPT port of a QNX v4.25G host.
When we boot the host on windows - everything works fast and reliable.
Does Dev32.par v4.25A support EPP, ECP or just legacy output-only
hardware?
There it no support for EPP ECP or any other more “advanced” method.
I’m looking into
ftp://ftp.qnx.com/usr/free/qnx4/os/samples/Dev_drivers/Dev.par.tgz> , this
version does not use hardware interrupts at all.
Indeed, because there is not EPP/ECP support using interrupt when overwelm
the CPU
What is the proper way of achieving the maximun throughput on LPT without
burdening the CPU? Should I write the driver of my own?
Yes looks like writing you own driver is the only way. You could set
Dev32.par at low priority and let it use all the CPU it wants, that’s still
pretty fast without having impact on the general behavior of the machine.