On 12/15/2017 07:22 AM, Mark wrote:
Doesn't it still need a devlink in the /dev folder? The
device parport0 shows up there. Neither one of the cards,
either the old one or the new one, show up using ppdiag or
ptest (the hal script for testing parallel ports).
Running ppdiag shows only one card, the one on the mobo.
It shows neither the old card or the new. Running ptest it
fails when it tries to load a parport.1 read. According to
lspci, I've got ccf0 and ccf8 to play with. And yes, I
know I don't want the regular lp driver to be used.
The LinuxCNC drivers don't actually need such a link, as
they manipulate the hardware registers directly. However,
they MIGHT need the /dev link to accept the port address.
There is code that asks the lp driver (or something in the
OS) to permit exclusive access to the port, and if the link
doesn't exist, then that function may not work.
Can you post the output from lspci -v related to the port in
question? Some sicko multi-I/O chips (or their config ROMs)
give bad info to the PCI enumerator, and that may be the
cause here. I had one parport-only card that identified as
a serial I/O. If you forced your way past that, it actually
worked as a plain parport, but not EPP. But, clearly
identifying the port incorrectly as serial, not parallel,
the enumerator would give it the wrong /dev link.
Jon
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
