All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ppc4xx] Please pull git://www.denx.de/git/u-boot-ppc4xx.git
Date: Thu, 12 Feb 2009 06:46:03 +0100	[thread overview]
Message-ID: <200902120646.03667.sr@denx.de> (raw)

The following changes since commit f15c6515fc23f83c51f3de272ca23d86b80e81b1:
  Wolfgang Denk (1):
        Coding style cleanup; update CHANGELOG

are available in the git repository at:

  git://www.denx.de/git/u-boot-ppc4xx.git master

Adam Graham (1):
      ppc4xx: Autocalibration can set RDCC to over aggressive value.

Carolyn Smith (1):
      ppc4xx: Fix initialization of the SDRAM_CODT register

Dirk Eibach (1):
      ppc4xx: Add README entry for CONFIG_PCI_DISABLE_PCIE

Stefan Roese (2):
      ppc4xx: Fix problem with CONFIG_MAX_MEM_MAPPED in include/asm-ppc/config.h
      ppc4xx: Fix problem with board_eth_init() vs cpu_eth_init() on AMCC boards

 README                              |    4 ++
 board/amcc/katmai/katmai.c          |    1 +
 board/amcc/taihu/taihu.c            |    1 +
 board/amcc/taishan/taishan.c        |    1 +
 board/amcc/yucca/yucca.c            |    1 +
 cpu/ppc4xx/44x_spd_ddr2.c           |    7 +--
 cpu/ppc4xx/4xx_ibm_ddr2_autocalib.c |   74 +++++++++++++++++++++--------------
 include/asm-ppc/config.h            |    4 +-
 include/asm-ppc/ppc4xx-sdram.h      |    2 +
 include/configs/katmai.h            |    1 -
 include/configs/kilauea.h           |    7 ---
 11 files changed, 59 insertions(+), 44 deletions(-)

             reply	other threads:[~2009-02-12  5:46 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-12  5:46 Stefan Roese [this message]
2009-02-12  7:39 ` [U-Boot] [ppc4xx] Please pull git://www.denx.de/git/u-boot-ppc4xx.git Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2009-02-18 15:01 Stefan Roese
2009-02-18 23:52 ` Wolfgang Denk
2009-02-06 10:19 Stefan Roese
2009-02-07 21:40 ` Wolfgang Denk
2009-01-29 10:11 Stefan Roese
2009-02-01 20:21 ` Wolfgang Denk
2009-01-26  9:47 Stefan Roese
2009-01-27 19:54 ` Wolfgang Denk
2009-01-14 10:39 Stefan Roese
2009-01-16  8:22 ` Wolfgang Denk
2008-12-10 16:23 Stefan Roese
2008-12-12 23:37 ` Wolfgang Denk
2008-11-25  8:18 Stefan Roese
2008-11-25 10:59 ` Wolfgang Denk
2008-11-21 10:54 Stefan Roese
2008-10-31  9:51 Stefan Roese
2008-11-01 15:10 ` Wolfgang Denk
2008-10-24 15:36 Stefan Roese
2008-10-27 21:31 ` Wolfgang Denk
2008-10-21 15:40 Stefan Roese
2008-10-21 19:20 ` Wolfgang Denk
2008-10-13  9:18 Stefan Roese
2008-10-13 10:35 ` Wolfgang Denk
2008-09-16 18:19 Stefan Roese
2008-09-16 20:36 ` Wolfgang Denk
2008-09-17  4:00   ` Stefan Roese
2008-09-21 20:48     ` Wolfgang Denk
2008-09-22  9:09       ` Stefan Roese
2008-09-12  5:22 Stefan Roese
2008-09-12 13:24 ` Wolfgang Denk
2008-09-08 13:23 Stefan Roese
2008-09-09  0:22 ` Wolfgang Denk
2008-09-09  7:34 ` Wolfgang Denk
2008-09-03 15:24 Stefan Roese
2008-09-03 20:59 ` Wolfgang Denk
2008-08-30  9:28 Stefan Roese
2008-08-31 22:05 ` Wolfgang Denk
2008-08-22 19:42 Stefan Roese
2008-08-22 22:16 ` Wolfgang Denk
2008-08-22  4:51 Stefan Roese
2008-08-22 22:15 ` Wolfgang Denk
2008-08-13  4:49 Stefan Roese
2008-08-13 21:01 ` Wolfgang Denk
2008-08-11  4:49 Stefan Roese
2008-08-11  6:46 ` Wolfgang Denk

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=200902120646.03667.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 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.