From: Antti Palosaari <crope@iki.fi>
To: Greg KH <greg@kroah.com>
Cc: linux-serial@vger.kernel.org, linux-media@vger.kernel.org,
linux-usb@vger.kernel.org, "Bjørn Mork" <bjorn@mork.no>,
"James Courtier-Dutton" <james.dutton@gmail.com>,
HoP <jpetrous@gmail.com>, "István Váradi" <ivaradi@gmail.com>
Subject: Re: serial device name for smart card reader that is integrated to Anysee DVB USB device
Date: Wed, 05 Oct 2011 08:58:51 +0300 [thread overview]
Message-ID: <4E8BF21B.4010907@iki.fi> (raw)
In-Reply-To: <20111005045917.GB4700@kroah.com>
On 10/05/2011 07:59 AM, Greg KH wrote:
> On Wed, Oct 05, 2011 at 12:22:09AM +0300, Antti Palosaari wrote:
>> I have been looking for correct device name for serial smart card
>> reader that is integrated to Anysee DVB USB devices. Consider it
>> like old so called Phoenix reader. Phoenix is de facto protocol used
>> for such readers and there is whole bunch of different RS232
>> (/dev/ttyS#) or USB-serial (/dev/ttyUSB#) readers using that
>> protocol.
>>
>> Anyhow, that one is integrated to DVB USB device that is driven by
>> dvb_usb_anysee driver. As I understand, I need reserve new device
>> name and major number for my device. See Documentation/devices.txt
>
> Why not just use the usb-serial core and then you get a ttyUSB* device
> node "for free"? It also should provide a lot of the basic tty
> infrastructure and ring buffer logic all ready to use.
Since I don't see how I can access same platform data from DVB USB and
USB-serial driver (usb_set_intfdata). I asked that earlier, see:
http://www.mail-archive.com/linux-media@vger.kernel.org/msg36027.html
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2011-10-05 5:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 21:22 serial device name for smart card reader that is integrated to Anysee DVB USB device Antti Palosaari
2011-10-05 4:59 ` Greg KH
2011-10-05 5:58 ` Antti Palosaari [this message]
2011-10-05 6:15 ` Oliver Neukum
2011-10-05 6:19 ` Antti Palosaari
2011-10-05 8:16 ` Oliver Neukum
2011-10-14 17:32 ` Oliver Neukum
2011-12-13 16:30 ` Antti Palosaari
2011-12-13 17:41 ` Alan Cox
2011-10-05 7:01 ` Greg KH
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=4E8BF21B.4010907@iki.fi \
--to=crope@iki.fi \
--cc=bjorn@mork.no \
--cc=greg@kroah.com \
--cc=ivaradi@gmail.com \
--cc=james.dutton@gmail.com \
--cc=jpetrous@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-usb@vger.kernel.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