lkml.org 
[lkml]   [2018]   [Dec]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH 0/7] microblaze: fix various problems in building boot images
From
Date
On 03. 12. 18 8:50, Masahiro Yamada wrote:
> This patch set fixes various issues in microblaze Makefiles.
>
> BTW, "simpleImage.<dt>" works like a phony target to generate the
> following four images, where the first three are just aliases.
>
> - arch/microblaze/boot/simpleImage.<dt>:
> identical to arch/microblaze/boot/linux.bin
>
> - arch/microblaze/boot/simpleImage.<dt>.unstrip:
> identical to vmlinux
>
> - arch/microblaze/boot/simpleImage.<dt>.ub:
> identical to arch/microblaze/boot/linux.bin.ub
>
> - arch/microblaze/boot/simpleImage.<dt>.strip:
> stripped vmlinux
>
> I am not sure how much useful those copies are,
> but, I tried my best to keep the same behavior.
>
> IMHO, I guess DTB=<dt> would be more sensible,
> but it is up to Michal.
>
>
>
> Masahiro Yamada (7):
> microblaze: fix cleaning of boot images
> microblaze: adjust the help to the real behavior
> microblaze: move "... is ready" message to arch/microblaze/Makefile
> microblaze: fix multiple bugs in arch/microblaze/boot/Makefile
> microblaze: add linux.bin* and simpleImage.* to PHONY
> microblaze: fix race condition in building boot images
> microblaze: remove the unneeded code just in case file copy fails
>
> arch/microblaze/Makefile | 14 +++++++++-----
> arch/microblaze/boot/Makefile | 33 +++++++++++++++++----------------
> arch/microblaze/boot/dts/Makefile | 5 +----
> 3 files changed, 27 insertions(+), 25 deletions(-)
>

One more thing I have in my mind for a while is that will be good to
configure kernel build flags from DT and completely get rid of these
symbols.

XILINX_MICROBLAZE0_USE_MSR_INSTR
XILINX_MICROBLAZE0_USE_PCMP_INSTR
XILINX_MICROBLAZE0_USE_BARREL
XILINX_MICROBLAZE0_USE_DIV
XILINX_MICROBLAZE0_USE_HW_MUL
XILINX_MICROBLAZE0_USE_FPU

It means setup CPUFLAGS based on extracting that values from DT that it
all the time match the hardware.
It will also simplify all the CPUFLAGS logic which is in
arch/microblaze/Makefile.

Do you have any idea how this can be done?

(I have the same issue in U-Boot too)

Thanks,
Michal

--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal SoCs


[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2018-12-06 15:54    [W:0.126 / U:5.060 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site