All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [Printing-architecture] Google Summer of Code 2014 - IPP-over-USB printer support - Joint project idea for OpenPrinting and the kernel
Date: Wed, 26 Feb 2014 15:02:47 -0800	[thread overview]
Message-ID: <20140226230247.GA8283@kroah.com> (raw)
In-Reply-To: <8E2929D6-4A60-4D27-9012-5250503D9B51@apple.com>

On Tue, Feb 25, 2014 at 08:56:23PM -0500, Michael Sweet wrote:
> Greg,
> 
> On Feb 25, 2014, at 8:47 PM, Greg KH <greg@kroah.com> wrote:
> > ...
> > So you want to do this as a userspace library talking directly to the
> > USB device through usbfs/libusb?  Or should the kernel provide a basic
> > "pipe-like" functionality to the hardware to make it easier for things
> > to be queued up to the device?
> 
> libusb is enough.
> 
> > Is there a pointer to the spec somewhere so that I can see what is
> > needed here?
> 
> http://www.usb.org/developers/devclass_docs

In reading the spec, it looks like some kernel code will have to be
written, as the default configuration for the printer device will cause
the usblp driver to bind to the device.  Are you thinking that libusb
will just unbind the printer driver and take over from there?  Why not
just use the kernel driver to expose another device node and have cups
talk to that?

thanks,

greg k-h

  parent reply	other threads:[~2014-02-26 23:02 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25 17:01 Google Summer of Code 2014 - IPP-over-USB printer support - Joint project idea for OpenPrinting and the kernel Till Kamppeter
2014-02-25 17:01 ` [Printing-architecture] " Till Kamppeter
     [not found] ` <CA+55aFx=5ubeSTcWVcM1bxnjG72fV0vwzTktuqccy1h4-aMScg@mail.gmail.com>
2014-02-25 17:26   ` Till Kamppeter
2014-02-25 17:26     ` [Printing-architecture] " Till Kamppeter
2014-02-25 18:42 ` Michael Sweet
2014-02-25 18:42   ` Michael Sweet
2014-02-26  1:47   ` Greg KH
2014-02-26  1:56     ` Michael Sweet
2014-02-26  1:56       ` Michael Sweet
2014-02-26 17:37       ` Till Kamppeter
2014-02-26 17:37         ` Till Kamppeter
2014-02-26 23:02       ` Greg KH [this message]
2014-02-27  0:05         ` Michael Sweet
2014-02-27  0:05           ` Michael Sweet
2014-02-27  1:35           ` Greg KH
2014-02-27  2:33           ` Carlos Rimola
2014-02-27  2:33             ` Carlos Rimola
2014-02-27 15:37             ` Michael Sweet
2014-02-27 15:37               ` Michael Sweet
2014-02-27 19:23               ` Carlos Rimola
2014-02-27 19:23                 ` Carlos Rimola
2014-02-27 19:29                 ` Michael Sweet
2014-02-27 19:29                   ` Michael Sweet
2014-03-04 22:28                   ` Carlos Rimola
2014-03-04 22:28                     ` Carlos Rimola
2014-03-05  1:00                     ` Michael Sweet
2014-03-05  1:00                       ` Michael Sweet
2014-02-26 22:31 ` Valdis.Kletnieks at vt.edu

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=20140226230247.GA8283@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 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.