public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
To: linux-sh@vger.kernel.org
Subject: Re: Linux 2.6.22.11 on T-Engine/SH7727 (MS7727CP02) Development Kit
Date: Mon, 15 Sep 2008 09:27:18 +0000	[thread overview]
Message-ID: <20080915182718.e6445d99.iwamatsu@nigauri.org> (raw)
In-Reply-To: <loom.20080915T032055-333@post.gmane.org>

Hi ,

On Mon, 15 Sep 2008 03:48:21 +0000 (UTC)
Cuong Dang Phu <cuongdp@Cybersoft-VN.com> wrote:

> Hi,
> 
> We are working for an embedded software company, for R&D purpose, we are 
> porting Linux on T-Engine/SH7727 (MS7727CP02) Development Kit. The first step 
> we do is: define physical memory and peripherals (in this file: \include\asm-
> sh\se7727.h), but we have some difficult:
> 	a. We can’t understand many symbols: I show you a list I get form Linux 
> kernel 2.6.22.11 for se7720:
>  
> #define PA_PCIC         PA_PERIPHERAL   		/* MR-SHPC-01 PCMCIA */
> #define PA_MRSHPC       (PA_PERIPHERAL + 0x003fffe0)    /* MR-SHPC-01 PCMCIA 
> controller */
> #define PA_MRSHPC_MW1   (PA_PERIPHERAL + 0x00400000)    /* MR-SHPC-01 memory 
> window base */
> #define PA_MRSHPC_MW2   (PA_PERIPHERAL + 0x00500000)    /* MR-SHPC-01 attribute 
> window base */
> #define PA_MRSHPC_IO    (PA_PERIPHERAL + 0x00600000)    /* MR-SHPC-01 I/O 
> window base */
> #define MRSHPC_OPTION   (PA_MRSHPC + 6)
> #define MRSHPC_CSR      (PA_MRSHPC + 8)
> #define MRSHPC_ISR      (PA_MRSHPC + 10)
> #define MRSHPC_ICR      (PA_MRSHPC + 12)
> #define MRSHPC_CPWCR    (PA_MRSHPC + 14)
> #define MRSHPC_MW0CR1   (PA_MRSHPC + 16)
> #define MRSHPC_MW1CR1   (PA_MRSHPC + 18)
> #define MRSHPC_IOWCR1   (PA_MRSHPC + 20)
> #define MRSHPC_MW0CR2   (PA_MRSHPC + 22)
> #define MRSHPC_MW1CR2   (PA_MRSHPC + 24)
> #define MRSHPC_IOWCR2   (PA_MRSHPC + 26)
> #define MRSHPC_CDCR     (PA_MRSHPC + 28)
> #define MRSHPC_PCIC_INFO (PA_MRSHPC + 30)

There symbols are for PCMCIA controller .
SE7727 has Marubun PCMCIA controller(MR-SHPC-01).
> 
> #define PA_FPGA		0xB7000000 	/* FPGA base address */
> 
> #define MRSHPC_IRQ0    	14
> 
> #define FPGA_ILSR1	(PA_FPGA + 0x02)
> #define FPGA_ILSR2	(PA_FPGA + 0x03)
> #define FPGA_ILSR3	(PA_FPGA + 0x04)
> #define FPGA_ILSR4	(PA_FPGA + 0x05)
> #define FPGA_ILSR5	(PA_FPGA + 0x06)
> #define FPGA_ILSR6	(PA_FPGA + 0x07)
> #define FPGA_ILSR7	(PA_FPGA + 0x08)
> #define FPGA_ILSR8	(PA_FPGA + 0x09)
>  
> 	b. We don’t know how to define these sysbols.
SE7727 has Interrput controller on FPGA.
These symbols are written in the manual. 

I think that You may not worry about these, maybe.

Best regards,
 Nobuhiro
-- 
Nobuhiro Iwamatsu

  reply	other threads:[~2008-09-15  9:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-15  3:48 Linux 2.6.22.11 on T-Engine/SH7727 (MS7727CP02) Development Kit - Mapping physical memory address Cuong Dang Phu
2008-09-15  9:27 ` Nobuhiro Iwamatsu [this message]
2008-09-15 10:43 ` Linux 2.6.22.11 on T-Engine/SH7727 (MS7727CP02) Development Kit - Mapping physical memory addres Cuong Dang Phu
2008-09-15 10:51 ` Linux 2.6.22.11 on T-Engine/SH7727 (MS7727CP02) Development Kit Nobuhiro Iwamatsu
2008-09-16  9:53 ` Linux 2.6.22.11 on T-Engine/SH7727 (MS7727CP02) Development Kit - Mapping physical memory addres Cuong Dang Phu
2008-09-18  1:23 ` Nobuhiro Iwamatsu
2008-09-18  6:41 ` Cuong Dang Phu

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=20080915182718.e6445d99.iwamatsu@nigauri.org \
    --to=iwamatsu@nigauri.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