Re: [Printing-architecture] Embedded printing

["chirag Shah" <chirag.shah@einfochips.com>]

[-- Attachment #1: Type: text/plain, Size: 10286 bytes --]

Hi Matt,

Thanks for your responce. But i need complete details on this as i am new to linux and especially for printing. 
Let me explain my experiments and assumptions:
  a.. My montavista kernel is having support for CUPS but not of ghostscripts, hpijs and libijs. I tried to print .jpg images directly to the HP b/w printer, it worked fine. But when i tried to print .txt or .vi file having normal text, its not getting printed. So i assumed that my kernel is not having support to creaete .PS files and to convert .PS files in to printable form.
  b.. So, i am trying to cross-compile ghostscipt code for my arm-v5t-le compiler. I changed configure files to make this happen. I will share the end result of my cross-compiling once its over.
  c.. Before cross compiling of ghostscript, I also tried to build hpijs code (which is part of my shost script source package) independently (to run hpijs_client_example), but i think it is not getting some function definitions which are in some libraries. So i am playing a gamble to cross-compile ghost script on my ARM board.
I am expecting from you:
  a.. In one liner, i need everything working for HP laserjet printer from you. I dont want to spent time on this as we are developing application not the driver / system support package for this project.
  b.. How could i convert my report file (can have text and images both) in to raster data. I think this is done by ghost script.
  c.. How hpijs will be useful to me without ghost script? Frenkly speaking i want to know what exactly hpijs and libijs are for ? As per my understandings, hpijs are using ghostscripts and without ghostscript , i can not use hpijs.
  d.. can you please provide complete source code package with installation and running steps to make HP printer working ? I think this will be good to not to spent more time on something which is proven and discovered. 
Thanks in advance.
Regards,
Chirag Shah
  ----- Original Message ----- 
  From: Matt Gessner 
  To: chirag Shah 
  Cc: printing-architecture@lists.linux-foundation.org 
  Sent: Sunday, November 23, 2008 6:41 PM
  Subject: Re: [Printing-architecture] Embedded printing


  Hi,

  What we ended up doing is invoking hp via fork() and exec(), with a pipe dup'd over the new process's stdout.

  Then we did a fork() and exec() and started hp, and set the OutputFD parameter to the hp's dup'd stdout pipe fd.

  Then we used the ijs_client commands (taken from the ijs_client_example, mostly) to get the printing done.

  Part of our system creates the raster in memory before invoking the printing.  We had to previously agree on the resolution (150x150 -- we're low on memory) and a full 8.5x11.0 page.  Then I simply converted the raster from ARGB to RGB (being careful of the system endianness!) 

  If you would like me to post more details, I'd be happy to do that.  Sometimes people like to figure things out themselves.

  It works pretty darn well.  One thing to watch is that you get the PrintableTopLeft value via ijs_client_get_parm() because it will affect how your page looks if you want a margin that's greater than the built in one on the printer.

  We used no cups, and no ghostscript.  Another person on the team figured out how to get it into OE.  I can give you the basics for compiling everything if you want it.

  You need hp, which requires hpmud for USB comms.  You also need hpijs (which builds the commands and spits them to OutputFD) and libijs (which is the ijs client stuff).

  This was one of several approaches I tried to make this work.  It's the only one that works.

  Oh, I also tore into the ghostscript code to see how it used the hpijs tool, and that provided an interesting detail or two that saved me some time.  The rest I figured out via experimentation.

  I hope this helps.

  Regards,

  Matt


  On Thu, Nov 20, 2008 at 12:22 AM, chirag Shah <chirag.shah@einfochips.com> wrote:

    Hi All,

    Sorry to copy paste whole thread as i did not find any button to post reply on continued thread. Anyway doesn't matter.
    What i would like to ask is, i am in the simillar situation as "Matt". 

    I am developing an embedded system in which i need to give support of laser printers. I am having monta vista linux 2.6 on my ARM based embedded board. In that basic kernel i am having support of CUPS through which i was able to print only .jpg files. I used lp commands to print .jpg file. But my end goal is to print a report which can have text and images combined on same page. I am not able to print a simple .txt or .vi file.

    For that, i believe i need ghost script support. But my monta vista linux is not having support for ghost script. I tried to cross-compile ghost script source with my arm tool-chain but it failed.

    So, how can i add support of laser printers in my embedded(ARM based) system?

    Thanks in advance,
    Chirag Shah (A new member eager for favorable reply :) )



    Matt Gessner magembcons at gmail.com 
    Mon Oct 13 10:46:18 PDT 2008 

      a.. Previous message: [Printing-architecture] Embedded printing 
      b.. Next message: [Printing-architecture] CANCEL - Next OP SC - Mon/Tue - 13/14 October 2008 
      c.. Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] 

