All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eran Liberty <liberty@extricom.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Flash write crash on MPC8548CDS
Date: Mon, 10 Mar 2008 15:11:05 +0000 (UTC)	[thread overview]
Message-ID: <loom.20080310T150412-737@post.gmane.org> (raw)
In-Reply-To: 73457D59-9913-4A70-AC74-BCEF6123B398@kernel.crashing.org

Kumar Gala <galak <at> kernel.crashing.org> writes:
> 
> 
> On Mar 10, 2008, at 7:35 AM, Eran Liberty wrote:
> 
> > Dear Andy,
> >
> > I experience the same behavior as ksi described.
> >
> > I experience this over u-boot-1.3.2-rc3 which should have had this  
> > fixed.
> > I assume you referred to commit	 
> > 21fae8b2b4e4e6e648796e07e20ab13e9cb18923.
> >
> > Are there any follow ups on this subject?
> 
> We pushed a fix and it should be in the 1.3.2 release.
> 
> Look for 'Invalidate INIT_RAM TLB mappings'
> 
> - k
> 

Exactly my point. I have followed up on the suggested patch, made sure it is
indeed in the latest release u-boot-1.3.2-rc3 (it is), And still I get this
behavior.

It is worth mentioning that:
1. It is much easier to reproduce this in flash to flash copy.
2. I am still not 100% sure that my hardware is not acting funny.

Cheers,
Liberty

  reply	other threads:[~2008-03-10 15:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20 19:13 [U-Boot-Users] Flash write crash on MPC8548CDS ksi at koi8.net
2008-02-20 21:00 ` Andy Fleming
2008-02-20 21:07   ` ksi at koi8.net
     [not found]     ` <2acbd3e40802201643x48969f5emd6644a66eb7d9d0@mail.gmail.com>
     [not found]       ` <Pine.LNX.4.64ksi.0802201646190.18544@home-gw.koi8.net>
2008-02-28  0:26         ` Andy Fleming
2008-02-28  0:39           ` ksi at koi8.net
2008-03-10 12:35             ` Eran Liberty
2008-03-10 14:41               ` Kumar Gala
2008-03-10 15:11                 ` Eran Liberty [this message]
2008-03-10 16:38               ` Andy Fleming
2008-03-10 17:05                 ` Eran Liberty
     [not found]                   ` <2acbd3e40803101416h9cb2deay38f16894cca2766f@mail.gmail.com>
     [not found]                     ` <47D63F1B.3070000@extricom.com>
     [not found]                       ` <2acbd3e40803111031n40399ee5q5058b9089df9d6ad@mail.gmail.com>
2008-03-11 18:30                         ` Eran Liberty
2008-03-11 19:08                           ` ksi at koi8.net
2008-03-11 21:06                           ` Andy Fleming
     [not found]                             ` <47D79D72.5030108@extricom.com>
2008-03-12 18:23                               ` Andy Fleming
2008-03-13 15:54                                 ` [U-Boot-Users] dtc n00bie - Flat device Tree nightmare Richard Parsons
2008-03-13 16:20                                   ` Jon Loeliger

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=loom.20080310T150412-737@post.gmane.org \
    --to=liberty@extricom.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.