[ltp] irda pilot-xfer with samsung sph-i500

[Marius Gedminas]

--JYK4vJDZwFMowpUq
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Dec 27, 2004 at 04:27:19PM -0800, Dimitris Kogias wrote:
> Thanks for the help Marius.  Unfortunately either I'm missing something=
=20
> else about how IR drivers work in Linux or my device's IR is busted;=20
> more details below.
>=20
> My only other Pilot, an older V, suffers from an apparent case of=20
> incurable Mad Digitizer Syndrome so I can't test IR comms between the=20
> two handhelds.
>=20
> One thing I have been able to ascertain though is that when irattach is=
=20
> up, the older Pilot does respond to discovery packets (saw it ack in=20
> irdadump) whereas my SPH-i500 doesn't.  The i500 has "beam receive"=20
> enabled of course.  It seems that an IR failure on the Samsung is the=20
> mot likely cause at this point, but I can't confirm...

You can try beaming a business card or something from the i500 and
looking whether irdadump sees anything.

In any case, if you see the older palm in /proc/net/irda/discovery, it
appears that IrDA works on the computer side.

Did you trigger HotSync over an IrDA connection on the i500 as well as
running pilot-xfer -p /dev/ircomm0?

> I did manage to get it to work with USB after I added usb-serial and=20
> visor modules to the kernel config.  It's hit-and-miss, in that I need=20
> to try it several times before the kernel will "agree" that the device=20
> is there on /dev/ttyUSB1 instead of another of the usb-serial ports.=20
> from syslog entries it seems to be trying ttyUSB2,3,... before trying 1=
=20
> several times and succeeding.  It definitely would be nice to make this=
=20
> more reliable; hotsync voodoo?

/dev/ttyUSB{0,1} appear a second or two after I press HotSync on the
cradle of my Palm; I've learned to wait those two seconds before I run
pilot-xfer.

> >Try
> >
> >  setserial /dev/ttyS1 uart none port 0 irq 0
>=20
> Note:  I'm using the SIR driver, not the "native" nsc-ircc driver (see=20
> module list in my original post).  AFAICT you only need to disable the=20
> serial port when you use the native driver.

You are right, this bit is only necessary for nsc-ircc.  I
misremembered.

Marius Gedminas
--=20
Life was simple before World War II. After that, we had systems.
        -- Grace Murray Hopper, 1987

--JYK4vJDZwFMowpUq
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFB0T2/kVdEXeem148RAhtrAJ0Tc6qSL4eoj7d6kYbhDiyp8hQlCACfYH2v
K8YLAeCs5R3ooLHUyKTNQRY=
=jrwc
-----END PGP SIGNATURE-----

--JYK4vJDZwFMowpUq--