From: Marcel Holtmann <marcel@holtmann.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Samuel Ortiz <samuel@sortiz.org>,
Network Development <netdev@vger.kernel.org>
Subject: Re: IrDA woes..
Date: Thu, 2 Jan 2014 13:41:28 -0800 [thread overview]
Message-ID: <370106E9-5C39-4917-AE74-2ED5E376DA11@holtmann.org> (raw)
In-Reply-To: <CA+55aFz_qDYP_P0PLUNv0wotoy=5PcS+7Qtt=U6EzvL4h4E69A@mail.gmail.com>
Hi Linus,
> Is anybody actually really using or maintaining irda any more? Because
> nothing seems to work. I think the following is *supposed* to work as
> a way to emulate having two irda dongles without actually having the
> hardware:
>
> - in terminal 1:
>
> socat PTY,link=/tmp/ttyS0 PTY,link=/tmp/ttyS1
>
> - terminal 2:
>
> irattach $(readlink /tmp/ttyS0) -s
> irattach $(readlink /tmp/ttyS1) -s
>
> - in terminal 3:
>
> echo "Duh" > /dev/ircomm0
>
> - in terminal 4:
>
> cat /dev/ircomm1
>
> (expecting to see "Duh" in terminal 4) but it really doesn't work for me.
if you are using the stir4200 driver then you are using an USB dongle that does not need the irattach to make it known to the IrDA subsystem. It will automatically make it known. For every IrDA dongle you attach you should see an irdaX with ifconfig.
The irattach (if I remember this correctly since this is long long time ago) is to take an IrDA device that is attached to a TTY and attach the IrDA ldisc to it to make it know to the IrDA subsystem. Not something that is needed for USB dongles with a proper driver. So the above should have never worked for you.
While the IrDA communication via /dev/ircommX is somehow possible, I do not remember how. What we used back in the days were IrDA sockets. I think if you look into Gnokii source you mind find an example on how to create an IrDA socket to talk to Nokia phone. Then again, this is so long time ago, I am not going to look at that since I am afraid that code is pretty ugly by todays standards.
Regards
Marcel
next prev parent reply other threads:[~2014-01-02 21:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-31 20:08 IrDA woes Linus Torvalds
2014-01-02 8:46 ` David Miller
2014-01-02 19:11 ` Linus Torvalds
2014-01-02 21:07 ` Linus Torvalds
2014-01-02 22:41 ` David Miller
2014-01-02 22:47 ` Linus Torvalds
2014-01-03 0:05 ` David Miller
2014-01-03 1:00 ` Linus Torvalds
2014-01-02 21:41 ` Marcel Holtmann [this message]
2014-01-02 21:49 ` Linus Torvalds
2014-01-02 22:13 ` Marcel Holtmann
2014-01-02 22:29 ` Linus Torvalds
2014-01-02 22:54 ` Linus Torvalds
2014-01-02 22:42 ` David Miller
2014-01-04 1:23 ` Samuel Ortiz
2014-01-04 8:15 ` Loganaden Velvindron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=370106E9-5C39-4917-AE74-2ED5E376DA11@holtmann.org \
--to=marcel@holtmann.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=samuel@sortiz.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox