linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ondrej Zary <linux@rainbow-software.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: David Miller <davem@davemloft.net>,
	samuel@sortiz.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH 0/4] irda: move it to drivers/staging so we can delete it
Date: Thu, 31 Aug 2017 09:31:16 +0200	[thread overview]
Message-ID: <201708310931.16406.linux@rainbow-software.org> (raw)
In-Reply-To: <20170831043042.GB3359@kroah.com>

On Thursday 31 August 2017, Greg KH wrote:
> On Tue, Aug 29, 2017 at 11:32:58PM +0200, Ondrej Zary wrote:
> > On Tuesday 29 August 2017 01:42:08 David Miller wrote:
> > > From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > Date: Sun, 27 Aug 2017 17:03:30 +0200
> > >
> > > > The IRDA code has long been obsolete and broken.  So, to keep people
> > > > from trying to use it, and to prevent people from having to maintain
> > > > it, let's move it to drivers/staging/ so that we can delete it
> > > > entirely from the kernel in a few releases.
> > >
> > > No objection, I'll apply this to net-next, thanks Greg.
> >
> > IRDA works fine in Debian 9 (kernel 4.9) and I use it for simple file
> > transfer. Hope I'm not the only one...
> >
> > # irattach /dev/ttyS0 -d tekram -s
> > # irdadump
> > 21:28:52.830350 xid:cmd aed8eb79 > ffffffff S=6 s=0 (14)
> > 21:28:52.922368 xid:cmd aed8eb79 > ffffffff S=6 s=1 (14)
> > 21:28:53.014350 xid:cmd aed8eb79 > ffffffff S=6 s=2 (14)
> > 21:28:53.106338 xid:cmd aed8eb79 > ffffffff S=6 s=3 (14)
> > 21:28:53.190276 xid:rsp aed8eb79 < 000035d1 S=6 s=3 Nokia 6230i hint=b125
> > [ PnP Modem Fax Telephony IrCOMM IrOBEX ] (28)
> > 21:28:53.198384 xid:cmd aed8eb79 > ffffffff S=6 s=4 (14)
> > 21:28:53.290382 xid:cmd aed8eb79 > ffffffff S=6 s=5 (14)
> > 21:28:53.382341 xid:cmd aed8eb79 > ffffffff S=6 s=* pentium hint=0400 [
> > Computer ] (23)
> > ^C
> > 8 packets received by filter
> >
> > $ obexftp -i -l MMC
> > Connecting..\done
> > Receiving "MMC".../<?xml version="1.0"?>
> > <!DOCTYPE folder-listing SYSTEM "obex-folder-listing.dtd"
> >  [ <!ATTLIST folder mem-type CDATA #IMPLIED> ]>
> > <folder-listing version="1.0">
> >     <parent-folder />
> >     <file name="Image000.jpg" size="304300" modified="20160219T135924"
> > user-perm="RWD"/>
> >     <file name="Image001.jpg" size="270037" modified="20170811T233122"
> > user-perm="RWD"/>
> >     <file name="Image004.jpg" size="53519" modified="20170814T074550"
> > user-perm="RWD"/>
> > ....
> > $ obexftp -i -c MMC -g Image004.jpg
> > Connecting..\done
> > Sending "MMC"...|done
> > Receiving "Image004.jpg"...-done
> > Disconnecting..\done
>
> Odd, and is this just a ir device connected to a "real" serial port, or
> a specific IRDA device?
>
> thanks,
>
> greg k-h

Yes, it's an external IrDA dongle connected to a real serial port.

I also have an ARK3116-based USB IrDA dongle and some laptops with integrated 
IrDA ports that used to work fine but haven't tested them recently (i.e. 
Debian 9).

-- 
Ondrej Zary

  reply	other threads:[~2017-08-31  7:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-27 15:03 [PATCH 0/4] irda: move it to drivers/staging so we can delete it Greg Kroah-Hartman
2017-08-27 15:03 ` [PATCH 1/4] irda: move net/irda/ to drivers/staging/irda/net/ Greg Kroah-Hartman
2017-08-30  6:04   ` [lkp-robot] [irda] 66d98e78e4: BUG:unable_to_handle_kernel kernel test robot
2017-08-30  6:12     ` Greg Kroah-Hartman
2017-08-30  6:19       ` Ye Xiaolong
2017-08-27 15:03 ` [PATCH 2/4] irda: move drivers/net/irda to drivers/staging/irda/drivers Greg Kroah-Hartman
2017-08-27 15:03 ` [PATCH 3/4] irda: move include/net/irda into staging subdirectory Greg Kroah-Hartman
2017-08-27 15:03 ` [PATCH 4/4] staging: irda: add a TODO file Greg Kroah-Hartman
2017-08-27 15:35 ` [PATCH 0/4] irda: move it to drivers/staging so we can delete it Joe Perches
2017-08-27 16:13   ` Greg Kroah-Hartman
2017-08-27 16:19     ` Joe Perches
2017-08-27 16:53       ` Greg Kroah-Hartman
2017-08-27 23:15         ` Joe Perches
2017-08-28 23:42 ` David Miller
2017-08-28 23:46   ` Joe Perches
2017-08-29  5:06     ` Greg KH
2017-08-29 21:32   ` Ondrej Zary
2017-08-31  4:30     ` Greg KH
2017-08-31  7:31       ` Ondrej Zary [this message]
2017-08-29 10:59 ` Geert Uytterhoeven
2017-08-29 11:11   ` Stefano Brivio
2017-08-29 11:28     ` Greg Kroah-Hartman
2017-08-29 12:11       ` Geert Uytterhoeven
2017-08-29 14:48         ` Greg Kroah-Hartman
2017-08-29 16:49           ` David Miller
2017-08-29 16:38   ` David Miller

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=201708310931.16406.linux@rainbow-software.org \
    --to=linux@rainbow-software.org \
    --cc=davem@davemloft.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=samuel@sortiz.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;
as well as URLs for NNTP newsgroup(s).