From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from host-216-252-217-242.interpacket.net ([216.252.217.242]
	helo=forof.hylink.am)
	by canuck.infradead.org with esmtps (Exim 4.43 #1 (Red Hat Linux))
	id 1D29KO-0007eK-By
	for linux-mtd@lists.infradead.org; Fri, 18 Feb 2005 09:41:58 -0500
Message-ID: <006c01c515c7$ef8c6d40$1000000a@araavanesyan>
From: "Ara Avanesyan" <araav@hylink.am>
To: "Josh Boyer" <jdub@us.ibm.com>
References: <200502171502.j1HF2OtT044879@forof.hylink.am>
	<1108657458.19262.671.camel@hades.cambridge.redhat.com>
	<005401c515a3$166ef470$1000000a@araavanesyan>
	<1108735670.7821.3.camel@windu.rchland.ibm.com>
Date: Fri, 18 Feb 2005 18:41:29 +0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="koi8-r"
Content-Transfer-Encoding: 7bit
Cc: linux-mtd@lists.infradead.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: Software Requirement && DiskOnChip
List-Id: Linux MTD discussion mailing list <linux-mtd.lists.infradead.org>
List-Unsubscribe: <http://lists.infradead.org/mailman/listinfo/linux-mtd>,
	<mailto:linux-mtd-request@lists.infradead.org?subject=unsubscribe>
List-Archive: <http://lists.infradead.org/pipermail/linux-mtd>
List-Post: <mailto:linux-mtd@lists.infradead.org>
List-Help: <mailto:linux-mtd-request@lists.infradead.org?subject=help>
List-Subscribe: <http://lists.infradead.org/mailman/listinfo/linux-mtd>,
	<mailto:linux-mtd-request@lists.infradead.org?subject=subscribe>

ok,

My question is from theory only:)
Can't then the driver writer copy-paste the documentation to source files as
comment? really...
And what could be the reason to not sharing the hardware documentation to
the community???

__
Thanks,
Ara


----- Original Message ----- 
From: "Josh Boyer" <jdub@us.ibm.com>
To: "Ara Avanesyan" <araav@hylink.am>
Cc: "David Woodhouse" <dwmw2@infradead.org>; <linux-mtd@lists.infradead.org>
Sent: Friday, February 18, 2005 6:07 PM
Subject: Re: Software Requirement && DiskOnChip


> On Fri, 2005-02-18 at 14:17 +0400, Ara Avanesyan wrote:
> > David,
> >
> > Thanks. I'll contact M-System for the document.
> > Bah! This somewhat violates my [very basic]
> > understanding of open source community. It's
> > something like "open source and close source of
> > source". Couldn't the driver writer (you:)) put the
> > document to the source tree documentation part?
>
> I don't think so.  The source code is definitely open source.  The
> hardware documentation is whatever the vendor decides it should be.  In
> this case, M-Systems decided that it should not be public, IIRC.
>
> josh
>
>