From: Jean T. <jt...@bo...> - 2002-03-27 02:20:49
|
Felix Tang wrote : > > It is setup to just take Rx, Tx, DTR, and RTS from the serial port. It in > fact only really needs the Rx and Tx from the App Notes. How do you set the speed (baud rate) in the chip ? I guess there must be some magic commands/pins whatever. How does the chip gets its power ? How does the chip gets reset ? > From this information, does it make sense that the IrTTY driver would work > with the MCP2120 (it's just serial data right?)? Once you figure out how to reset the chip and set the speed, you just need to write a dongle driver (have a look at actisys.c/esi.c/litelink.c). Good luck... Jean |
From: Felix T. <ta...@ee...> - 2002-03-27 03:31:43
|
Thanks for the response. It actually worked for me as I expected (lucky me). It only needed Rx and Tx. I just did irattach /dev/ttyS0 -s 1 and it worked. In this case the baud rate was set to 9600 baud at the chip. It just worked. However, I have read in the application note (an756). There is a software data rate selection mode. You can put the device in command mode and then change the baud rate through the serial port. It works with Microsoft Windows 95,98 and ME. "The software data select mode is compatible with the Microsoft CRYSTAL.VXD driver ... " I figure some of the existing irda drivers for linux might do this (and then I can reflect the changes in the hardware). So I wanted to ask about that. Since, the autonegotiation must work through some method. Default to 9600 and the up it till you max out or break the connection? Seems like I'll be able to send squirts in a bit. ;) I'll just hardcode the baudrate to 9600 but I'd like to have it go upto 115200, that would be nice. Thanks, Felix On Tue, 26 Mar 2002, Jean Tourrilhes wrote: > Felix Tang wrote : > > > > It is setup to just take Rx, Tx, DTR, and RTS from the serial port. It in > > fact only really needs the Rx and Tx from the App Notes. > > How do you set the speed (baud rate) in the chip ? I guess > there must be some magic commands/pins whatever. > How does the chip gets its power ? How does the chip gets > reset ? > > > From this information, does it make sense that the IrTTY driver would work > > with the MCP2120 (it's just serial data right?)? > > Once you figure out how to reset the chip and set the speed, > you just need to write a dongle driver (have a look at > actisys.c/esi.c/litelink.c). > > Good luck... > > Jean > > _______________________________________________ > irda-users mailing list > ird...@li... > https://lists.sourceforge.net/lists/listinfo/irda-users > |
From: Jean T. <jt...@bo...> - 2002-03-27 03:38:14
|
On Tue, Mar 26, 2002 at 10:31:31PM -0500, Felix Tang wrote: > Thanks for the response. It actually worked for me as I expected (lucky > me). It only needed Rx and Tx. I just did irattach /dev/ttyS0 -s 1 and it > worked. > > In this case the baud rate was set to 9600 baud at the chip. It just > worked. However, I have read in the application note (an756). There is a > software data rate selection mode. You can put the device in command mode > and then change the baud rate through the serial port. It works with > Microsoft Windows 95,98 and ME. Yes, that's exactly what I was refering to. Read those precious instructions, they will enable you to write the dongle driver you need. > "The software data select mode is compatible with the Microsoft > CRYSTAL.VXD driver ... " > > I figure some of the existing irda drivers for linux might do this (and > then I can reflect the changes in the hardware). So I wanted to ask > about that. Well... Not sure. Just have a look in the source code (each dongle driver is between one and two pages of source in Linux). > Since, the autonegotiation must work through some method. > Default to 9600 and the up it till you max out or break the connection? No, there is a single negociation. The default rate is 9600 (which is bloody slow). Each device tell the other its available bit rate, and they pick the highest and switch to it. You can use the "old_belkin" dongle driver that tells the IrDA stack that it can only support 9600. That should work for you. > Seems like I'll be able to send squirts in a bit. ;) I'll just hardcode > the baudrate to 9600 but I'd like to have it go upto 115200, that would be > nice. You will need to implement the dongle driver. It's not that bad. > Thanks, > > Felix Have fun... Jean |