public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Xiangfu Liu <xiangfu@openmobilefree.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] question about add new board to MAKEALL
Date: Wed, 21 Jul 2010 08:47:05 +0800	[thread overview]
Message-ID: <4C464389.6070207@openmobilefree.net> (raw)
In-Reply-To: <20100720154749.886C3153780@gemini.denx.de>

Hi Wolfgang

On 07/20/2010 11:47 PM, Wolfgang Denk wrote:
> Dear Xiangfu Liu,
>
> In message<4C45B400.2000509@openmobilefree.net>  you wrote:
>>
>> I modify the patch to a new one[1], since this board use a new cpu
>> named "xburst".
>> this new patch works fine when I run "./MAKEALL mips_el" :)
>
> Well, we don't want to add lists for each and every CPU, especially
> not for MIPS where we have only very few systems supported; which

ok. understand.

> family does xburst best fit in?
>

in there website[1], they don't mention MIPS at all, but I found this
in their head file:
	"MIPS 4Kc (32 bit RISC)"
and the gcc argument is
	"-march=4kc -mtune=4kc -EL -mabicalls -mips32"

here[2] is the new files for the jz4740 soc. give me some advice on this.
thanks.

(some linke for our board:
http://sharism.cc/products/ben-nanonote/
http://en.qi-hardware.com/wiki/Ben_NanoNote
   in this wiki you can find all the document of our boards.
   include hardware design files.
)

[1]
http://www.ingenic.cn/eng/productServ/AppPro/JZ4740/pfCustomPage.aspx
ftp://ftp.ingenic.cn/2soc/Jz4740_ds.pdf

[2]
.
??? arch
?   ??? mips
?       ??? cpu
?       ?   ??? xburst
?       ?       ??? cache.S
?       ?       ??? config.mk
?       ?       ??? cpu.c
?       ?       ??? interrupts.c
?       ?       ??? jz4740.c
?       ?       ??? jz_mmc.c
?       ?       ??? jz_mmc.h
?       ?       ??? jz_serial.c
?       ?       ??? Makefile
?       ?       ??? nanonote_gpm940b0.c
?       ?       ??? nanonote_gpm940b0.h
?       ?       ??? start.S
?       ?       ??? start_spl.S
?       ?       ??? usbboot.S
?       ??? include
?           ??? asm
?               ??? jz4740.h
??? board
?   ??? xburst
?       ??? nanonote
?           ??? config.mk
?           ??? config.tmp
?           ??? Makefile
?           ??? nanonote.c
?           ??? u-boot.lds
?           ??? u-boot-nand.lds
??? drivers
?   ??? mtd
?       ??? nand
?           ??? jz4740_nand.c
??? include
?   ??? configs
?       ??? nanonote.h
?       ??? qi_lb60.h
??? nand_spl
     ??? board
     ?   ??? xburst
     ?       ??? nanonote
     ?           ??? config.mk
     ?           ??? Makefile
     ?           ??? u-boot.lds
     ??? nand_boot_jz4740.c


> Best regards,
>
> Wolfgang Denk
>


-- 
Best Regards
Xiangfu Liu
http://www.openmobilefree.net

  reply	other threads:[~2010-07-21  0:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-28  2:41 [U-Boot] question about add new board to MAKEALL "Xiangfu Liu(刘向富)"
2010-06-28  7:43 ` Wolfgang Denk
2010-07-19  3:42   ` "Xiangfu Liu(刘向富)"
2010-07-19 17:45     ` Wolfgang Denk
2010-07-20  2:30       ` "Xiangfu Liu(刘向富)"
2010-07-20  8:02       ` Xiangfu Liu
2010-07-20  9:51         ` Wolfgang Denk
2010-07-20 14:34           ` Xiangfu Liu
2010-07-20 15:47             ` Wolfgang Denk
2010-07-21  0:47               ` Xiangfu Liu [this message]
2010-07-21  8:28                 ` Wolfgang Denk

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=4C464389.6070207@openmobilefree.net \
    --to=xiangfu@openmobilefree.net \
    --cc=u-boot@lists.denx.de \
    /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