All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Underwood <steveu@coppice.org>
To: Tim Waugh <twaugh@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB IEEE1284 gadgets and ppdev
Date: Tue, 01 Oct 2002 23:35:53 +0800	[thread overview]
Message-ID: <3D99C0D9.7060704@coppice.org> (raw)
In-Reply-To: 20020925150915.GM9457@redhat.com

Tim Waugh wrote:

>On Wed, Sep 25, 2002 at 08:01:29AM -0700, Greg KH wrote:
>
>  
>
>>I understand that the uss720 driver should register with parport, as
>>it is a USB to parallel port adapter, but the usblp driver should
>>not, as it is just a pass-through to a printer.  Do you see any
>>advantage to having usblp registering with parport?
>>    
>>
>
>Well, it would mean that ppdev could use it.  I understand that only a
>few functions of a normal parallel port could be implemented (read,
>write, get status).
>
>Alternatively I suppose I could get libieee1284 to grok /dev/usb/lp*.
>Steve---would that solve the problem that you're running into?
>
>Tim.
>*/
>  
>
Well, the application is this. A lot of industrial control, embedded 
processor development interfaces, and other stuff use a parallel port to 
connect to a PC. The parallel port has gone from some notebooks, and is 
soon to go from desktops too. I want to access some of those devices 
through a USB to IEEE1284 cable. If the programming interface is ppdev, 
that is great - no changes needed for code that already works with a 
real parallel port. If it requires a somewhat different API, that's no 
big deal. Being able to bit twiddle to the extent that ppdev allows is 
pretty important, though. I guess there may be some latency issues 
slowing the bit twiddling across a USB interface, but nothing's perfect.

Regards,
Steve



  reply	other threads:[~2002-10-01 15:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-24 15:22 USB IEEE1284 gadgets and ppdev Steve Underwood
2002-09-24 16:21 ` Tim Waugh
2002-09-25 13:51   ` Steve Underwood
2002-09-25 14:27     ` Tim Waugh
2002-09-25 15:01       ` Greg KH
2002-09-25 15:09         ` Tim Waugh
2002-10-01 15:35           ` Steve Underwood [this message]
2002-10-01 16:23             ` Tim Waugh

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=3D99C0D9.7060704@coppice.org \
    --to=steveu@coppice.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=twaugh@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.