From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jerry Van Baren Date: Thu, 03 Jul 2008 20:57:58 -0400 Subject: [U-Boot-Users] u-boot and OneNAND In-Reply-To: <9c9fda240807022351q14443917n6345049f5c01d7e5@mail.gmail.com> References: <7ff602fb0807020455j643f9ce9w49ec8c1a14206b6a@mail.gmail.com> <9c9fda240807022158v9636510ia177c68b49c0bbf2@mail.gmail.com> <9c9fda240807022351q14443917n6345049f5c01d7e5@mail.gmail.com> Message-ID: <486D7596.9050001@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Kyungmin Park wrote: > On Thu, Jul 3, 2008 at 1:58 PM, Kyungmin Park wrote: >> Hi, >> >> On Wed, Jul 2, 2008 at 8:55 PM, Mile Davidovic wrote: >>> Hello >>> If I read code correctly u-boot have OneNAND driver. But when I check JFFS2 >>> in u-boot it seems that JFFS2 can not work on OneNAND. >> Yes, it's not yet implemented. >> > > Feel free to use this patch. > the mtdparts and fsload is working, but I'm not suer it's working correctly. > > Thank you, > Kyungmin Park > --- > diff --git a/common/cmd_jffs2.c b/common/cmd_jffs2.c > index 1b67e73..51c742c 100644 > --- a/common/cmd_jffs2.c > +++ b/common/cmd_jffs2.c I don't know what the rest of the list thinks, but I would like to see a "Signed-off-by" line (and/or a note on where the code came from - e.g. linux) on all patches whether they are preliminary or not. I would hate to get into a "where did this code come from" quandary over a code that came from, was influenced by, or simply looked like a patch that was posted without proper traceability. Thanks, gvb