linux-kernel - Re: [PATCH] mflash: Initial support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20090305142746.a2c6f415.akpm@linux-foundation.org>
Date:	Thu, 5 Mar 2009 14:27:46 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	unsik Kim <donari75@...il.com>
Cc:	linux-kernel@...r.kernel.org, hch@...radead.org,
	alan@...rguk.ukuu.org.uk, shdl@...alwe.fi,
	harvey.harrison@...il.com, minchan.kim@...il.com
Subject: Re: [PATCH] mflash: Initial support

On Thu, 5 Mar 2009 18:24:47 +0900
unsik Kim <donari75@...il.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/