[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140831183342.GA25437@ravnborg.org>
Date: Sun, 31 Aug 2014 20:33:42 +0200
From: Sam Ravnborg <sam@...nborg.org>
To: Guenter Roeck <linux@...ck-us.net>
Cc: linux-kernel@...r.kernel.org, linux-cris-kernel@...s.com,
Jesper Nilsson <jesper.nilsson@...s.com>,
Mikael Starvik <starvik@...s.com>,
Grant Likely <grant.likely@...aro.org>,
"Edgar E. Iglesias" <edgar.iglesias@...il.com>
Subject: Re: Status of 'cris' architecture support in Linux kernel
On Sun, Aug 31, 2014 at 10:50:10AM -0700, Guenter Roeck wrote:
> The idea was to create a crisv32 kernel and initramfs to work with qemu
> for the ongoing Linux kernel test project.
>
> After spending a number of days (and nights) on it, the results don't look
> very encouraging.
>
> My overall conclusion is that 'cris' architecture support in the Linux kernel
> is in bad shape, does not work anymore, and would require substantial effort
> to get it into working state.
>
> Anyway, below are my individual findings. If there is an ongoing effort to
> improve cris support in the upstream kernel, specifically support for crisv32,
> please let me know. I'll be happy to test the resulting kernels.
Jesper is on parental leave so do not expect any prompt reply from him.
>
> Individual findings:
>
> headers_install
>
> make ARCH=cris INSTALL_HDR_PATH=/tmp headers_install
>
> results in:
>
> ./scripts/Makefile.headersinst:14: arch/cris/include/uapi/asm/arch-v10/Kbuild:
> No such file or directory
> make[2]: *** No rule to make target `arch/cris/include/uapi/asm/arch-v10/Kbuild'. Stop.
I have already sent a fix for this that Michael said he wanted to deal with.
Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists