On 11/19/2015 10:20 PM, Jeshua Lacock wrote: > On Nov 19, 2015, at 2:05 PM, Todd Zuercher <zuerc...@embarqmail.com> wrote: > >> Are you sure that is actually the right listing for your pci card? > > Hi Todd, > > Yes, I am sure, if the card isn’t in the machine the listing isn’t there. > >> The listing for my card (albeit a different card) is. >> >> Try the command >> $ cat /proc/ioports | grep parport >> >> >> My system show this for the above command. >> 0378-037a : parport0 >> e030-e032 : parport2 >> e050-e052 : parport1 > > I have some ports shown for the address expected (from lspci) but they aren’t > labeled as yours: > > d000-dfff : PCI Bus 0000:04 > d000-d0ff : 0000:04:00.0 > d100-d103 : 0000:04:00.0 > > It is interesting to me that your lspci listing indicates "Kernel driver in > use: parport_p” whereas my card does not. I guess Ubuntu must not even > recognize it as a parport. I didn’t have any luck with trying to use the > address ranges shown to connect or set it to epp with the showport utility. > Oh, oh! If the Linux kernel does not recognize it as a parallel port, (probably because the card's BIOS extension ROM code is buggy) then the extended control registers won't be declared in the BIOS area at boot time. Thus, the various LinuxCNC drivers that try to intelligently handle the parport (such as select EPP mode) will not work properly.
You might still be able to make this card work with various tricks like my pcisetup program (but you have to know the address of the ECR register to do that). This card may just be totally oddball, and only the specific Windows driver for that card knows what to do with it. There ARE standards, but a lot of outfits choose to not follow them. Jon ------------------------------------------------------------------------------ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
