From: Martin Michlmayr <tbm@cyrius.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>
Cc: linux-mtd@lists.infradead.org,
Yoshinori Sato <ysato@users.sourceforge.jp>,
buytenh@wantstofly.org
Subject: Re: Oops parsing empty RedBoot partition with 2.6.20-rc7
Date: Fri, 2 Feb 2007 18:57:55 +0100 [thread overview]
Message-ID: <20070202175755.GG24587@deprecation.cyrius.com> (raw)
In-Reply-To: <0C7297FA1D2D244A9C7F6959C0BF1E520148F6A0@azsmsx413.amr.corp.intel.com>
* Williams, Dan J <dan.j.williams@intel.com> [2007-02-02 10:22]:
> > With current git (2.6.20-rc7) I get the following oops when it's
> > trying to parse the RedBoot partition. This is on an IOP13xx based
> > board (Intel iq81340mc). I guess the problm happens because I don't
> > have any RedBoot partitions. Note that 2.6.19 work fine.
> >
> I am seeing this as well. After a 'fis init' it starts working, but our
> customer reference boards normally ship without a partition table. As
> you said this works fine on 2.6.19. You may be able to do a 'git
> bisect' if iop13xx support was added before this regression...
It was caused by:
commit 0b47d654089c5ce3f2ea26a4485db9bcead1e515
Author: Yoshinori Sato <ysato@users.sourceforge.jp>
Date: Fri Dec 1 10:01:50 2006 +0000
[MTD] redboot partition combined fis / config problem
Can't analyze FIS directory in CYGSEM_REDBOOT_FLASH_COMBINED_FIS_AND_CONFIG
really.
--
Martin Michlmayr
http://www.cyrius.com/
next prev parent reply other threads:[~2007-02-02 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-02 15:56 Oops parsing empty RedBoot partition with 2.6.20-rc7 Martin Michlmayr
2007-02-02 17:22 ` Williams, Dan J
2007-02-02 17:57 ` Martin Michlmayr [this message]
2007-02-02 18:14 ` Martin Michlmayr
2007-02-09 15:07 ` David Woodhouse
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=20070202175755.GG24587@deprecation.cyrius.com \
--to=tbm@cyrius.com \
--cc=buytenh@wantstofly.org \
--cc=dan.j.williams@intel.com \
--cc=linux-mtd@lists.infradead.org \
--cc=ysato@users.sourceforge.jp \
/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.