From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/7946 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Moving forward with sh2/nommu Date: Tue, 16 Jun 2015 03:02:10 -0400 Message-ID: <20150616070210.GG1173@brightrain.aerifal.cx> References: <20150601151107.GA20759@brightrain.aerifal.cx> <20150610033050.GS17573@brightrain.aerifal.cx> <5579085B.5090407@landley.net> <20150611151252.GW17573@brightrain.aerifal.cx> <87oakl602i.wl-ysato@users.sourceforge.jp> <20150612042821.GB17573@brightrain.aerifal.cx> <871thcgnss.wl-ysato@users.sourceforge.jp> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1434438156 4519 80.91.229.3 (16 Jun 2015 07:02:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 16 Jun 2015 07:02:36 +0000 (UTC) Cc: musl@lists.openwall.com, "D. Jeff Dionne" , shumpei.kawasaki@swhwc.com To: Yoshinori Sato Original-X-From: musl-return-7959-gllmg-musl=m.gmane.org@lists.openwall.com Tue Jun 16 09:02:36 2015 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1Z4ktG-0006H9-6k for gllmg-musl@m.gmane.org; Tue, 16 Jun 2015 09:02:34 +0200 Original-Received: (qmail 23920 invoked by uid 550); 16 Jun 2015 07:02:31 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 23887 invoked from network); 16 Jun 2015 07:02:30 -0000 Content-Disposition: inline In-Reply-To: <871thcgnss.wl-ysato@users.sourceforge.jp> User-Agent: Mutt/1.5.21 (2010-09-15) Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:7946 Archived-At: 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