All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] non SPL boot on beagleboard-xm
Date: Wed, 25 Jan 2012 18:53:20 +0100	[thread overview]
Message-ID: <201201251853.20895.marek.vasut@gmail.com> (raw)
In-Reply-To: <4F203A6F.40305@ti.com>

> On 01/25/2012 08:43 AM, Peter Meerwald wrote:
> > Hello Tom,
> > 
> >>> MLO/SPL + current u-boot breaks the USB ethernet patches (i.e. booting
> >>> via tftp)
> >> 
> >> Even with 'dc off' before you start usb?
> > 
> > I was not aware of the u-boot command 'dc off' -- yes, it solve my USB
> > ethernet problem
> > 
> > here is my story (from bisecting):
> > 
> > v2011.06 + Koen et al. patches (git://github.com/koenkooi/u-boot.git)
> > works
> > 
> > shortly afterwards, dcache was enabled (commit
> > c2dd0d45540397704de9b13287417d21049d34c6) and USB ethernet fails
> > 
> > v2011.09 works if using 'dc off' before 'usb start' (I tried it as a
> > recent non-SPL u-boot version)
> > 
> > u-boot current (137703b811502dfea364650fb3e17f20b4c21333) works as well
> > with 'dc off' before 'usb start'
> 
> So what's going on is that the dcache has been enabled now, but the USB
> stack is not safe, so we have to issue 'dcache off' (or 'dc off') before
> starting USB (or in other cases, networking).

Why would it not be safe? Because we don't have the unified cache ops in place 
yet? :-(

M

      reply	other threads:[~2012-01-25 17:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-24 17:02 [U-Boot] non SPL boot on beagleboard-xm Peter Meerwald
2012-01-24 17:46 ` Tom Rini
2012-01-25 10:03   ` Peter Meerwald
2012-01-25 15:20     ` Tom Rini
2012-01-25 15:43       ` Peter Meerwald
2012-01-25 17:22         ` Tom Rini
2012-01-25 17:53           ` Marek Vasut [this message]

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=201201251853.20895.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.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.