linux-kernel - Re: Status of 'cris' architecture support in Linux kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <54036E45.2050604@roeck-us.net>
Date:	Sun, 31 Aug 2014 11:49:41 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Sam Ravnborg <sam@...nborg.org>
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 08/31/2014 11:33 AM, Sam Ravnborg wrote:
> 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.
>

Hi Sam,

That is great. Note there is a second part besides the failure itself:
The resulting installed headers don't work and need a post-installation
patch, as mentioned in my previous e-mail. Would be great if you can
look into this as well (if you did not do so already).

Thanks,
Guenter

--
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/