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] Possible Denx m28evk ethernet problem + solution
Date: Sun, 8 Jan 2012 11:51:30 +0100	[thread overview]
Message-ID: <201201081151.30796.marek.vasut@gmail.com> (raw)
In-Reply-To: <67CA36CD-3416-40DC-8602-855AAD3EEB9A@delien.nl>

> > Please use Stefano's imx git tree, which has support for mx28evk already.
> 
> Thanks for the heads-up. It's a bit confusing and unexpected to have a
> mainline spread across different git trees; Will Stefano's mainline be
> integrated into the main-mainline sometime?

Not really ... that's how it all works. When Stefano sends pull RQ, it'll go 
mainline.
> 
> > m28evk and mx28evk differ in the way they driver their Ethernet PHYs.
> 
> Yes, Marek has patiently explained that to me; It's all clear now. But it
> was a good exercise because our product board has a different phy too.
> 
> > Let me know if you have any issues.
> 
> I have a question: The auto-detected SDRAM size is parsed form SPL to
> U-Boot through both scrathch1 and scratch2, probably as a safeguard not to
> assume any value to be a valid one. Did you ever see the error or
> different scratch values occur? I never did. But what I do see occur every
> now and then is a value of 0 in both registers, mostly after obscure reset
> scenarios.

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.

> 
> Can we agree on a different algo to determine the validity of SDRAM size?
> I'm thinking somewhere around the line of a power of 2 between 2MiB and
> 1GiB. Preferable I'd like to use only 1 scratch register for that. The
> other scratch register could then be used to store the boot-mode value
> during SPL stage. The boot mode value is useful for boards capable of
> booting from different MMC devices, like ours.

RFC/patch is always welcome.
> 
> BTW: My version has both MMCs, both Ethernet intefaces and NAND working for
> the evk.

MX28EVK has no NAND if I understand it correctly.

> I have also typed in regs-digctl.h. I can send you or Stefano my
> files, if they're any use to you.

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.
> 
> Cheers,
> 
>          Robert.

M

  reply	other threads:[~2012-01-08 10:51 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 [this message]
2012-01-08 15:16       ` Robert Deliën
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=201201081151.30796.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.