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]

Message-Id: <0A3D681C-9597-44F0-9540-B42F259004D1@holtmann.org>
Date:	Thu, 2 Jan 2014 14:13:50 -0800
From:	Marcel Holtmann <marcel@...tmann.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	"David S. Miller" <davem@...emloft.net>,
	Samuel Ortiz <samuel@...tiz.org>,
	Network Development <netdev@...r.kernel.org>
Subject: Re: IrDA woes..

Hi Linus,

>> 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).

I do not think that the irattach emulation idea of PTY is going to work for you. irattach is pretty much specialized to the underlaying IrDA hardware that is attached to its exposed (or physically connected) TTY.

As far as I recall, there was never any loopback emulation implemented in Linux that you could use. So you need to go through real IrDA hardware if you want to do anything useful. You might be just out of luck with the IrDA subsystem and its capabilities to do any easy development.

Maybe irdadump is helping you do debug some parts, but that tool might be as outdated as everything else.

Back in the days, I had more success with the stir4200 based USB dongles than any of the TTY based ones. But my bet is also that this all goes back 10 years, so my brain could clearly play tricks on me.

Regards

Marcel

--
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