Re: [PATCH 02/56] microblaze_v2: Makefiles for Microblaze cpu

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> --- /dev/null
> +++ b/arch/microblaze/Makefile
> @@ -0,0 +1,63 @@
> +UTS_SYSNAME = -DUTS_SYSNAME=\"uClinux\"
> +
> +# What CPU vesion are we building for, and crack it open
> +# as major.minor.rev
> +CPU_VER=$(subst ",,$(CONFIG_XILINX_MICROBLAZE0_HW_VER) )
> +CPU_MAJOR=$(shell echo $(CPU_VER) | cut -d '.' -f 1)
> +CPU_MINOR=$(shell echo $(CPU_VER) | cut -d '.' -f 2)
> +CPU_REV=$(shell echo $(CPU_VER) | cut -d '.' -f 3)

No doubt there's some cleaner shell-fu to do this but I'm not
complaining as I'm responsible for the original yucky version!

> --- /dev/null
> +++ b/arch/microblaze/platform/Makefile
> @@ -0,0 +1,3 @@
> +#
> +# Makefile for arch/microblaze/platform directory
> +#

How about a single 

obj-$(CONFIG_PLATFORM_GENERIC) += generic/

to show how platform-specific setup code can be added (even though
there's none in the default generic target)?


--
To unsubscribe from this list: send the line "unsubscribe linux-arch" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [Kernel Newbies]     [x86 Platform Driver]     [Netdev]     [Linux Wireless]     [Netfilter]     [Bugtraq]     [Linux Filesystems]     [Yosemite Discussion]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]

  Powered by Linux