You can build yourself a FreeWing which connects to the parallel port
but you have to write the software yourself
chkcomms.com version 0.07E ©1998 K-Comm.
usage : chkcomm [switch]
switch: -P<num> PC CommsLink Port # (def=2)
CommsLink 0:300 1:310 2:320 3:330
ExStand 4:LPT1 5:LPT2 6:LPT3
FreeWing 7:LPT1 8:LPT2 9:LPT3
-T<num> Test item to use (def=0)
0: Send/Rec. test (PAR protocol)
1: Send/Rec. test (caetla)
2: Module: PortIO
3: Module: PortIOPhaseX
4: Module: SendDatas
5: Module: RecvDatas
func. : Checks communication between PC <--> PSX.
That's for suport for the Japanese PC98 standard parallel ports.
EDIT: Didn't you adapt the Linux Commlink driver for Saturn use? What changes did you have to make?
Originally posted by ExCyber@Mar 3, 2003 @ 07:15 PM
I assume that's what LPT_98 refers to. I'm a little skeptical that LPT_PC means the same, especially considering that it specifically refers to port address 0x378.
I didn't adapt the driver (for those who don't know, it's the /dev/pccl driver from Daniel Balster's psxdev), but wrote a userland utility that uses some of its low-level functions. It was largely copy/paste/edit from TyRaNiD's debugger. It can be found at my derelict, if you want to look at the code, but it's really completely unaware of the physical protocol; that's taken care of by /dev/pccl.
LPT_PC should mean the standard PC parallel ports, but it still doesn't say what interface it uses. FreeWing, ExStand, Xploder or something else?
OK, then the driver probably only provides direct access to the Commlink hardware. I remember that the documentation talks about the Caetla functions, but support for those might have been through a library.
Originally posted by ExCyber@Mar 3, 2003 @ 08:22 PM
Well, it is a Free Wing program...