From mboxrd@z Thu Jan  1 00:00:00 1970
From: greg@kroah.com (Greg KH)
Date: Wed, 26 Feb 2014 15:02:47 -0800
Subject: [Printing-architecture] Google Summer of Code 2014 -
	IPP-over-USB printer support - Joint project idea for OpenPrinting and
	the kernel
In-Reply-To: <8E2929D6-4A60-4D27-9012-5250503D9B51@apple.com>
References: <530CCC53.8070007@gmail.com>
	<3F2A4315-4F2C-4BB1-BC9C-67B6F6BCD3A3@apple.com>
	<20140226014714.GA8346@kroah.com>
	<8E2929D6-4A60-4D27-9012-5250503D9B51@apple.com>
Message-ID: <20140226230247.GA8283@kroah.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

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