mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: Yoshinori Sato <ysato@users.sourceforge.jp>
Cc: musl@lists.openwall.com, "D. Jeff Dionne" <Jeff@uClinux.org>,
	shumpei.kawasaki@swhwc.com
Subject: Re: Moving forward with sh2/nommu
Date: Tue, 16 Jun 2015 03:02:10 -0400	[thread overview]
Message-ID: <20150616070210.GG1173@brightrain.aerifal.cx> (raw)
In-Reply-To: <871thcgnss.wl-ysato@users.sourceforge.jp>

On Tue, Jun 16, 2015 at 03:38:59PM +0900, Yoshinori Sato wrote:
> > > > Thank you. I'd really like to make progress at least on the matter of
> > > > determining if this is feasible. I now have a new musl/sh2 patch that
> > > > simply uses "trapa #31" unconditionally, and it's a lot
> > > > simpler/cleaner and working on my patched kernel. The big question is
> > > > just whether this is an unacceptable constraint on hardware.
> > > 
> > > SH2A reserved system for vector 31.
> > > But not assigned now.
> > > I think no problem.
> > 
> > Thank you for the feedback. This sounds promising.
> > 
> > We still need whoever ends up being the new kernel maintainer for SH
> > to be okay with adding trap 31 syscall support for sh2 and declaring
> > it supported/stable for sh3/4 too, but at least it looks like there
> > arent technical problems for doing this.
> 
> Yes.
> I think test necessary by SH2A, but there would be no problems.

Do you know anyone who could verify that vector 31 is unused? There's
nothing in the upstream Linux kernel attached to it, but I'm not clear
on whether somebody would have to make a new SH2A chip variant
(unlikely) to use it for hardware purposes, or whether it could come
into use as a result of how an existing SH2A chip is wired up to other
hardware on the board.

Rich


      reply	other threads:[~2015-06-16  7:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-01 15:11 Rich Felker
2015-06-02  6:09 ` Rob Landley
2015-06-02 16:45   ` Rich Felker
2015-06-02 23:49     ` Rich Felker
2015-06-10  3:30 ` Rich Felker
2015-06-11  4:02   ` Rob Landley
2015-06-11 15:12     ` Rich Felker
2015-06-11 17:22       ` Rich Felker
2015-06-12  4:26         ` Yoshinori Sato
2015-06-12  4:35           ` Rich Felker
2015-06-12  4:49             ` uClinux.org
2015-06-12  6:37               ` Rich Felker
2015-06-12  6:46                 ` D. Jeff Dionne
2015-06-12  4:08       ` Yoshinori Sato
2015-06-12  4:28         ` Rich Felker
2015-06-16  6:38           ` Yoshinori Sato
2015-06-16  7:02             ` Rich Felker [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=20150616070210.GG1173@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=Jeff@uClinux.org \
    --cc=musl@lists.openwall.com \
    --cc=shumpei.kawasaki@swhwc.com \
    --cc=ysato@users.sourceforge.jp \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).