From: Kumar Gala <galak@kernel.crashing.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2 v3] powerpc/8xxx: Refactor fsl_ddr_get_spd into common code from board
Date: Wed, 9 Feb 2011 23:21:18 -0600 [thread overview]
Message-ID: <F5865443-2DB6-4CDC-8966-1045829F67D7@kernel.crashing.org> (raw)
In-Reply-To: <1296852266-1801-1-git-send-email-galak@kernel.crashing.org>
On Feb 4, 2011, at 2:44 PM, Kumar Gala wrote:
> Move fsl_ddr_get_spd into common mpc8xxx/ddr/main.c as most boards
> pretty much do the same thing. The only variations are in how many
> controllers or DIMMs per controller exist. To make this work we
> standardize on the names of the SPD_EEPROM_ADDRESS defines based on the
> use case of the board.
>
> We allow boards to override get_spd to either do board specific fixups
> to the SPD data or deal with any unique behavior of how the SPD eeproms
> are wired up.
>
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
> ---
> * Changed __get_spd error message from debug -> printf
applied to 85xx next
- k
next prev parent reply other threads:[~2011-02-10 5:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 4:54 [U-Boot] [PATCH 1/2] powerpc/8xxx: Replace fsl_ddr_get_mem_data_rate with get_ddr_freq() Kumar Gala
2011-02-01 4:54 ` [U-Boot] [PATCH 2/2] powerpc/8xxx: Refactor fsl_ddr_get_spd into common code from board Kumar Gala
2011-02-01 5:28 ` [U-Boot] [PATCH 2/2 v2] " Kumar Gala
2011-02-01 10:08 ` Timur Tabi
2011-02-01 14:06 ` Kumar Gala
2011-02-01 16:24 ` [U-Boot] !!! Trouble with u-boot and leon3 !!!! Fabio Giovagnini
2011-02-04 20:44 ` [U-Boot] [PATCH 2/2 v3] powerpc/8xxx: Refactor fsl_ddr_get_spd into common code from board Kumar Gala
2011-02-10 5:21 ` Kumar Gala [this message]
2011-02-10 5:21 ` [U-Boot] [PATCH 1/2] powerpc/8xxx: Replace fsl_ddr_get_mem_data_rate with get_ddr_freq() Kumar Gala
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=F5865443-2DB6-4CDC-8966-1045829F67D7@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--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