On Sat, Mar 6, 2021, at 4:03 PM, Thomas Bogendoerfer wrote:
> On Thu, Mar 04, 2021 at 07:00:57PM +0800, Qing Zhang wrote:
> > The purpose of separating loongson_system_configuration from boot_param.h
> > is to keep the other structure consistent with the firmware.
> >
> > Signed-off-by: Jiaxun Yang <jiaxun.y...@flygoat.com>
> > Signed-off-by: Qing Zhang <zhangq...@loongson.cn>
> > ---
> > .../include/asm/mach-loongson64/boot_param.h | 18 ------------------
> > .../include/asm/mach-loongson64/loongson.h | 18 ++++++++++++++++++
>
> as you are already touching mach-loongson64 files...
>
> Is there a chance you clean up that up even further ? My goal is to
> have only files in mach-<platform> files, which have an mach-generic
> counterpart. Everything else should go to its own directory. So in
> case of loongson something
>
> like
>
> arch/mips/include/asm/loongson for common stuff
> arch/mips/include/asm/loongson/32
> arch/mips/include/asm/loongson/64
Hi Thomas
I'm object to this idea as loongson32/2ef/64 have nothing in common.
They're different cores and different SoC designed by different team with
different booting protocol.
Maybe it's possible to merge loongson32 into generic platform but my LS1C borad
is broken...
Thanks.
- Jiaxun
>
> Comments ?
>
> Thomas.
>
> --
> Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
> good idea. [ RFC1925, 2.3 ]
>
--
- Jiaxun
