Date: Thu, 26 Jun 2014 08:06:12 +0200 From: Ernest Staszuk <erneststaszuk@gmail.com> To: soc-status@freebsd.org, Grzegorz Bernacki <gjb@semihalf.com>, =?UTF-8?Q?Rafa=C5=82_Jaworowski?= <raj@semihalf.com> Subject: Re: Status of work report Message-ID: <CANFE%2BdxusWQ%2BMh4FTHF=9jwrE7n2Fh605CtmOMJ_%2BXYVPP8AnA@mail.gmail.com> In-Reply-To: <CANFE%2BdxK9-qGPU2nFfA_DAQtrM%2BdP2qbOVpMbswgrTr7gKHDTg@mail.gmail.com> References: <CANFE%2BdxK9-qGPU2nFfA_DAQtrM%2BdP2qbOVpMbswgrTr7gKHDTg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, There is actual progress of my project: - Ive done microblaze directory tree with all things (mainly headers and c/asm sources) necessary to compile basic kernel. - Made some minor changes in arch independent code to glue everything together (most of them will be reverted, a few may be needed indeed). Many changes there touch some irrelevant mechanisms. - Ive compiled kernel with microblaze target. To full build ldscript needs to be fitted. Linking objects passes. Fitting pieces together into kernel file not yet. What I am doing now: - instructions how code can be built for now - ldscript adjustments - first attempts in bootstrap field and memory initialization - of course midterm evaluation During next week I would like make: - plam of memory map - booting (not final version yet. Something which could load and run code in any way on target) - locore.S I am concern about way to include toolchain. I can either add it to ports tree or contrib in source tree. But there are parts with not BSD-compliant license (GPLv3). Temporally I prepared a script which builds a microblaze toolchain. Regards, Ernest Staszuk 2014-06-18 16:06 GMT+02:00 Ernest Staszuk <erneststaszuk@gmail.com>: > Hi, > > I aim for compilable kernel for midterm prepared for microblaze. > > - I figured out two possible toolchains (with gcc 4.6.2 or gcc 4.9.0) > . Have gcc 4.6.2 prepared for microblaze target, but now I test 4.9.0 > . > - Common kernel code compiles with 4.9.0 after minor tunes > (WITHOUT_CRYPT option and possibly small workaround inside stdlib.h). > - I made skeleton of microblaze arch. > > Now I put emphasis on filling up platform specific code and making > configuration for proper system booting. This is the aim for current > week. > > Regards, > Ernest
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANFE%2BdxusWQ%2BMh4FTHF=9jwrE7n2Fh605CtmOMJ_%2BXYVPP8AnA>