public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Shinya Kuribayashi <skuribay@ruby.dti.ne.jp>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [GIT PULL] MIPS updates
Date: Tue, 25 Mar 2008 22:04:41 +0900	[thread overview]
Message-ID: <47E8F869.3010601@ruby.dti.ne.jp> (raw)

Dear Wolfgang,

please pull MIPS updates. These patches contain various fixes, headers'
update and cleanups. MAKEALL results is good (big-endian only).

The following changes since commit 0d48926c87ec96f974a6ac4034f4a2f2eab3255f:
  Yuri Tikhonov (1):
        lwmon5 SYSMON POST: fix backlight control

are available in the git repository at:

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

Shinya Kuribayashi (13):
      [MIPS] Request for the 'mips_cache_lock()' removal
      [MIPS] asm headers' updates
      [MIPS] cpu/mips/cache.S: Introduce NESTED/LEAF/END macros
      [MIPS] Replace memory clearance code with f_fill64
      [MIPS] Fix I-/D-cache initialization loops
      [MIPS] Implement flush_cache()
      [MIPS] INCA-IP: Move watchdog init code from start.S to lowlevel_init()
      [MIPS] Initialize CP0 Cause before setting up CP0 Status register
      [MIPS] Cleanup CP0 Status initialization
      [MIPS] Introduce _machine_restart
      [MIPS] Fix dcache_status()
      [MIPS] Extend MIPS_MAX_CACHE_SIZE upto 64kB
      [MIPS] Move gth2_config from ARM section to MIPS

 Makefile                     |   10 +-
 board/incaip/incaip.c        |    6 +
 board/incaip/lowlevel_init.S |    6 +
 board/purple/purple.c        |    8 +
 board/tb0229/tb0229.c        |    9 +-
 cpu/mips/cache.S             |  209 +++++++++++++--------
 cpu/mips/cpu.c               |   35 +++-
 cpu/mips/start.S             |   48 +++--
 include/asm-mips/asm.h       |  409 ++++++++++++++++++++++++++++++++++++++++++
 include/asm-mips/byteorder.h |   60 ++++++-
 include/asm-mips/cachectl.h  |   10 +-
 include/asm-mips/cacheops.h  |   78 ++++++--
 include/asm-mips/isadep.h    |    5 +-
 include/asm-mips/processor.h |  249 ++++++--------------------
 include/asm-mips/ptrace.h    |   67 ++++----
 include/asm-mips/reboot.h    |   14 ++
 include/asm-mips/reg.h       |  134 ++++++++++----
 include/asm-mips/regdef.h    |  126 +++++++++----
 include/asm-mips/types.h     |   30 +++-
 19 files changed, 1058 insertions(+), 455 deletions(-)
 create mode 100644 include/asm-mips/asm.h
 create mode 100644 include/asm-mips/reboot.h

             reply	other threads:[~2008-03-25 13:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-25 13:04 Shinya Kuribayashi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-07-29 16:00 [U-Boot-Users] [GIT PULL] MIPS updates Shinya Kuribayashi
2008-07-29 23:24 ` Wolfgang Denk
2008-07-08 14:04 Shinya Kuribayashi
2008-07-09 21:24 ` Wolfgang Denk
2008-06-07  1:19 Shinya Kuribayashi
2008-06-11 20:51 ` Wolfgang Denk
2008-05-22 15:29 Shinya Kuribayashi
2008-05-06  4:34 Shinya Kuribayashi
2008-05-09 20:20 ` Wolfgang Denk
2008-05-02  3:33 Shinya Kuribayashi
2008-05-03 22:10 ` Wolfgang Denk
2008-01-16 23:42 Shinya Kuribayashi
2008-01-23 13:38 ` Wolfgang Denk
2007-11-17 12:15 Shinya Kuribayashi
2007-11-18  0:28 ` Wolfgang Denk
2007-10-21 14:31 Shinya Kuribayashi
2007-11-01 21:54 ` 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=47E8F869.3010601@ruby.dti.ne.jp \
    --to=skuribay@ruby.dti.ne.jp \
    --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