----------------------------------------------------------------------------

Hello, and thank you.

Is the HPIJS solution part of the HPLIP solution?  Or is it something
different?

On the web page, http://www.linuxprinting.org/ijs there are some drivers
listed, but I'm confused as to where to go from there?

Also, is there a web page that describes in detail what I need?  Something
that lays out the architecture of what needs to be done by applications (do
I need lpd, CUPS, or something else?)  I've skimmed lots of documentation,
so perhaps I've missed something in my skimming that would answer all my
questions.

THanks lots,

Matt

On Mon, Oct 13, 2008 at 12:33 PM, Petrie, Glen
<glen.petrie at eitc.epson.com>wrote:

>  Matt,
>
>
>
> For embedded solutions, IJS (for Epson and others) or HPIJS (for HP
> printers) is a suggestion.  It is small, MIT open-source driver; and,
> print-vender drivers typically do not have floating point.   (Contact me for
> a CD of Epson's version of the IJS.)
>
>
>
> Epson also has a generic, platform independent, non-floating driver for
> their desktop inkjet printer. (Contact me if you are interested.)
>
>
>
> glen
>
>
>   ------------------------------
>
> *From:* printing-architecture-bounces at lists.linux-foundation.org [mailto:
> printing-architecture-bounces at lists.linux-foundation.org] *On Behalf Of *Matt
> Gessner
> *Sent:* Sunday, October 12, 2008 6:33 PM
> *To:* printing-architecture at lists.linux-foundation.org
> *Subject:* [Printing-architecture] Embedded printing
>
>
>
> Hi,
>
> I''m looking for some solutions for doing printing on an embedded system
> (arm, if it matters).  Raster screen shots and simple text reports are
> (pretty much) all that's desired.
>
> One objective is to avoid using anything that requires floating point math,
> as it's only emulated on this particular arm.
>
> I've been searcing the lists and can't find anything specific to embedded
> systems, but in an O'Reilly article from 2007, there's a note that such
> capabilities would be added in 6 months.  Since we're well past that date,
> I'm wondering if that's been tackled.
>
> Would someone please point me to some resources where I could read up on
> how to do printing on such a system?  I will continue to do my own research,
> but it sure seems like this is an area where there would be some discussion
> so I'm hoping this is the right list.
>
> Thank you.


-- 
_____________________________________________________________________
Disclaimer: This e-mail message and all attachments transmitted with it
are intended solely for the use of the addressee and may contain legally
privileged and confidential information. If the reader of this message
is not the intended recipient, or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby
notified that any dissemination, distribution, copying, or other use of
this message or its attachments is strictly prohibited. If you have
received this message in error, please notify the sender immediately by
replying to this message and please delete it from your computer. Any
views expressed in this message are those of the individual sender
unless otherwise stated.Company has taken enough precautions to prevent
the spread of viruses. However the company accepts no liability for any
damage caused by any virus transmitted by this email.
_____________________________________________________________________
 



    _______________________________________________
    Printing-architecture mailing list
    Printing-architecture@lists.linux-foundation.org
    https://lists.linux-foundation.org/mailman/listinfo/printing-architecture





        Email Scanned for Virus & Dangerous Content by : www.CleanMailGateway.com 

--
_____________________________________________________________________
Disclaimer: This e-mail message and all attachments transmitted with it
are intended solely for the use of the addressee and may contain legally
privileged and confidential information. If the reader of this message
is not the intended recipient, or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby
notified that any dissemination, distribution, copying, or other use of
this message or its attachments is strictly prohibited. If you have
received this message in error, please notify the sender immediately by
replying to this message and please delete it from your computer. Any
views expressed in this message are those of the individual sender
unless otherwise stated.Company has taken enough precautions to prevent
the spread of viruses. However the company accepts no liability for any
damage caused by any virus transmitted by this email.
_____________________________________________________________________


[-- Attachment #2: Type: text/html, Size: 20068 bytes --]