kernelnewbies.kernelnewbies.org archive mirror
 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: Tue, 25 Feb 2014 17:47:14 -0800	[thread overview]
Message-ID: <20140226014714.GA8346@kroah.com> (raw)
In-Reply-To: <3F2A4315-4F2C-4BB1-BC9C-67B6F6BCD3A3@apple.com>

On Tue, Feb 25, 2014 at 01:42:00PM -0500, Michael Sweet wrote:
> Till,
> 
> Some comments inline...
> 
> On Feb 25, 2014, at 12:01 PM, Till Kamppeter <till.kamppeter@gmail.com> wrote:
> > Hi,
> > 
> > a new standard not yet supported under Linux but starting to penetrate
> > the market is IPP-over-USB (Internet Printing Protocol over USB).
> > ...
> > Fortunately, the PWG has added a standard to make it also go into USB
> > printers, IPP-over-USB. Problem is that there is no Linux support for that.
> 
> Actually, it was the USB Implementers Forum (USB-IF) that defined and published the IPP USB specification, not the PWG.
> 
> > First, I want to make a feature request to the kernel to add it.
> 
> I don't think the kernel is the right place for this.  IPP USB isn't
> like IP-over-USB, and you'll want the interface to provide arbitration
> and multiplexing of HTTP requests over the available IPP USB
> interfaces.

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?

Is there a pointer to the spec somewhere so that I can see what is
needed here?

> > Second,
> > I want to suggest this as a Google Summer of Code project, asking for
> > mentors on the kernel side. Mentoring Organization will be the Linux
> > Foundation, hosting projects for both OpenPrinting and the kernel.
> 
> This will make an excellent SoC project, but you'll need someone
> familiar with Avahi, libusb, HTTP, systemd, and general networking for
> this.  This isn't a kernel project.

That's a non-trivial set of experience to try to find, good luck :)

And why systemd?  What is needed from it for this?

thanks,

greg k-h

  reply	other threads:[~2014-02-26  1:47 UTC|newest]

Thread overview: 16+ 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
     [not found] ` <CA+55aFx=5ubeSTcWVcM1bxnjG72fV0vwzTktuqccy1h4-aMScg@mail.gmail.com>
2014-02-25 17:26   ` Till Kamppeter
2014-02-25 18:42 ` [Printing-architecture] " Michael Sweet
2014-02-26  1:47   ` Greg KH [this message]
2014-02-26  1:56     ` Michael Sweet
2014-02-26 17:37       ` Till Kamppeter
2014-02-26 23:02       ` Greg KH
2014-02-27  0:05         ` Michael Sweet
2014-02-27  1:35           ` Greg KH
2014-02-27  2:33           ` Carlos Rimola
2014-02-27 15:37             ` Michael Sweet
2014-02-27 19:23               ` Carlos Rimola
2014-02-27 19:29                 ` Michael Sweet
2014-03-04 22:28                   ` Carlos Rimola
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=20140226014714.GA8346@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 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).