From mboxrd@z Thu Jan  1 00:00:00 1970
From: harshadnimje <harshadnimje@tataelxsi.co.in>
Date: Mon, 16 Jun 2008 16:25:09 +0530
Subject: [U-Boot-Users] Hi All
In-Reply-To: <29ab51dc0806160330o20125206jce69589baf6bda07@mail.gmail.com>
Message-ID: <008e01c8cf9f$72420c60$0729320a@telxsi.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi Nobuhiro;

Thanks for your support.

I am not able to see the /board/r2dplus/* in uboot directory stucture.
Can you please send me the link for this board specific source code.

Thanks in Advance

Regards;
Harshad	

-----Original Message-----
From: Nobuhiro Iwamatsu [mailto:iwamatsu at nigauri.org]
Sent: Monday, June 16, 2008 4:00 PM
To: harshadnimje at tataelxsi.co.in
Cc: u-boot-users at lists.sourceforge.net
Subject: Re: [U-Boot-Users] Hi All


Hi,

2008/6/16 harshadnimje <harshadnimje@tataelxsi.co.in>:
>
> For which peripherals I need to write the driver as far as U-boot is
> concerned?

1.Real time clock
 Not Supported
2.Timer Unit
 Supported
3.Bus state controller
 Supported
4.DMA cotroller
 Not Supported
5.Serial communication interface
 Not Suported
6.I/O Ports
 Supported
7.Interrupt controller
 Not Supported
8.PCI conroller.
 Supported. But check on SH7751R only.

> In generic U-Boot1.3.2 directory structure where do I need to make the
> change?
> At what places the config files and make files will have undergo
> changes?
>
You need create your board configration file and Bus state controller
initialization file(lowleve_init.S).

You can take a source code of r2d board into account.
This board has SH7751R cpu too.
board/r2dplus/*

Best reagards,
 Nobuhiro

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments contained in it.

Contact your Administrator for further information.