From: Cuong Dang Phu <cuongdp@Cybersoft-VN.com>
To: linux-sh@vger.kernel.org
Subject: Re: Linux 2.6.22.11 on T-Engine/SH7727 (MS7727CP02) Development Kit - Mapping physical memory addres
Date: Thu, 18 Sep 2008 06:41:18 +0000 [thread overview]
Message-ID: <loom.20080918T062854-451@post.gmane.org> (raw)
In-Reply-To: <loom.20080915T032055-333@post.gmane.org>
Hi Nobuhiro
> The macro that you mind is a thing of Solution Engine 7720.
> And the board which you develop is SH7727 T-Engine Board.
> These are totally different boards. I think that I do not serve as a
> reference very much.
>
> If you want to know the macrocontents which you point out by the first email ,
> you need get a manual of *Solution Engine 7720*.
>
> This point doesn't write in SH7727 T-Engine Board and SH7727 CPU of manual.
>
You are right, the board which I develop is SH7727 T-Engine Board and we use
Solution Engine 7720 as an example. I understood you idea, and now, I think I
can understand things which I wrote in the first email.
Thank you very much
Cuong Dang
prev parent reply other threads:[~2008-09-18 6:41 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 ` Linux 2.6.22.11 on T-Engine/SH7727 (MS7727CP02) Development Kit Nobuhiro Iwamatsu
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 [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=loom.20080918T062854-451@post.gmane.org \
--to=cuongdp@cybersoft-vn.com \
--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