Mike Cinquino wrote: >Anders, > >Thanks, that's good info. > >After looking at the HAL_Documentation again... The answer to my >question on adding a second port jumped out at me. I don't know how I >missed it many times before. > >It looks like I want to do this: (add this to my standard_pinout.hal >file) > >loadrt hal_parport cfg="myport#_0 myport#_1 in" > > I'm glad you found it, that should work. You may want to use underscores instead of spaces though. Apparently insmod on some systems cuts off string parameters at the first space. The modified line looks like this: loadrt hal_parport cfg="port0addr_port1addr_in"
>My first port will be defaulted to an output type because I did not >specify in. My second port will be an in type because I used in after >the port number. Does this look right? > > It's safer in general to specify things instead of using defaults - that way it keep working even if the default changes: loadrt hal_parport cfg="port0addr_out_port1addr_in" >Can I start using this port after I have done this? > > Yes. It will be parport.1.xxx, as you originally thought. - Steve >Thanks, >Mike > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
