Chris Morley wrote: > Can there be multiply parallel port boards (assuming multiply pports on > computer?
Yes, the hostmot2 driver supports up to four 7i43 boards, each on its own EPP parport. If you're feeling frisky you can increase the number of boards supported by changing the HM2_7I43_MAX_BOARDS constant in hm2_7i43.h and recompile... But if you need that much I/O you're probably better off buying a PCI board or two. > - How does the BoarNum system work? > Does it always go up with the second board or only when the > boardtype and/or firmware are the same? Each board type (7i43, 5i20, 5i23, etc) has its own BoardNum counter. All BoardNums start at 0 and increment once for each board it successfully initializes. So if your computer has two 7i43s, three 5i22s, and one 3x20, they'll be named hm2_7i43.0, hm2_7i43.1, hm2_5i22.0, hm2_5i22.1, hm2_5i22.2, and hm2_3x20.0. That numbering is independent of what firmwares are loaded on those boards. Note that the 5i22 and the 3x20 are both handled by the hm2_pci driver; the BoardNum is per board type, not per driver. Some AnyIO boards are available with different FPGA sizes - the 5i22 with 1.0 or 1.5 Mgates, and the 3x20 with 1.0, 1.5, or 2.0 Mgates. All the boards of a "family" (such as 5i22 or 3x20) share a BoardNum counter, it is *not* split up by FPGA size. I hope that makes sense. > - If a system has a parallel port and a pci board, does it matter what > order they are loaded? No, with one parport board and one pci board there can be no confusion, since they are handled by different drivers (hm2_7i43 and hm2_pci, respectively), and each driver gets its own "config" modparam. Things do get a bit confusing when you try to control multiple boards with a single driver module, for example if you have two 5i20s or two 7i43s. In that case you supply an array of config modparam strings, one per board, using a syntax like config="for-one-board","for-another-board". This works ok with the hm2_7i43 driver, since you give it "ioaddr" and "ioaddr_hi" modparams in addition to the config modparam, and the config strings apply in the same order as the ioaddrs. It's more annoying with the hm2_pci driver. I don't know of a way to tell, without just trying it, which string goes to which board. It depends on in which order the kernel hands the boards to the hm2_pci driver. This ordering is the same each time the driver loads, so once you figure it out you're good to go. I know this is not ideal, it would be better to explicitly say "the board at PCI address X gets the config string Y", but that's not implemented yet... -- Sebastian Kuzminsky the last of the V8 Interceptors ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
