All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert Deliën" <robert@delien.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] Possible Denx m28evk ethernet problem + solution
Date: Sun, 8 Jan 2012 15:16:49 +0000	[thread overview]
Message-ID: <4D2946FA-39DE-4AB8-9F22-DDE8562159A0@delien.nl> (raw)
In-Reply-To: <201201081151.30796.marek.vasut@gmail.com>

> Not really ... that's how it all works. When Stefano sends pull RQ, it'll go 
> mainline.

Aha, so it's not mainline yet after all ;-) But I get it; It's available in Fabio's
repo and will be in Denx mainline soon.

> I see no problems with the board DRAM detection on our board, no. I tested this 
> quite thoroughly.
> 
> I don't see the registers differ either ... ever. I suspect your problem is with 
> your DRAM configuration data -- if your DRAM chip is misconfigured, you'll get 
> such memory problems.

It works beautifully; I have no reason to assume there's anything wrong with it.
When it detects 0 MiB SDRAM, it's been my own fault so far: Obscure reset
scenarios, incremental builds where a clean build was due, etc.

> RFC/patch is always welcome.

Great. I'll see what I can come up with.

> MX28EVK has no NAND if I understand it correctly.

It has one of these beautiful TSOP-48 footprint compatible ZIF sockets on board.
Standard it's empty, but with a Samsung K9G08UOM in it, it worked out-of-the-box
using your m28evk configuration.
However mx28evk NAND is mutually exclusive with the use of MMC1 socket
because of shared pins. So in my config, CMD_NAND is used to configure in
NAND and to configure out MMC1.

> Make a patch and submit to the mailing list, like everyone else does please. 
> Don't try to reinvent wheel ... square one this time even.

It's hardly worth a patch; Perhaps Fabio already typed his own. But I'll submit
one tomorrow anyway.

Robert.

  reply	other threads:[~2012-01-08 15:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-06 17:54 [U-Boot] Possible Denx m28evk ethernet problem + solution Robert Deliën
2012-01-06 19:05 ` Marek Vasut
2012-01-06 20:05   ` Robert Deliën
2012-01-06 20:51     ` Marek Vasut
2012-01-06 22:17       ` Robert Deliën
     [not found]       ` <6F6D3536-378A-4DA4-8C7E-7C6D74CC7895@delien.nl>
2012-01-06 23:22         ` Marek Vasut
2012-01-07 22:04 ` Fabio Estevam
2012-01-08 10:39   ` Robert Deliën
2012-01-08 10:51     ` Marek Vasut
2012-01-08 15:16       ` Robert Deliën [this message]
2012-01-08 16:05         ` Marek Vasut

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=4D2946FA-39DE-4AB8-9F22-DDE8562159A0@delien.nl \
    --to=robert@delien.nl \
    --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.