Date: Tue, 2 Mar 2010 10:23:58 +0530 From: "C. Jayachandran" <c.jayachandran@gmail.com> To: "M. Warner Losh" <imp@bsdimp.com> Cc: freebsd-mips@freebsd.org Subject: Re: USB support for RMI processors Message-ID: <98a59be81003012053w81c3b4cxf25d1157abfe3114@mail.gmail.com> In-Reply-To: <20100301.163233.4959786962507439.imp@bsdimp.com> References: <98a59be81002230021j6a0cc408j99fe6a5d57a21aff@mail.gmail.com> <98a59be81003010632n526acfd0i57c58bca8645d62@mail.gmail.com> <5B27996C-CAAC-4C87-BF9A-D914B57E175F@lakerest.net> <20100301.163233.4959786962507439.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 2, 2010 at 5:02 AM, M. Warner Losh <imp@bsdimp.com> wrote: > In message: <5B27996C-CAAC-4C87-BF9A-D914B57E175F@lakerest.net> > =A0 =A0 =A0 =A0 =A0 =A0Randall Stewart <rrs@lakerest.net> writes: > : Hmm I might have missed these.. I got some in. Thanks. > : The n32 ones I will leave for Warner to look at.. > : > : I personally think we should be working on n64 not n32.. But > : I will go with whatever our fearless leader says (the passer > : of the cold).. > > n64 for the kernel definitely is the way to go. =A0However, I'd like to > get the n32 and n64 userland support in place too. =A0And the first > place to start with that is tools... Please see my reply on the list on n32. The userland compiles with the patches and with -DNO_USB -DNO_BLUETOOTH (using ld to convert binary to n32 obj fails - needs to look at this). But the main battle will be ahead, the syscall, exception and pobably signal handling and executable support needs to be fixed before init goes thru. I'm working on this. Regards, JC.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?98a59be81003012053w81c3b4cxf25d1157abfe3114>