Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Max Okumoto <okumoto@ucsd.edu>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: Toshiba JMR 3927 working setup?
Date: Fri, 25 Jan 2008 08:50:21 -0800	[thread overview]
Message-ID: <479A134D.7090206@ucsd.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 992 bytes --]

Hi,

I have a JMR3927 based system and I got it to work with the 2.6.23.14 kernel, but
used 0xff0000 instead of 0xff000.  The offset passed in was 0xfffec000 which isn't
within the 0xff000000 - 0xff0ff000.

     Max 

    Subject: [MIPS] Fix plat_ioremap for JMR3927

    TX39XX's "reserved" segment in CKSEG3 area is 0xff000000-0xfffeffff.

    Signed-off-by: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
    ---
    diff --git a/include/asm-mips/mach-jmr3927/ioremap.h
    b/include/asm-mips/mach-jmr3927/ioremap.h
    index aa131ad..ac3be35 100644
    --- a/include/asm-mips/mach-jmr3927/ioremap.h
    +++ b/include/asm-mips/mach-jmr3927/ioremap.h
    @@ -25,7 +25,7 @@ static inline void __iomem *plat_ioremap(phys_t
    offset,
    unsigned long size,
    {
    #define TXX9_DIRECTMAP_BASE 0xff000000ul
    if (offset >= TXX9_DIRECTMAP_BASE &&
    - offset < TXX9_DIRECTMAP_BASE + 0xf0000)
    + offset < TXX9_DIRECTMAP_BASE + 0xff000)
    return (void __iomem *)offset;
    return NULL;
    }


[-- Attachment #2: Type: text/html, Size: 1292 bytes --]

             reply	other threads:[~2008-01-25 16:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-25 16:50 Max Okumoto [this message]
2008-01-26  5:08 ` Toshiba JMR 3927 working setup? Atsushi Nemoto
2008-01-28 16:36   ` Gregor Waltz
2008-01-29 13:50     ` Atsushi Nemoto
2008-03-06 15:49   ` Ralf Baechle
  -- strict thread matches above, loose matches on Subject: below --
2008-01-04 16:45 Gregor Waltz
2008-01-04 17:21 ` Thiemo Seufer
2008-01-04 18:40   ` Gregor Waltz
2008-01-04 18:51     ` Florian Lohoff
2008-01-04 19:23       ` Gregor Waltz
2008-01-04 19:23     ` Thiemo Seufer
2008-01-04 22:27       ` Gregor Waltz
2008-01-05 14:42         ` Atsushi Nemoto
2008-01-07 12:21           ` Ralf Baechle
2008-01-07 15:34             ` Atsushi Nemoto
2008-01-05 15:07     ` Atsushi Nemoto
2008-01-11 17:49       ` Gregor Waltz
2008-01-12 12:17         ` Atsushi Nemoto
2008-01-15 15:50           ` Gregor Waltz
2008-01-15 15:50             ` Gregor Waltz
2008-01-15 16:14             ` Thiemo Seufer
2008-01-15 20:05               ` Gregor Waltz
2008-01-15 23:14                 ` Thiemo Seufer
2008-01-16 15:28                   ` Gregor Waltz
2008-01-16 16:04                     ` Atsushi Nemoto
2008-01-17 16:50                       ` Gregor Waltz
2008-01-18  1:05                         ` Atsushi Nemoto
2008-01-05 14:45 ` Ralf Baechle
2008-01-08 23:54   ` Gregor Waltz
2008-01-09  0:17     ` Thiemo Seufer
2008-02-04  1:14     ` M. Warner Losh

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=479A134D.7090206@ucsd.edu \
    --to=okumoto@ucsd.edu \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=linux-mips@linux-mips.org \
    /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