From: Robert L. <lt...@em...> - 2002-06-14 19:54:22
|
Okay, I'm going to try one last time. Can anyone explain to me in a paragraph or less, but over ONE word, how to have my linux machine recieve data from my Palm Vx. Thanks, Robert. -- __________________________________________________________ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup Save up to $160 by signing up for NetZero Platinum Internet service. http://www.netzero.net/?refcd=N2P0602NEP8 |
From: <dhi...@ya...> - 2002-09-02 07:35:42
|
Hi, I am trying to dedug the code.but as there is no documentation available.Can you help me in giving the URL on which I will get Documentation of Linux Code For IrDA Implementation.Please do the needful Regards, Dhiraj --------------------------------- Sell you car, by placing a classified ad on Yahoo India Autos . It's Free!! |
From: tiny f. <fis...@ho...> - 2003-05-08 07:38:37
|
Hi, I am testing the compatibility of OpenOBEX-1.0.0. I have tried some systems(Palm/PPC/Win2K) and it works very good. But Win2K sometimes will return 0x63 when I put a file to Win2K. The steps are: 1) Linux connects to Win2K successfully, 2) but Win2K returns 0x63 when linux do a put operation. From the log of irdadump, 1) After negotiation with Win2K, Linux sends "OBEX" & "IrDA:TinyTP:LsapSel" and Win2K returns SUCCESS. 2) Linux sends CONNECT cmd and Win2K returns SUCCESS. 3) Now Win2K sends "OBEX:IrXfer" & "IrDA:TinyTP:LsapSel" and Linux sends "OBEX PUT final=1 len=68 Name="a.vcf" Lenght=44 body-end=[44 bytes]" nearly at the same time. Before Win2K returns something about PUT, Linux sends "No such class" out, then, Win2K returns 0x63. I have checked OBEX SPEC. OpenOBEX is based on OBEX 1.2 but it seems that OBEX of Win2K(irftp.exe) is based on OBEX 1.0 because 0x63 is no defined in OBEX SPEC 1.2 but defined in OBEX SPEC 1.0. OBEX response code HTTP status code Definition 0x63 (0xE3) 503 Service Unavailable Has anybody here known it? And how to fix it? Any help would be appreciated! The following is log of irdadump: 20:29:47.277691 xid:cmd fed0286f > ffffffff S=6 s=0 (14) enter irdadump_loop 20:29:47.357056 xid:rsp fed0286f < 0005694e S=6 s=0 w20146-01 hint=8425 [ Computer Telephony IrCOMM IrOBEX ] (27) enter irdadump_loop 20:29:47.407242 xid:cmd fed0286f > ffffffff S=6 s=1 (14) enter irdadump_loop 20:29:47.537225 xid:cmd fed0286f > ffffffff S=6 s=2 (14) enter irdadump_loop 20:29:47.667239 xid:cmd fed0286f > ffffffff S=6 s=3 (14) enter irdadump_loop 20:29:47.797239 xid:cmd fed0286f > ffffffff S=6 s=4 (14) enter irdadump_loop 20:29:47.927241 xid:cmd fed0286f > ffffffff S=6 s=5 (14) enter irdadump_loop 20:29:48.057248 xid:cmd fed0286f > ffffffff S=6 s=* Linux hint=c420 [ Computer LAN Access IrO BEX ] (22) enter irdadump_loop 20:29:48.317672 xid:cmd fed0286f > ffffffff S=6 s=0 (14) enter irdadump_loop 20:29:48.447232 xid:cmd fed0286f > ffffffff S=6 s=1 (14) enter irdadump_loop 20:29:48.577239 xid:cmd fed0286f > ffffffff S=6 s=2 (14) enter irdadump_loop 20:29:48.655939 xid:rsp fed0286f < 0005694e S=6 s=2 w20146-01 hint=8425 [ Computer Telephony IrCOMM IrOBEX ] (27) enter irdadump_loop 20:29:48.707309 xid:cmd fed0286f > ffffffff S=6 s=3 (14) enter irdadump_loop 20:29:48.837307 xid:cmd fed0286f > ffffffff S=6 s=4 (14) enter irdadump_loop 20:29:48.967244 xid:cmd fed0286f > ffffffff S=6 s=5 (14) enter irdadump_loop 20:29:49.097247 xid:cmd fed0286f > ffffffff S=6 s=* Linux hint=c420 [ Computer LAN Access IrO BEX ] (22) enter irdadump_loop 20:29:49.136912 snrm:cmd ca=fe pf=1 fed0286f > 0005694e new-ca=36 LAP QoS: Baud Rate=115200bps Max Turn Time=500ms Data Size=2048B Window Size=7 Add BO FS=0 Min Turn Time=1000us Link Disc=12s (32) enter irdadump_loop 20:29:49.240012 ua:rsp ca=36 pf=1 fed0286f < 0005694e LAP QoS: Baud Rate=115200bps Max Turn Time=500ms Data Size=2048B Window Size=4 Add BO FS=24 Min Turn Time=1000us Link Disc=12s (31) enter irdadump_loop enter irdadump_loop 20:29:49.240222 rr:cmd > ca=36 pf=1 nr=0 (2) enter irdadump_loop 20:29:49.787246 rr:cmd > ca=36 pf=1 nr=0 (2) enter irdadump_loop 20:29:49.796407 rr:rsp < ca=36 pf=1 nr=0 (2) enter irdadump_loop 20:29:49.796529 i:cmd > ca=36 pf=1 nr=0 ns=0 LM slsap=12 dlsap=00 CONN_CMD (6) enter irdadump_loop 20:29:49.806753 i:rsp < ca=36 pf=1 nr=1 ns=0 LM slsap=00 dlsap=12 CONN_RSP (6) enter irdadump_loop 20:29:49.806907 i:cmd > ca=36 pf=1 nr=1 ns=1 LM slsap=12 dlsap=00 GET_VALUE_BY_CLASS: "OBEX" "IrDA:TinyTP:LsapSel" (30) enter irdadump_loop 20:29:49.819548 i:rsp < ca=36 pf=1 nr=2 ns=1 LM slsap=00 dlsap=12 GET_VALUE_BY_CLASS: Succes s Integer: 02 (15) enter irdadump_loop 20:29:49.819739 i:cmd > ca=36 pf=1 nr=2 ns=2 LM slsap=12 dlsap=00 DISC (6) enter irdadump_loop 20:29:49.828411 rr:rsp < ca=36 pf=1 nr=3 (2) enter irdadump_loop 20:29:49.837720 i:cmd > ca=36 pf=1 nr=2 ns=3 LM slsap=13 dlsap=02 CONN_CMD TTP credits=14 (7 ) enter irdadump_loop 20:29:49.848838 i:rsp < ca=36 pf=1 nr=4 ns=2 LM slsap=02 dlsap=13 CONN_RSP TTP credits=14 (7 ) enter irdadump_loop 20:29:49.850426 i:cmd > ca=36 pf=1 nr=3 ns=4 LM slsap=13 dlsap=02 TTP credits=0 OBEX CONNECT len=19 (24) enter irdadump_loop 20:29:49.862400 rr:rsp < ca=36 pf=1 nr=5 (2) enter irdadump_loop 20:29:50.357246 rr:cmd > ca=36 pf=1 nr=3 (2) enter irdadump_loop 20:29:50.366336 rr:rsp < ca=36 pf=1 nr=5 (2) enter irdadump_loop 20:29:50.857239 rr:cmd > ca=36 pf=1 nr=3 (2) enter irdadump_loop 20:29:50.867280 rr:rsp < ca=36 pf=1 nr=5 (2) enter irdadump_loop 20:29:51.367236 rr:cmd > ca=36 pf=1 nr=3 (2) enter irdadump_loop 20:29:51.377572 i:rsp < ca=36 pf=0 nr=5 ns=3 LM slsap=03 dlsap=00 CONN_CMD (6) enter irdadump_loop 20:29:51.384099 i:rsp < ca=36 pf=1 nr=5 ns=4 LM slsap=02 dlsap=13 TTP credits=0 OBEX SUCCESS len=7 ver=1.0 flags=0 mtu=9983 (12) enter irdadump_loop 20:29:51.384235 i:cmd > ca=36 pf=1 nr=5 ns=5 LM slsap=00 dlsap=03 CONN_RSP (6) enter irdadump_loop 20:29:51.396281 i:rsp < ca=36 pf=1 nr=6 ns=5 LM slsap=03 dlsap=00 GET_VALUE_BY_CLASS: "OBEX: IrXfer" "IrDA:TinyTP:LsapSel" (37) enter irdadump_loop 20:29:51.396489 i:cmd > ca=36 pf=0 nr=6 ns=6 LM slsap=13 dlsap=02 TTP credits=1 OBEX PUT final=1 len=68 Name="a.sh" Lenght=44 body-end=[44 bytes] (73) enter irdadump_loop 20:29:51.406283 i:cmd > ca=36 pf=1 nr=6 ns=7 LM slsap=00 dlsap=03 GET_VALUE_BY_CLASS: No suc h class (11) enter irdadump_loop 20:29:51.414568 i:rsp < ca=36 pf=1 nr=0 ns=6 LM slsap=03 dlsap=00 DISC (6) enter irdadump_loop 20:29:51.907238 rr:cmd > ca=36 pf=1 nr=7 (2) enter irdadump_loop 20:29:51.915693 i:rsp < ca=36 pf=0 nr=0 ns=7 LM slsap=02 dlsap=13 TTP credits=0 OBEX Unknown response 63 (8) enter irdadump_loop 20:29:51.921703 i:rsp < ca=36 pf=1 nr=0 ns=0 LM slsap=02 dlsap=13 TTP credits=0 OBEX Unknown response 63 (8) enter irdadump_loop 20:29:51.921844 i:cmd > ca=36 pf=1 nr=1 ns=0 LM slsap=13 dlsap=02 DISC (6) enter irdadump_loop 20:29:51.931166 rr:rsp < ca=36 pf=1 nr=1 (2) enter irdadump_loop 20:29:52.427239 rr:cmd > ca=36 pf=1 nr=1 (2) enter irdadump_loop 20:29:52.437107 rr:rsp < ca=36 pf=1 nr=1 (2) enter irdadump_loop 20:29:52.927239 rr:cmd > ca=36 pf=1 nr=1 (2) enter irdadump_loop 20:29:52.937050 rr:rsp < ca=36 pf=1 nr=1 (2) enter irdadump_loop 20:29:53.427236 rr:cmd > ca=36 pf=1 nr=1 (2) enter irdadump_loop 20:29:53.435987 rr:rsp < ca=36 pf=1 nr=1 (2) enter irdadump_loop 20:29:53.907253 disc:cmd > ca=0x36 pf=1 (2) enter irdadump_loop 20:29:53.916639 ua:rsp ca=36 pf=1 fed0286f < 0005694e (10) enter irdadump_loop enter irdadump_loop 20:29:56.566524 xid:cmd ffffffff < 0005694e S=6 s=0 (14) enter irdadump_loop 20:29:56.677480 xid:cmd ffffffff < 0005694e S=6 s=1 (14) enter irdadump_loop 20:29:56.789479 xid:cmd ffffffff < 0005694e S=6 s=2 (14) enter irdadump_loop 20:29:56.900436 xid:cmd ffffffff < 0005694e S=6 s=3 (14) enter irdadump_loop 20:29:57.011392 xid:cmd ffffffff < 0005694e S=6 s=4 (14) enter irdadump_loop 20:29:57.113391 xid:cmd ffffffff < 0005694e S=6 s=5 (14) enter irdadump_loop 20:29:57.113510 xid:rsp fed0286f > 0005694e S=6 s=5 Linux hint=c420 [ Computer LAN Access IrO BEX ] (22) enter irdadump_loop 20:29:57.288945 xid:cmd ffffffff < 0005694e S=6 s=* w20146-01 hint=8425 [ Computer Telephony IrCOMM IrOBEX ] (27) enter irdadump_loop THX & BR, tinyfish _________________________________________________________________ 免费下载 MSN Explorer: http://explorer.msn.com/lccn/ |
From: Loren M L. <lo...@al...> - 2003-06-16 08:16:51
|
-- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C |
From: Aynton S. <ayn...@ho...> - 2003-09-16 21:05:50
Attachments:
browse.txt
|
_________________________________________________________________ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail |
From: Manuele M. <man...@li...> - 2003-10-19 17:32:02
|
From: Luigi B. <lu...@al...> - 2004-06-08 11:38:36
|
From: Christine P. <mad...@ms...> - 2004-07-31 16:24:55
|
I bought a WU-2 USB IrDA Dongle and I can't get it to work with Windows XP. Can you help me or direct me to a place that can? Christine |
From: abel e. <kar...@wa...> - 2005-06-14 13:59:20
|
hi, I have a gold-120 usb dongle. This thing seems to be considered as a Ma600 under linux. --> http://www.prodigy-tools.com/irda.htm I have tried to configure it but the process fail early. When i plug the thing, i got the following on dmesg ohci_hcd 0000:00:02.0: wakeup usb 1-3: new full speed USB device using address 2 drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic usbcore: registered new driver usbserial_generic usbcore: registered new driver usbserial drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0 drivers/usb/serial/usb-serial.c: USB Serial support registered for PL-2303 pl2303 1-3:1.0: PL-2303 converter detected usb 1-3: PL-2303 converter now attached to ttyUSB0 usbcore: registered new driver pl2303 drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver v0.11 well since here i have tried many thing i have found on the net but nothing have work at all. the most common is irattach /dev/usb/ttyUSB0 -d ma600 -s irdadump give me nothing ... can anyone send me some step-by-step idea to help me ? thanks |
From: William A. <wl...@ea...> - 2005-06-14 14:48:43
|
Greetings: Please feel free to redirect me to another forum if appropriate. I have also made a quick examination of the archive but did not see a post relevant to this inquiry. I am using Linux to connect to Palm/OS 5.2 via ir. SIR works fine but my FIR attempts have not been successful. This appears to be because 5.2 does not support IrNET. Is it possible to activate FIR on the Palm without the need for a mediation device such as those offered by Clarinet? If so, would such strategy involve a PPP link absent serial framing between the two devices? Thanks |
From: Alan M. <sou...@al...> - 2005-06-17 12:01:56
|
> I am using Linux to connect to Palm/OS 5.2 via ir. > SIR works fine but my FIR attempts have not been successful. > This appears to be because 5.2 does not support IrNET. > As far as I know neither PalmOS 4 nor 5 has any support for FIR (etc), they only support SIR. (I presume version 6, Cobalt, does support the faster rates). The support for IrNet is orthogonal to this. IrNet is layered over TinyTP-LMP-LAP-PHY, so will work whatever physical layer type is being used. BTW, I've a not-quite-finished IrNet Virtual Serial Driver for OS4, if anyone can tell me how to compile it for OS5+ARM I can have a go a porting it. -- Alan J. McFarlane http://www.alanjmcf.me.uk/ |
From: William A. <wl...@ea...> - 2005-06-18 00:11:14
|
----- Original Message ----- From: "Alan McFarlane" <sou...@al...> To: <ird...@li...> Sent: Friday, June 17, 2005 8:01 AM Subject: RE: [irda-users] (no subject) >> I am using Linux to connect to Palm/OS 5.2 via ir. >> SIR works fine but my FIR attempts have not been successful. >> This appears to be because 5.2 does not support IrNET. >> > As far as I know neither PalmOS 4 nor 5 has any support for FIR (etc), > they only support SIR. (I presume version 6, Cobalt, does support the > faster rates) Thank you for responding to my inquiry. It appears to me that the link layer is cueing upon a hint from the Palm and beginning negotiation before realizing that kernel(et al) support is not generated. 23:43:57.296195 xid:rsp 336c862c > 225842dd S=6 s=2 darkstar hint=4400 [ Computer LAN Access ] (24) 23:43:57.436157 xid:cmd ffffffff < 225842dd S=6 s=3 (14) 23:43:57.517156 xid:cmd ffffffff < 225842dd S=6 s=4 (14) 23:43:57.597156 xid:cmd ffffffff < 225842dd S=6 s=5 (14) 23:43:57.686156 xid:cmd ffffffff < 225842dd S=6 s=* IrCOMM hint=8204 [ PDA/Palmtop IrCOMM ] (23) 23:43:57.732156 snrm:cmd ca=fe pf=1 336c862c < 225842dd new-ca=6a LAP QoS: Baud Rate=115200bps Max Turn Time=500ms Data Size=512B Window Size=1 Add BOFS=0 Min Turn Time=5000us Link Disc=40s (32) 23:43:57.732224 ua:rsp ca=6a pf=1 336c862c > 225842dd LAP QoS: Baud Rate=115200bps Max Turn Time=500ms Data Size=2048B Window Size=7 Add BOFS=0 Min Turn Time=1000us Link Disc=12s (31) 23:43:58.305157 rr:cmd < ca=6a pf=1 nr=0 (2) 23:43:58.305193 rr:rsp > ca=6a pf=1 nr=0 (2) 23:43:58.325155 i:cmd < ca=6a pf=1 nr=0 ns=0 LM slsap=01 dlsap=00 CONN_CMD (6) 23:43:58.325204 i:rsp > ca=6a pf=1 nr=1 ns=0 LM slsap=00 dlsap=01 CONN_RSP (6) 23:43:58.348155 i:cmd < ca=6a pf=1 nr=1 ns=1 LM slsap=01 dlsap=00 GET_VALUE_BY_CLASS: "IrDA:IrCOMM" "IrDA:TinyTP:LsapSel" (37) 23:43:58.348186 i:rsp > ca=6a pf=1 nr=2 ns=1 LM slsap=00 dlsap=01 GET_VALUE_BY_CLASS: No such class (11) 23:43:58.365155 disc:cmd < ca=0x6a pf=1 (2) If this is so, can it be disabled by /proc/sys/net/irda? If I am incorrect, can you point me in another direction? > > The support for IrNet is orthogonal to this. IrNet is layered over > TinyTP-LMP-LAP-PHY, so will work whatever physical layer type is being > used. > > > BTW, I've a not-quite-finished IrNet Virtual Serial Driver for OS4, if > anyone can tell me how to compile it for OS5+ARM I can have a go a > porting it. > -- If you'll send me the driver, I'll try to help you. Thanks, Bill > Alan J. McFarlane > http://www.alanjmcf.me.uk/ > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > irda-users mailing list > ird...@li... > http://lists.sourceforge.net/lists/listinfo/irda-users > |
From: Alan M. <sou...@al...> - 2005-06-21 17:36:03
|
> From William Adams >> From: "Alan McFarlane" <sou...@al...> >>> From William Adams >>> I am using Linux to connect to Palm/OS 5.2 via ir. >>> SIR works fine but my FIR attempts have not been successful. >>> This appears to be because 5.2 does not support IrNET. >>> >> As far as I know neither PalmOS 4 nor 5 has any support for >> FIR (etc), they only support SIR. (I presume version 6, >> Cobalt, does support the faster rates) > > Thank you for responding to my inquiry. > What is your high level aim here? To form a data network between Linux and Palm? Normally one connects from the Palm to the Linux box, using IrCOMM (as there's no (released) IrNet support on the Palm). Someone more familiar with Linux can likely point you to a page describing this. > It appears to me that the link layer is cueing upon a hint > from the Palm > and beginning negotiation before realizing that kernel(et al) support > is not generated. > I don't understand what you're saying there. I'm no Linux expert so... See below for my explanation of what the trace shows. [...] > 23:43:58.348155 i:cmd < ca=6a pf=1 nr=1 ns=1 LM slsap=01 dlsap=00 > GET_VALUE_BY_CLASS: "IrDA:IrCOMM" "IrDA:TinyTP:LsapSel" (37) > > 23:43:58.348186 i:rsp > ca=6a pf=1 nr=2 ns=1 LM slsap=00 dlsap=01 > GET_VALUE_BY_CLASS: No such class (11) > > 23:43:58.365155 disc:cmd < ca=0x6a pf=1 (2) > That irdadump trace shows a completely bog standard instance of the Palm forming a IrLAP connection to the Linux box, looking for the IrCOMM service, and disconnecting when it doesn't find it. I see no evidence of IrNet at all--if the Palm wanted IrNet it would ask for it in the same way as it did for "IrDA:IrCOMM" (see http://www.alanjmcf.me.uk/comms/infrared/IrDA%20uses%20(brief).html). The Virtual Serial Driver that appears as "Infrared" and is used by the "IR to Handheld/PC" and Connections, is the IrCOMM Vdrv by-the-way. > If this is so, can it be disabled by /proc/sys/net/irda? > > If I am incorrect, can you point me in another direction? > I'm lost, maybe a Linux person can help. It all depends on what your ultimate aim is. >> The support for IrNet is orthogonal to this. IrNet is layered over >> TinyTP-LMP-LAP-PHY, so will work whatever physical layer >> type is being used. >> >> >> BTW, I've a not-quite-finished IrNet Virtual Serial Driver >> for OS4, if >> anyone can tell me how to compile it for OS5+ARM I can have a go a >> porting it. >> > If you'll send me the driver, I'll try to help you. > Well it's not really in a state for that to be useful. :-,( (I need a guru on PalmOS+OS5+ARM+GCC+PRC-Tool to show me how to build a Vdrv for OS5, that's how to tell GCC and the other tools what to create, and what modifications are needed in the Vdrv API. See e.g. http://news.palmos.com/read/messages?id=191105) Alan |
From: William A. <wl...@ea...> - 2005-06-21 18:52:24
|
----- Original Message ----- From: "Alan McFarlane" <sou...@al...> To: <ird...@li...> Sent: Tuesday, June 21, 2005 1:35 PM Subject: RE: [irda-users] (no subject) >> From William Adams >>> From: "Alan McFarlane" <sou...@al...> >>>> From William Adams >>>> I am using Linux to connect to Palm/OS 5.2 via ir. >>>> SIR works fine but my FIR attempts have not been successful. >>>> This appears to be because 5.2 does not support IrNET. >>>> >>> As far as I know neither PalmOS 4 nor 5 has any support for >>> FIR (etc), they only support SIR. (I presume version 6, >>> Cobalt, does support the faster rates) >> >> Thank you for responding to my inquiry. >> > What is your high level aim here? To form a data network between Linux > and Palm? Yes > Normally one connects from the Palm to the Linux box, using > IrCOMM (as there's no (released) IrNet support on the Palm). Someone > more familiar with Linux can likely point you to a page describing this. > I have initiated connectivity in both directions using IrCOMM. I wanted to avoid the overhead of serial framing and it seemed that if FIR were available for the Actisys ir-210u, IrNET would be the most productive companion protocol. >> It appears to me that the link layer is cueing upon a hint >> from the Palm >> and beginning negotiation before realizing that kernel(et al) support >> is not generated. >> > I don't understand what you're saying there. I'm no Linux expert so... I'm saying that it seems frivilous for the IrDA stack to respond to a hint that can not succeed based upond intrinsic lack of support. Better to let the Palm continue to bid until something more palatable shows up. > See below for my explanation of what the trace shows. > > [...] >> 23:43:58.348155 i:cmd < ca=6a pf=1 nr=1 ns=1 LM slsap=01 dlsap=00 >> GET_VALUE_BY_CLASS: "IrDA:IrCOMM" "IrDA:TinyTP:LsapSel" (37) >> >> 23:43:58.348186 i:rsp > ca=6a pf=1 nr=2 ns=1 LM slsap=00 dlsap=01 >> GET_VALUE_BY_CLASS: No such class (11) >> >> 23:43:58.365155 disc:cmd < ca=0x6a pf=1 (2) >> > That irdadump trace shows a completely bog standard instance of the Palm > forming a IrLAP connection to the Linux box, looking for the IrCOMM > service, and disconnecting when it doesn't find it. I see no evidence > of IrNet at all--if the Palm wanted IrNet it would ask for it in the > same way as it did for "IrDA:IrCOMM" This is correct. However when the connection is initiated from the Linux side with only IrNet support generated, the same bid response protocol is seen. The only difference is that the bid token offered by Linux is "IrNetv1". The Palm responds with "NO_SUCH_CLASS" just as Linux did when IrCOMM was not generated. This is how I knew that the Palm did not support IrNET. (see > http://www.alanjmcf.me.uk/comms/infrared/IrDA%20uses%20(brief).html). > The Virtual Serial Driver that appears as "Infrared" and is used by the > "IR to Handheld/PC" and Connections, is the IrCOMM Vdrv by-the-way. > > >> If this is so, can it be disabled by /proc/sys/net/irda? >> >> If I am incorrect, can you point me in another direction? >> > I'm lost, maybe a Linux person can help. It all depends on what your > ultimate aim is. > I want to get to my Java program. > >>> The support for IrNet is orthogonal to this. IrNet is layered over >>> TinyTP-LMP-LAP-PHY, so will work whatever physical layer >>> type is being used. >>> >>> >>> BTW, I've a not-quite-finished IrNet Virtual Serial Driver >>> for OS4, if >>> anyone can tell me how to compile it for OS5+ARM I can have a go a >>> porting it. >>> >> If you'll send me the driver, I'll try to help you. >> > Well it's not really in a state for that to be useful. :-,( (I need a > guru on PalmOS+OS5+ARM+GCC+PRC-Tool to show me how to build a Vdrv for > OS5, that's how to tell GCC and the other tools what to create, and what > modifications are needed in the Vdrv API. See e.g. > http://news.palmos.com/read/messages?id=191105) > Not my bag but I'll be in that area soon. Thanks for the help. Bill > Alan > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > irda-users mailing list > ird...@li... > http://lists.sourceforge.net/lists/listinfo/irda-users > |
From: <rbn...@bl...> - 2005-10-07 18:34:26
|
Hi, I've got a Dell Latitude C600 dual booting Fedora Core 4 and WinXP. I'm running the FC4 stock kernels (1398 at the moment). The BIOS gives options for the two serial ports so I switch off the first COM port and the printer port and set the Infrared port to COM3 (recommended by Dell). However I've tried this on all available ports COM1,2,3 and 4. It has an optio for SIR and FIR and I've tried both. As can be seen from the output below, the C600 contains SMC chip FDC37N972. When using WinXP, this IR port works fine. I've used a webcam to see the output from the transceiver (good tip I found) and can see the really bright flashes under WinXP. However, I've tried both SIR and FIR modes under linux and although I can get output from irdadump, there's no flashing from the transceiver and no devices are recognised. I've tried smcinit but can't get 0.4 to compile on my machine. RPMS for FC4 are for 0.3 only which doesn't include the more flexible smcinit command, only the toshXX00-smcinit commands. I think this is a chip initialisation problem but don't know enough to be sure. I'm not a kernel or module developer either so I don't know enough to take the specs from the SMC website and write my own initialisation. I've given an example below to help. When trying this with the different COM ports I get the same result just with different IRQ's and IO ranges. All match those in WinXP though so it's like everthing's being detected OK, just not set up properly. Any help would be great. WINXP Device resource settings for FIR SMC chip when set to FIR on COM3 IRQ=4 DMA=3 I/O 0x03e8 - 0x03ef (I believe this is the SIR range from the specs) I/O 0x0290 - 0x0297 (FIR?) The smcirda.sys driver file mentions that the base address should be SIR-10h or FIR-18h 32 bit aligned (don't know what this means). This set up works fine. I can see transmissions with the webcam. LINUX SIR first BIOS Setting com3 SIR >dmesg | grep tty ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A > irattach /dev/ttyS2 -s >tail /var/log/messages Oct 7 18:44:38 localhost kernel: NET: Registered protocol family 23 Oct 7 18:44:39 localhost irattach: executing: 'echo laptop > /proc/sys/net/irda/devname' Oct 7 18:44:39 localhost irattach: executing: 'echo 1 > /proc/sys/net/irda/discovery' Oct 7 18:44:39 localhost irattach: Starting device irda0 >irdadump 17:45:41.499075 xid:cmd 0906bc4e > ffffffff S=6 s=0 (14) 17:45:41.589060 xid:cmd 0906bc4e > ffffffff S=6 s=1 (14) 17:45:41.679050 xid:cmd 0906bc4e > ffffffff S=6 s=2 (14) 17:45:41.769043 xid:cmd 0906bc4e > ffffffff S=6 s=3 (14) 17:45:41.859031 xid:cmd 0906bc4e > ffffffff S=6 s=4 (14) 17:45:41.949022 xid:cmd 0906bc4e > ffffffff S=6 s=5 (14) 17:45:42.039016 xid:cmd 0906bc4e > ffffffff S=6 s=* laptop hint=0400 [ Computer ] (22) Webcam: No output from transceiver FIR Same BIOS settings >dmesg | grep tty ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A >setserial /dev/ttyS2 uart none >setserial /dev/ttyS2 /dev/ttyS2, UART: unknown, Port: 0x03e8, IRQ: 4 >modprobe smsc-ircc2 >tail /var/log/messages Oct 7 19:02:58 localhost kernel: NET: Registered protocol family 23 Oct 7 19:02:58 localhost kernel: found SMC SuperIO Chip (devid=0x0b rev=00 base=0x03f0): FDC37N972 Oct 7 19:02:58 localhost kernel: SMsC IrDA Controller found Oct 7 19:02:58 localhost kernel: IrCC version 2.0, firport 0x290, sirport 0x3e8 dma=3, irq=4 Oct 7 19:02:58 localhost kernel: No transceiver found. Defaulting to Fast pin select Oct 7 19:02:58 localhost kernel: IrDA: Registered device irda0 >irattach irda0 -s >tail /var/log/messages Oct 7 19:04:01 localhost irattach: executing: '/sbin/modprobe irda0' Oct 7 19:04:01 localhost irattach: executing: 'echo laptop > /proc/sys/net/irda/devname' Oct 7 19:04:01 localhost irattach: executing: 'echo 1 > /proc/sys/net/irda/discovery' Oct 7 19:04:01 localhost irattach: Starting device irda0 >lsmod | more Module Size Used by irport 13153 0 smsc_ircc2 18909 0 irda 129657 2 irport,smsc_ircc2 crc_ccitt 2113 1 irda parport_pc 28933 0 lp 13001 0 ....snip..... >irdadump 18:04:46.747132 xid:cmd 3825703c > ffffffff S=6 s=0 (14) 18:04:46.837117 xid:cmd 3825703c > ffffffff S=6 s=1 (14) 18:04:46.927109 xid:cmd 3825703c > ffffffff S=6 s=2 (14) 18:04:47.017099 xid:cmd 3825703c > ffffffff S=6 s=3 (14) 18:04:47.107090 xid:cmd 3825703c > ffffffff S=6 s=4 (14) 18:04:47.197080 xid:cmd 3825703c > ffffffff S=6 s=5 (14) 18:04:47.287073 xid:cmd 3825703c > ffffffff S=6 s=* laptop hint=0400 [ Computer ] (22) 21 packets received by filter >gqcam Webcam: No output from transceiver >cat /proc/interrupts CPU0 0: 1805156 XT-PIC timer 1: 7267 XT-PIC i8042 2: 0 XT-PIC cascade 4: 1806 XT-PIC irda0 5: 43 XT-PIC Maestro3 8: 1 XT-PIC rtc 9: 1 XT-PIC acpi 11: 475212 XT-PIC uhci_hcd:usb1, yenta, yenta, ath0 12: 121817 XT-PIC i8042 14: 17689 XT-PIC ide0 15: 15429 XT-PIC ide1 >cat /proc/dma 3: irda0 4: cascade >lspci 00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03) 00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03) 00:03.0 CardBus bridge: Texas Instruments PCI1420 00:03.1 CardBus bridge: Texas Instruments PCI1420 00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02) 00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) 00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01) 00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03) 00:08.0 Multimedia audio controller: ESS Technology ES1983S Maestro-3i PCI Audio Accelerator (rev 10) 01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility M3 AGP 2x (rev 02) 06:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01) Thanks |
From: Montes Jean-B. <jb....@py...> - 2006-06-02 08:40:06
|
Hi, I have a dongle usb irda (sigmatel). I make "irattach irda0 -s" to launch Irda. that functions very well. But I would like to have I will want to have an attached node in /dev (for exemple /dev/irda0). thanks by advance Jean-Bastien |
From: Samuel O. <sa...@so...> - 2006-06-11 23:10:10
|
Hi Jean-Bastien, On Fri, Jun 02, 2006 at 10:39:45AM +0200, Montes Jean-Bastien wrote: > Hi, > I have a dongle usb irda (sigmatel). I make "irattach irda0 -s" to > launch Irda. that functions very well. But I would like to have I will > want to have an attached node in /dev (for exemple /dev/irda0). You won't get that. Network devices I/O semantics are quite different from other devices (block, character) and thus they can not be mapped to a regular file under /dev/ We can help you if you explain what would you need a /dev/irda0 for. Cheers, Samuel. > thanks by advance > Jean-Bastien > > > > _______________________________________________ > irda-users mailing list > ird...@li... > http://lists.sourceforge.net/lists/listinfo/irda-users |
From: rami j. <sr...@ya...> - 2012-04-27 11:20:32
|
http://djmedieval.com/wp-content/plugins/google-sitemap-generator/vmord.html?rff=gr.zffzl&rag=y.gg&zin=mnej |
From: rami j. <sr...@ya...> - 2012-04-27 13:25:16
|
http://djmedieval.com/wp-content/plugins/google-sitemap-generator/bmorn.html?yna=ffyq.jgj&ffg=gg.gz&ggi=dmyq |
From: rami j. <sr...@ya...> - 2012-04-28 09:09:33
|
http://876dy.com/data/bmorn.html?cz=ji.jrg&rgg=rag.zgffg&rc=wosr |
From: rami j. <sr...@ya...> - 2012-05-09 16:52:48
|
http://evo.aeldan.com/static/evos/gjvgkle.html?gz=nff.jazg&zny=gyg.jyg&ggi=qnut |
From: rami j. <sr...@ya...> - 2012-05-09 17:26:14
|
http://alan-davis.net/apd/piwigo/local/combined/gjvgkle.html?bbg=ic.gffz&rxc=az.ffnff&rgi=amju |
From: rami j. <sr...@ya...> - 2012-05-11 19:16:33
|
http://wp.coralmine.com/uploads/2011/06/thjfle.html?dfe=pkdc.tnb&gv=dbr.xswch&ujf=qwad |
From: Michael S. <mi...@os...> - 2012-05-11 20:10:24
|
On Fri, May 11, 2012 at 12:16:25PM -0700, rami jiossy wrote: > http:// I suggest to unsubscribe/premoderate this account -- seems like hijacked for spam. -- ---- WBR, Michael Shigorin <mi...@al...> ------ Linux.Kiev http://www.linux.kiev.ua/ |
From: rami j. <sr...@ya...> - 2012-05-13 15:15:38
|
http://treyhendon.com/images/2011/06/thjfle.html?rgs=fktl.fhe&ed=rog.saef&swef=uynl |