public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Does U-boot supports Spansion S29GL512P NOR Flash?
Date: Mon, 12 Apr 2010 09:59:46 +0200	[thread overview]
Message-ID: <201004120959.47043.sr@denx.de> (raw)
In-Reply-To: <j2gb9c1f3ac1004112118z7157edaaj4a05e2910aab4023@mail.gmail.com>

On Monday 12 April 2010 06:18:12 prakash bedge wrote:
> >> Right. Most likely you just need to tune the chip select timing
> >> registers
> 
> And of course the size of the CS.
> What mean by size of CS? Which file I should check for timing register for
> S29GL512P?

IIRC, then you have a custom PPC440 SoC. I have no idea which external bus 
controller (EBC) is used on your SoC. Is it the one also used on the 
AppliedMicro (AMCC) PPC4xx? Then you need to change the CONFIG_SYS_EBC_PBxCR / 
CONFIG_SYS_EBC_PBxAP defines. Take a look at the users manual for details. If 
you have a different EBC then I can't really help you here. Your SoC 
documentation should have all details you need.
 
> >> BTW: You might also need to configure a bigger TLB entry for the FLASH
> 
> now that you use a bigger FLASH chip.
> Does uboot support one single TLB entry for 64MB size. At pesent I have
> configured 4 TLB entries, each 16MB.

Looking into the PPC440 users manual makes it clear. 64MByte as TLB size is 
not available. You need to define 4 16MB entries for this.

Cheers,
Stefan

--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de

  reply	other threads:[~2010-04-12  7:59 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09  5:26 [U-Boot] Does U-boot supports Spansion S29GL512P NOR Flash? prakash bedge
2010-04-09  6:10 ` Stefan Roese
2010-04-09  7:22   ` prakash bedge
2010-04-09  7:35     ` Stefan Roese
2010-04-09  7:55       ` Frank Svendsbøe
2010-04-09  8:05       ` prakash bedge
2010-04-09  8:09         ` Stefan Roese
2010-04-09  9:10           ` Frank Svendsbøe
2010-04-09 12:11             ` prakash bedge
2010-04-09 13:27               ` Frank Svendsbøe
2010-04-12  4:13                 ` prakash bedge
2010-04-12 17:01                   ` Frank Svendsbøe
2010-04-12 17:15                   ` Frank Svendsbøe
2010-04-13  6:31                     ` prakash bedge
2010-04-13  8:34                       ` Stefan Roese
2010-04-13 11:46                         ` prakash bedge
2010-04-13 12:16                           ` Stefan Roese
2010-04-14  5:03                             ` prakash bedge
2010-04-14  7:38                               ` Frank Svendsbøe
2010-04-14 12:05                               ` Stefan Roese
2010-04-16 14:38                                 ` prakash bedge
2010-04-20  9:25                                   ` prakash bedge
2010-04-09 13:35               ` Stefan Roese
2010-04-12  4:18                 ` prakash bedge
2010-04-12  7:59                   ` Stefan Roese [this message]
2012-03-10 10:47   ` Balaji Sivakumar
2012-03-10 18:29     ` Dirk Behme
2012-03-10 19:10     ` Wolfgang Denk
2010-04-09  7:48 ` Frank Svendsbøe
2010-04-09  8:07   ` prakash bedge
2010-04-09  8:23     ` Frank Svendsbøe

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=201004120959.47043.sr@denx.de \
    --to=sr@denx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox