All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ara Avanesyan" <araav@hylink.am>
To: "David Woodhouse" <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: supporting DiskOnChip G3
Date: Thu, 16 Dec 2004 15:00:15 +0400	[thread overview]
Message-ID: <002401c4e35e$6d926c40$1000000a@araav> (raw)
In-Reply-To: 1103106287.13016.110.camel@hades.cambridge.redhat.com

ohh, actually I'm noob in the low level world but in any case I have to do 
this porting. accidentally, is there any good book/material that explains 
the mtd structure etc so i won't loose too much time exploring the source 
code blindly... actually i'm doing it for two days already:)

hey, thanks for a great answer!
Ara

----- Original Message ----- 
From: "David Woodhouse" <dwmw2@infradead.org>
To: "Ara Avanesyan" <araav@hylink.am>
Cc: <linux-mtd@lists.infradead.org>
Sent: Wednesday, December 15, 2004 2:24 PM
Subject: Re: supporting DiskOnChip G3


> On Wed, 2004-12-15 at 14:12 +0400, Ara Avanesyan wrote:
>> David,
>>
>> thanks for the answer.
>> the documentation is the easiest part;)
>> http://www.m-systems.com/files/documentation/doc/DOC_G3_512Mb_1Gb_Rev2.0.pdf
>
> Oh, that's interesting. They always used to be very cagey about their
> documentation. I'm glad to see they're making progress -- at first
> glance it looks like we ought to be able to support the device with that
> information.
>
> That would be enough for using YAFFS or JFFS2 on it; if the translation
> layer isn't INFTL (as I suspect it isn't) then we'd also need docs on
> the new translation layer too, if we want to use it in DOS-compatible
> mode.
>
>> so now you have the doc, means you have plans to support it?:)
>
> Yeah -- given some sample hardware and a few spare weeks of spare time,
> I'd be happy to play :)
>
> It shouldn't be _that_ hard to make a driver for it which uses the core
> NAND code. See the existing drivers/mtd/nand/diskonchip.c for
> inspiration and turn up on #mtd of irc.freenode.net. If you're willing
> and capable then we can help you do it -- but if it turns out to be as
> much work to talk you through it as it would be to do it ourselves, then
> it's not going to work too well :)
>
> -- 
> dwmw2
>
> 

      reply	other threads:[~2004-12-16 11:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redirect-100966814@mail5.rambler.ru>
2004-12-15  7:05 ` supporting DiskOnChip G3 Ara Avanesyan
2004-12-15 10:03   ` David Woodhouse
2004-12-15  9:54     ` jasmine
2004-12-15 10:12     ` Ara Avanesyan
2004-12-15 10:24       ` David Woodhouse
2004-12-16 11:00         ` Ara Avanesyan [this message]

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='002401c4e35e$6d926c40$1000000a@araav' \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.