From: "Ara Avanesyan" <araav@hylink.am>
To: "David Woodhouse" <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Software Requirement && DiskOnChip
Date: Fri, 18 Feb 2005 14:17:43 +0400 [thread overview]
Message-ID: <005401c515a3$166ef470$1000000a@araavanesyan> (raw)
In-Reply-To: 1108657458.19262.671.camel@hades.cambridge.redhat.com
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?
__
Thanks,
Ara
----- Original Message -----
From: "David Woodhouse" <dwmw2@infradead.org>
To: "Ara Avanesyan" <araav@hylink.am>
Cc: <linux-mtd@lists.infradead.org>
Sent: Thursday, February 17, 2005 8:24 PM
Subject: Re: Software Requirement && DiskOnChip
> On Thu, 2005-02-17 at 19:02 +0400, Ara Avanesyan wrote:
> > Everywhere in DiskOnChip files there are referneces to a magic
> > "Software Requirement 11.x.y".
> > Can someone please tell me where can I locate one?
> >
> > Also, where can I find the descriptions of the registers
> > DoC_Mplus_FlashControl through DoC_Mplus_WritePipeTerm
> > defined in doc2000.h? The data-sheet for MPlus DOC device does not
> > contain this info.
>
> Unfortunately I don't think these are publicly available. Although I
> have a vague recollection of being corrected last time I said that.
>
> --
> dwmw2
>
>
next prev parent reply other threads:[~2005-02-18 10:18 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 [this message]
2005-02-18 14:07 ` Josh Boyer
2005-02-18 14:41 ` Ara Avanesyan
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='005401c515a3$166ef470$1000000a@araavanesyan' \
--to=araav@hylink.am \
--cc=dwmw2@infradead.org \
--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