public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Ara Avanesyan" <araav@hylink.am>
To: "Josh Boyer" <jdub@us.ibm.com>
Cc: linux-mtd@lists.infradead.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: Software Requirement && DiskOnChip
Date: Fri, 18 Feb 2005 18:41:29 +0400	[thread overview]
Message-ID: <006c01c515c7$ef8c6d40$1000000a@araavanesyan> (raw)
In-Reply-To: 1108735670.7821.3.camel@windu.rchland.ibm.com

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
>
>

  reply	other threads:[~2005-02-18 14:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-17 15:02 Software Requirement && DiskOnChip Ara Avanesyan
2005-02-17 16:24 ` David Woodhouse
2005-02-18 10:17   ` Ara Avanesyan
2005-02-18 14:07     ` Josh Boyer
2005-02-18 14:41       ` Ara Avanesyan [this message]
2005-02-18 14:45         ` Jörn Engel
2005-02-18 14:54         ` Josh Boyer
2005-02-18 15:09           ` Ara Avanesyan
2005-02-18  6:54 ` Raphael Zimmerer
2005-02-18 10:22   ` Ara Avanesyan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='006c01c515c7$ef8c6d40$1000000a@araavanesyan' \
    --to=araav@hylink.am \
    --cc=dwmw2@infradead.org \
    --cc=jdub@us.ibm.com \
    --cc=linux-mtd@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox