From: Sam Ravnborg <sam@ravnborg.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-kernel@vger.kernel.org, linux-cris-kernel@axis.com,
Jesper Nilsson <jesper.nilsson@axis.com>,
Mikael Starvik <starvik@axis.com>,
Grant Likely <grant.likely@linaro.org>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Subject: Re: Status of 'cris' architecture support in Linux kernel
Date: Sun, 31 Aug 2014 20:33:42 +0200 [thread overview]
Message-ID: <20140831183342.GA25437@ravnborg.org> (raw)
In-Reply-To: <20140831175010.GA15408@roeck-us.net>
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
next prev parent reply other threads:[~2014-08-31 18:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-31 17:50 Status of 'cris' architecture support in Linux kernel Guenter Roeck
2014-08-31 18:33 ` Sam Ravnborg [this message]
2014-08-31 18:49 ` Guenter Roeck
2014-09-01 3:49 ` Mikael Starvik
2014-09-15 14:52 ` Jesper Nilsson
2014-09-15 15:49 ` Hans-Peter Nilsson
2014-09-15 18:30 ` Guenter Roeck
2014-09-16 3:22 ` Guenter Roeck
2014-09-15 19:55 ` Guenter Roeck
2014-09-15 22:37 ` Edgar E. Iglesias
2014-09-16 7:23 ` Geert Uytterhoeven
2014-09-16 13:24 ` Guenter Roeck
2014-09-17 19:07 ` Guenter Roeck
2014-09-18 8:52 ` Jesper Nilsson
2014-09-21 16:47 ` Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140831183342.GA25437@ravnborg.org \
--to=sam@ravnborg.org \
--cc=edgar.iglesias@gmail.com \
--cc=grant.likely@linaro.org \
--cc=jesper.nilsson@axis.com \
--cc=linux-cris-kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=starvik@axis.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.