public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Status of the Yaffs patches?
Date: Tue, 29 Apr 2008 07:08:00 +0200	[thread overview]
Message-ID: <200804290708.00897.sr@denx.de> (raw)
In-Reply-To: <20080428214442.21BE3248A6@gemini.denx.de>

On Monday 28 April 2008, Wolfgang Denk wrote:
> > Can anyone give me an update on the status of integrating YAFFS binary
> > image reading and writing into U-Boot?
>
> I think they got lost, most probably because  the  patches  were  not
> posted inline but just as a reference to some URI.

I'm not sure if that's what Stuart is referring to. YAFFS "binary images" can 
be read and written without problems with the current code (since years). You 
need to use the ".jffs2/.i" option for skipping bad blocks.

But if you are referring to the YAFFS filesystem support in U-Boot, then the 
work Wolfgang is referring to is currently available in the mtd-2.6.22.1 
branch of the u-boot-nand-flash repository. I have to admit that I'm not sure 
if the YAFFS support has already been integrated though. Unfortunately this 
branch still has some problems and I didn't get enough feedback/patches to 
fix those problems. So we can't merge this stuff into mainline yet.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  reply	other threads:[~2008-04-29  5:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-28 20:38 [U-Boot-Users] Status of the Yaffs patches? Stuart Wood
2008-04-28 21:44 ` Wolfgang Denk
2008-04-29  5:08   ` Stefan Roese [this message]
2008-04-29 12:54     ` Stuart Wood
2008-04-29 13:27       ` William Juul

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=200804290708.00897.sr@denx.de \
    --to=sr@denx.de \
    --cc=u-boot@lists.denx.de \
    /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