All of lore.kernel.org
 help / color / mirror / Atom feed
From: Woodruff, Richard <r-woodruff2@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RE: Nand OOB layout, u-boot and the kernel sources do not agree.. ??
Date: Thu, 24 Jul 2003 12:56:35 -0500	[thread overview]
Message-ID: <FD2AC9A020DDD51194710008C7089B200BEE2212@dlee17.itg.ti.com> (raw)

Looking about infradead.org tells that the OOB area can be reconfigured via
ioctl.  I suppose that this is something which would be needed prior to
mount.  Having more up to date definitions would seem better....as raw nand
doesn't seem to be well supported except with jffs2 & possibly yaffs I don't
suppose the NAND_NOOB is such a concern.
 
Richard W.

-----Original Message-----
From: Woodruff, Richard 
Sent: Thursday, July 24, 2003 12:45 PM
To: u-boot-users at lists.sourceforge.net
Subject: Nand OOB layout, u-boot and the kernel sources do not agree..??


Hello,
 
While trying to resolve what the OOB data layout should be I see that the
kernel headers as of 8-10-2002 have changed such that both the NAND_JFFS2
and NAND_NOOB use position 5 for bad block data.  The u-boot headers do not
reflect this change...doesn't this mean u-boot will be incompatible with
more recent kernels?  Should u-boot's headers be updated here?
 
Regards,
 
Richard W.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20030724/4cc484b9/attachment.htm 

             reply	other threads:[~2003-07-24 17:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-24 17:56 Woodruff, Richard [this message]
2003-07-24 18:59 ` [U-Boot-Users] RE: Nand OOB layout, u-boot and the kernel sources do not agree.. ?? Dave Ellis
2003-07-24 19:13   ` Wolfgang Denk

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=FD2AC9A020DDD51194710008C7089B200BEE2212@dlee17.itg.ti.com \
    --to=r-woodruff2@ti.com \
    --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 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.