Re: hplip and use of the "driver plugin"

From	Jape Person <japers@comcast.net>
Newsgroups	linux.debian.user
Subject	Re: hplip and use of the "driver plugin"
Date	2016-11-19 22:40 +0100
Message-ID	<sFlwB-1RM-1@gated-at.bofh.it> (permalink)
References	(1 earlier) <sFeY9-68F-7@gated-at.bofh.it> <sFgdA-6QV-21@gated-at.bofh.it> <sFgQh-7nf-11@gated-at.bofh.it> <sFiyJ-5C-39@gated-at.bofh.it> <sFk7v-18g-15@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On 11/19/2016 03:09 PM, Brian wrote:
> On Sat 19 Nov 2016 at 13:21:23 -0500, Jape Person wrote:
>
>> On 11/19/2016 11:31 AM, Henrique de Moraes Holschuh wrote:
>>> On Sat, 19 Nov 2016, Brian wrote:
>>>>> I'd like to know that, too.  I need a new home color printer, my
>>>>> 10-year-old HP PhotoSmart (blobless) MFP has finally broken down and
>>>>> good second-hand parts are not easy to find in Brazil :-(
>>>>
>>>> Why is it important for the printer to be blobless? Look at it this way:
>>>
>>> Are we talking about printer firmware, or host-cpu device drivers?
>>>
>>> All of your reply is only relevant for device firmware (runs in the
>>> device).  But I thought this was about a binary-only driver blob that
>>> runs in the host OS ?  Or did I misunderstand?
>>>
>> I'm pretty sure it's a host-cpu device driver.
>>
>> http://hplipopensource.com/node/309
>
> Sorry to be awkward, but what does "it's" refer to?
>

Uh, I'm the awkward one here. That's why I'm asking for help.

> The plugin contains *.fw files and libraries. A firmware file is uploaded to
> the printer when it is switched on. Quite what the libraries do I do not
> know but my assumption is they are involved in this and the host-based
> management of the printer. Enlightenment would be appreciated.
>

Let's not start with unreasonable expectations. The likelihood that I 
will enlighten you in such a matter is vanishingly small.

I didn't find any information this specific about the driver plugin. If 
you can steer me toward the relevant information I would appreciate it. 
I read information at all the links that seemed as though they could be 
pertinent from the hplipopensource.com location.

So, are you saying that nothing within that driver plugin gets invoked 
by or interacts with the host system? It's just some firmware that gets 
copied to the printer and some libraries which reside on the host and 
which interact with the printer. If that's the case, then my concern 
about the driver plugin is a tempest in a teapot.

It still would seem to beg the question as to why the system would be 
designed this way. But I'm not a printer hardware designer, and I don't 
know what requirements are placed on those guys by the production and 
delivery schedules. Maybe it's just a workaround to help HP get the most 
up-to-date stuff out the door in the most timely manner possible.

At any rate, I can probably fulfill my requirements my buying a little 
more hardware than I had originally intended. And I appreciate the 
efforts you and Henrique have made on my behalf.

If I should learn anything interesting from HP tech support I'll try to 
come back with it.

Thread

hplip and use of the "driver plugin" Jape Person <japers@comcast.net> - 2016-11-19 02:40 +0100
  Re: hplip and use of the "driver plugin" Brian <ad44@cityscape.co.uk> - 2016-11-19 12:50 +0100
    Re: hplip and use of the "driver plugin" Jape Person <japers@comcast.net> - 2016-11-19 19:00 +0100
  Re: hplip and use of the "driver plugin" Henrique de Moraes Holschuh <hmh@debian.org> - 2016-11-19 15:40 +0100
    Re: hplip and use of the "driver plugin" Brian <ad44@cityscape.co.uk> - 2016-11-19 17:00 +0100
      Re: hplip and use of the "driver plugin" Henrique de Moraes Holschuh <hmh@debian.org> - 2016-11-19 17:40 +0100
        Re: hplip and use of the "driver plugin" Brian <ad44@cityscape.co.uk> - 2016-11-19 18:40 +0100
        Re: hplip and use of the "driver plugin" Jape Person <japers@comcast.net> - 2016-11-19 19:30 +0100
          Re: hplip and use of the "driver plugin" Brian <ad44@cityscape.co.uk> - 2016-11-19 21:10 +0100
            Re: hplip and use of the "driver plugin" Jape Person <japers@comcast.net> - 2016-11-19 22:40 +0100
              Re: hplip and use of the "driver plugin" Brian <ad44@cityscape.co.uk> - 2016-11-20 21:00 +0100
                Re: hplip and use of the "driver plugin" Jape Person <japers@comcast.net> - 2016-11-21 00:00 +0100
                Re: hplip and use of the "driver plugin" "James P. Wallen" <jpwallen@comcast.net> - 2016-11-21 00:20 +0100
                Re: hplip and use of the "driver plugin" Richard Hector <richard@walnut.gen.nz> - 2016-11-23 12:30 +0100
                Re: hplip and use of the "driver plugin" <tomas@tuxteam.de> - 2016-11-23 13:00 +0100
                Re: hplip and use of the "driver plugin" Gene Heskett <gheskett@shentel.net> - 2016-11-23 15:10 +0100
                Re: hplip and use of the "driver plugin" Brian <ad44@cityscape.co.uk> - 2016-11-24 19:30 +0100
            Re: hplip and use of the "driver plugin" Brian <ad44@cityscape.co.uk> - 2016-11-24 21:50 +0100
      Re: hplip and use of the "driver plugin" <tomas@tuxteam.de> - 2016-11-19 18:10 +0100
        Re: hplip and use of the "driver plugin" Brian <ad44@cityscape.co.uk> - 2016-11-19 18:50 +0100
      Re: hplip and use of the "driver plugin" Jape Person <japers@comcast.net> - 2016-11-19 19:20 +0100
        Re: hplip and use of the "driver plugin" Brian <ad44@cityscape.co.uk> - 2016-11-19 20:50 +0100
          Re: hplip and use of the "driver plugin" Jape Person <japers@comcast.net> - 2016-11-19 22:30 +0100
            Re: hplip and use of the "driver plugin" Brian <ad44@cityscape.co.uk> - 2016-12-04 20:00 +0100
              Re: hplip and use of the "driver plugin" Jape Person <japers@comcast.net> - 2016-12-06 04:10 +0100
    Re: hplip and use of the "driver plugin" Jape Person <japers@comcast.net> - 2016-11-19 19:10 +0100
      Re: hplip and use of the "driver plugin" Lisi Reisz <lisi.reisz@gmail.com> - 2016-11-21 23:30 +0100
  Re: hplip and use of the "driver plugin" Jape Person <japers@comcast.net> - 2016-12-03 19:20 +0100
    Re: hplip and use of the "driver plugin" Lisi Reisz <lisi.reisz@gmail.com> - 2016-12-03 20:20 +0100
      Re: hplip and use of the "driver plugin" Jape Person <japers@comcast.net> - 2016-12-03 21:20 +0100
        Re: hplip and use of the "driver plugin" Lisi Reisz <lisi.reisz@gmail.com> - 2016-12-04 12:50 +0100
          Re: hplip and use of the "driver plugin" rhkramer@gmail.com - 2016-12-04 16:00 +0100
            Re: hplip and use of the "driver plugin" Lisi Reisz <lisi.reisz@gmail.com> - 2016-12-04 16:50 +0100
            Re: hplip and use of the "driver plugin" Jape Person <japers@comcast.net> - 2016-12-06 04:00 +0100
              Re: hplip and use of the "driver plugin" Lisi Reisz <lisi.reisz@gmail.com> - 2016-12-07 00:50 +0100
                Re: hplip and use of the "driver plugin" Jape Person <japers@comcast.net> - 2016-12-07 02:50 +0100
                Re: hplip and use of the "driver plugin" Richard Hector <richard@walnut.gen.nz> - 2016-12-07 09:00 +0100
                Re: hplip and use of the "driver plugin" Jape Person <japers@comcast.net> - 2016-12-07 16:20 +0100
      Re: hplip and use of the "driver plugin" Brian <ad44@cityscape.co.uk> - 2016-12-03 21:30 +0100
        Re: hplip and use of the "driver plugin" Jape Person <japers@comcast.net> - 2016-12-03 21:40 +0100
          Re: hplip and use of the "driver plugin" Marc Shapiro <marcnshap@gmail.com> - 2016-12-06 00:40 +0100
            Re: hplip and use of the "driver plugin" Jape Person <japers@comcast.net> - 2016-12-06 04:10 +0100
              Re: hplip and use of the "driver plugin" Marc Shapiro <marcnshap@gmail.com> - 2016-12-06 06:40 +0100
        Re: hplip and use of the "driver plugin" Fred <fred@blakemfg.com> - 2016-12-04 02:00 +0100
          Re: hplip and use of the "driver plugin" Jape Person <japers@comcast.net> - 2016-12-04 06:40 +0100

csiph-web