From: Andrew Morton <akpm@linux-foundation.org>
To: unsik Kim <donari75@gmail.com>
Cc: linux-kernel@vger.kernel.org, hch@infradead.org,
alan@lxorguk.ukuu.org.uk, shdl@zakalwe.fi,
harvey.harrison@gmail.com, minchan.kim@gmail.com
Subject: Re: [PATCH] mflash: Initial support
Date: Thu, 5 Mar 2009 14:27:46 -0800 [thread overview]
Message-ID: <20090305142746.a2c6f415.akpm@linux-foundation.org> (raw)
In-Reply-To: <57afda040903050124h30bff6fflb9d8dedde966d18c@mail.gmail.com>
On Thu, 5 Mar 2009 18:24:47 +0900
unsik Kim <donari75@gmail.com> wrote:
> 1. ATA layer deals standard ATA protocol. ATA layer have many low-
> level device specific interface, but data transfer keeps ATA rule. But,
> mflash IO mode doesn't.
>
> 2. Even though currently not used in mflash driver code, mflash has
> some custom command and modes. (nand fusing, firmware patch,
> etc) If this feature supported in linux kernel, ATA layer more altered.
>
> 3. Currently PATA platform device driver doesn't support interrupt.
> (I'm not sure) But, mflash uses interrupt (polling mode is just for debug).
>
> 4. mflash is somewhat under-develop product. Even though some
> company already using mflash their own product, I think more time is
> needed for standardization of custom command and mode. That time
> (maybe October) I will talk to with ATA people. If they accept integration,
> I will integrate.
Thsi is fairly important information. Please include it in the changelog
for the patch, and maintain it.
next prev parent reply other threads:[~2009-03-05 22:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 9:31 [PATCH] mflash: Initial support unsik Kim
2009-02-26 21:35 ` Andrew Morton
2009-03-05 9:24 ` unsik Kim
2009-03-05 22:27 ` Andrew Morton [this message]
2009-03-06 2:26 ` unsik Kim
2009-03-06 2:29 ` [PATCH v2] mflash: Initial support v2 unsik Kim
2009-03-06 21:46 ` Andrew Morton
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=20090305142746.a2c6f415.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=donari75@gmail.com \
--cc=harvey.harrison@gmail.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan.kim@gmail.com \
--cc=shdl@zakalwe.fi \
/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