On Mon 2008-07-07 21:49:05, Arjan van de Ven wrote:
quoted text
> On Mon, 7 Jul 2008 21:41:41 -0700 (PDT)
> david@lang.hm wrote:
> > umm, by merging the code a you reveal a lot of what they are
> > attempting to keep secret. what's to stop someone from reading the
> > code and writing the documentation?
> > 
> > that really should be someone at HP if you don't want to publish the 
> > exising documentation (since you are submitting the code)
> 
> I think you're being quite unreasonable here.
> In Linux we accept well written drivers even if there is no hardware
> docs. Sure we prefer them to be available, but is has never been a

This is not well-written driver. This is a layer that provides access
to hardware from userspace - AFAICT. But we are not told what hardware
does, nor how to control it.

Imagine a PC speaker "driver" that has two functions:

* write this to port 0x60

* write this to port 0x64

...and you don't get docs for the pc speaker. Only think that can use
your "driver" is proprietary binary. (Actually, in this case you are
not even told it is a pc speaker.)

I don't think that's acceptable...
								Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/