[Openicc] Drop size calibration

[edmund ronald]

It would appear that Barbieri see themselves as a pure manufacturer of
hardware -not software- and would like to set open interface
specifications and export measurements a L*a*b* values, but
unfortunately some of their "firmware" runs on the host platform and
they cannot expose the source to this code  for a reason which I
haven't been told. As we clearly have a device manufacturer
sympathetic to the needs of the open source community here, and who
even says good things about argyll, I think we shouldn't scare them
off, and rather help them actively pursue a solution that would help
the userbase.

As for my virtual box solution, I don't think communicating with the
outside world is hard - if you go to the VMware site you will see a
lot of virtual appliances that implement things like Apache, MySQL or
LAMP and communicate very nicely with the nearby world via TCP/IP,
while guaranteeing the user a stable, tested and preconfigured version
of the target software. I don't think that exposing a port and an HTTP
server that can be sent a request, maybe upload a target definition
file,  and sends back a file with measurements is that hard in 2008.

Edmund

On Feb 4, 2008 8:35 PM, Hal V. Engel <hvengel at astound.net> wrote:

> I have yet to see any well known open source advocate asking any hardware
> vendor to open* the source code for their drivers.  What we want from the
> vendors is open hardware interface specifications.  This is a very different
> thing and is in no way comparable to requesting that the vendors open their
> driver source code.
>
> On the other hand any hardware vendor that actually works with the open source
> community on open source drivers gets extra points.  There are major hardware
> vendors that are currently doing this.  This includes Intel and AMD which are
> clearly the two largest hardware vendors in the world.  In both cases the
> vendors supply specifications for both CPU and GPU hardware to the open
> source community and both vendors are currently providing funding and
> internal staff to provide these specifications and to do some of the open
> source coding activity.
>