public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] add addrespace definition for sh2a.
Date: Mon, 04 Aug 2008 05:37:33 +0000	[thread overview]
Message-ID: <20080804053733.GA11682@linux-sh.org> (raw)
In-Reply-To: <48969386.4050705@renesas.com>

On Mon, Aug 04, 2008 at 02:28:38PM +0900, Takashi Yoshii wrote:
> Newfile: arch/sh/include/cpu-sh2a/cpu/addrspace.h
> 
> This file seems had be removed to use fallback (cpu-common/cpu/addrspace.h),
> but, I'd like to add sh2a specific file here, because
> 1. the values defined there are not suitable for sh2a.
> 2. I don't think there is "common" definition for these values.
> 
> Values are chosen by consideration of followings...
> P1 is 0. perhaps no question.
> P2 is from hardware manual, which says no-cache area starts at 20000000.
> It means that P? space size 000000.
> P3 is P2+size since asm/ptrace.h uses P3 as a end of P2. 
> P4 is P3+size since asm/fixup.h uses P4 as a end of P3.
> 
> Signed-off-by: Takashi YOSHII <yoshii.takashi@renesas.com>

This is a good indicator for why we should just kill off all of the
references in-tree that we can find, it's been a terrible abstraction
from the beginning. It would have been nice if more than a single family
of CPUs could have been consistent with its segmentation.

For SH-2A these look fine, so I'll check this in as it is, but I would
much rather see patches that get rid of more of these references, rather
than adding more ;-)

      reply	other threads:[~2008-08-04  5:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-04  5:28 [PATCH] add addrespace definition for sh2a Takashi Yoshii
2008-08-04  5:37 ` Paul Mundt [this message]

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=20080804053733.GA11682@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=linux-sh@vger.kernel.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