All of lore.kernel.org
 help / color / mirror / Atom feed
From: "P. Christeas" <p_christ@hol.gr>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Oliver Neukum <oliver@neukum.org>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-usb@vger.kernel.org, twaugh@redhat.com
Subject: Re: Patch: usblp quirk for zebra printers
Date: Sun, 25 May 2008 12:03:45 +0300	[thread overview]
Message-ID: <200805251203.49033.p_christ@hol.gr> (raw)
In-Reply-To: <20080521153756.cc701b14.zaitcev@redhat.com>

On Thursday 22 May 2008, Pete Zaitcev wrote:
> On Wed, 21 May 2008 20:57:49 +0300, "P. Christeas" <p_christ@hol.gr> wrote:
> > I guess such a quirk may be a little odd, but it has been a blocking
> > point in my system not being able to support more than one printer.
> Personally, I don't like this. In kernel, we typically try not to
> fake things in lower levels in order to fool upper levels. 
>...
> I'm cc-ing this to Tim Waugh.

I'm now working in a more "politically correct" way around that issue [1]. The 
outline is that we _add_ a backend to CUPS[2], which will bring back USB 
addressing by /dev/.. name. Then, we could implement udev rulesets which will 
create "by-id" symlinks to the usblpX devices. 
My work is at github under "cups-usbbackend".


[1] it is a blocking point for my business, as I cannot attach a second 
printer.
[2] it could remain a complementary package until we really agree we want that 
code mainline.

      reply	other threads:[~2008-05-25  9:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21 17:57 Patch: usblp quirk for zebra printers P. Christeas
2008-05-21 22:37 ` Pete Zaitcev
2008-05-25  9:03   ` P. Christeas [this message]

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=200805251203.49033.p_christ@hol.gr \
    --to=p_christ@hol.gr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oliver@neukum.org \
    --cc=twaugh@redhat.com \
    --cc=zaitcev@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.