Hi Wolfgang
On 07/20/2010 11:47 PM, Wolfgang Denk wrote:
Dear Xiangfu Liu,
In message4C45B400.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