-----Original Message----- From: u-boot-users-bounces@lists.sourceforge.net [mailto:u-boot-users-bounces@lists.sourceforge.net] On Behalf Of Vishal Oliyil Kunnil Sent: 03 March 2008 09:18 To: U-Boot-Users@lists.sourceforge.net Cc: wd@denx.de Subject: [U-Boot-Users] Cortex-M1 support
Hi all,
i have ported u-boot on Cortex-M1 series - It does not use the conventional arm routines in lib_arm (as Cortex M1 need these in Thumb-2). What is the correct method of integrating it in to u-boot ? For now I have a new directory named lib_armv6-m. Is it better to use place the lib files in existing arm folder ?
Best regards, Vishal Oliyil Kunnil
Vishal Currently I'm envisaging
./lib_arm Existing armv4,v5 assembly code ./lib_armv6 New v6 arm assembly code ./lib_armv6m New v6 thumb assembly code ./lib_armv7 New v7 arm assembly code ./lib_armv7m New v7m thumb assembly code ./cpu/armxxx Existing arm v4,v5 cpus ./cpu/armv6 New v6 arm cpus ./cpu/armv6m New v6 thumb cpus ./cpu/armv7 New v7 arm cpus ./cpu/armv7m New v7 thumb cpus ./include/asm-arm/arch-v6 v6 socs ./include/asm-arm/arch-v6m v6 thumb socs ./include/asm-arm/arch-v7 v7 socs ./include/asm-arm/arch-v7m v7 thumb socs
However it may be possible to reduce this depending on toolchains, use of unified assembler code, ifdefs etc
I suggest you submit a patch with any v6m dependent code split out as above.
Please try to keep as much code as possible in existing locations, rather than making identical copies.
I assume you are using the Code Sourcery toolchain....
Regards
Peter