From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 10096] SH4 toolchain does not build Linux kernel magicpanelr2_defconfig
Date: Wed, 24 Jan 2024 03:25:59 +0000 [thread overview]
Message-ID: <bug-10096-163-0AcdzjPHq0@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10096-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10096
Kieran Weaver <drawbook.productions@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|NEW |RESOLVED
Assignee|unassigned@buildroot.uclibc |drawbook.productions@gmail.
|.org |com
--- Comment #2 from Kieran Weaver <drawbook.productions@gmail.com> ---
Reproduced on the current buildroot git head.
From linux commit ded5431ff311d963888ac951131a04fe7633aa79:
"""
From ded5431ff311d963888ac951131a04fe7633aa79 Mon Sep 17 00:00:00 2001
From: Markus Brunner <super.firetwister@gmail.com>
Date: Wed, 12 Sep 2007 11:54:58 +0900
Subject: sh: Magic Panel R2 board support.
This adds support for the SH7720 (SH3-DSP) based Magic Panel R2
board.
"""
The Magic Panel R2 is a SH3 board, not a SH4 board, it's not supported by
buildroot.
The root cause is that the SH3-DSP scheduler code saves and loads the SH3 DSP
registers via inline ASM, and mixing SH3-DSP code with SH4-FPU code isn't
supported.
Marking as RESOLVED/WONTFIX
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-01-24 3:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 15:08 [Buildroot] [Bug 10096] New: SH4 toolchain does not build Linux kernel magicpanelr2_defconfig bugzilla at busybox.net
2018-04-01 11:56 ` [Buildroot] [Bug 10096] " bugzilla at busybox.net
2024-01-24 3:25 ` bugzilla [this message]
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=bug-10096-163-0AcdzjPHq0@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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.