All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: printing-architecture@lists.linux-foundation.org
Subject: Re: [Printing-architecture] printing architecture for embedded Linux system
Date: Wed, 08 Apr 2015 21:38:02 -0300	[thread overview]
Message-ID: <5525C9EA.4040509@gmail.com> (raw)
In-Reply-To: <CAOd_LFx_Vz3ZKp6bauA6vFRV_gLrXAJX16NFw4tPiMn-eAV0XA@mail.gmail.com>

Hi,

unfortunately, the HPLIP developers have discontinued the HPIJS driver 
already some time ago. Support for new models is only added to the 
hpcups driver. The HPIJS driver is still included in the package but 
only supports older printers and standard PCL 5c/e laser printers.

The hpcups driver can also be used without the CUPS daemon, but it needs 
the CUPS libraries to support the CUPS Raster input format. Ghostscript 
is not needed, you simply need to generate CUPS Raster for feeding into 
hpcups.

    Till

On 08.04.2015 18:46, Cliff Brake wrote:
> Hi,
>
> We've been using the hpijs printer driver in an embedded system for a
> number of years very successfully.
>
> http://bec-systems.com/site/218/printing-from-embedded-systems
>
> However, it seems that newer printers are not supported by the hpijs driver:
>
> https://answers.launchpad.net/hplip/+question/264258
>
> Does anyone have suggestions for a printing architecture going forward
> -- we'd prefer not to ship cups+ghostscript in our system due to size.
>
> Or, are there printer vendors who still use ijs drivers?
>
> Thanks,
> Cliff
> _______________________________________________
> Printing-architecture mailing list
> Printing-architecture@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/printing-architecture
>


      reply	other threads:[~2015-04-09  0:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 21:46 [Printing-architecture] printing architecture for embedded Linux system Cliff Brake
2015-04-09  0:38 ` Till Kamppeter [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=5525C9EA.4040509@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=printing-architecture@lists.linux-foundation.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.