netdev - Re: IrDA woes..

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 2 Jan 2014 13:49:25 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Marcel Holtmann <marcel@...tmann.org>
Cc:	"David S. Miller" <davem@...emloft.net>,
	Samuel Ortiz <samuel@...tiz.org>,
	Network Development <netdev@...r.kernel.org>
Subject: Re: IrDA woes..

On Thu, Jan 2, 2014 at 1:41 PM, Marcel Holtmann <marcel@...tmann.org> wrote:
>
> 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.

I don't actually want to use the USB dongle if I can avoid it. I've
*tried* it, but it has the exact same issue as the pty has, namely
that it doesn't really work reliably.

So for debugging I'd actually much prefer to use the pty approach.

I don't have any devices that use irda (the dive computers that showed
the problem are expensive and not any that I personally would actually
want to buy), so I'm trying to recreate the problems using a loopback
system.

(I have a non-ircomm version too, which has a device emulation on one
end of the pty, and uses a irda socket on another end. That one is
very specialized for the dive computer thing, though, which is why I
wanted to first try to do something "simpler" using just ircomm at
both ends).

               Linus
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html