On 16 May 2015 at 09:38, Prannoy Pilligundla <prannoy.bits(a)gmail.com&gt; wrote: > Hello Everyone, > > I am Prannoy and I am a pre-final year undergrad student at BITS-Pilani, > India. I will be working on "Porting jor1k to RISC-V" as a part of Google > Summer of Code 2015. I am extremely honoured for having been selected. I > would like to thank the community for having faith in me and I promise to > put in my best efforts during the course of the project. I had successfully > completed Google Summer of Code 2014 with LyX. Also, congratulations to all > others who are participating in this year's Summer of Code. > > jor1k is currently built for OpenRISC (OR1K Specification) and my main > task would be to port it for RISC-V. My first goal would be to boot Linux > successfully. Then I am planning to work on implementing more features like > providing a web interface to test the compiled binaries, providing a demo > file system with some major tools, compiling the Linux kernel with the > drivers of the devices currently supported by jor1k, adding support to > features of lowRISC such as minion cores etc. Initially my plan is to focus > on booting Linux using a not-so-fast implementation taking safecpu.js [1] > as the reference. Then I plan to optimize the speed by working on > implementing an asm.js optimized version like in fastcpu.js [2] where the > number of lines of code executed per instruction is reduced to a minimum. > After I am done booting Linux via the optimized version, I will go on to > implement the other features. > > Looking forward to comments and suggestions from your side. > > Thanks and Regards > Prannoy Pilligundla > > [1] > https://github.com/s-macke/jor1k/blob/master/js/worker/or1k/safecpu.js > [2] > https://github.com/s-macke/jor1k/blob/master/js/worker/or1k/fastcpu.js > Hi Prannoy, thanks for introducing yourself. I'm about this project and look forward to seeing what you produce. However I must admit, this email is actually to test a problem with the mailing list. It seems that some email clients (including at least one version of Mail.app on OS X and mailman's pipermail web interface) render emails containing both a text/html and a text/plain part in base64-encoded form, which is not very useful (see http://listmaster.pepperfish.net/pipermail/lowrisc-dev-lists.lowrisc.org/...). These emails are fine in Gmail and on GMANE though: http://listmaster.pepperfish.net/pipermail/lowrisc-dev-lists.lowrisc.org/... I'm deliberately responding from Gmail in HTML mode as an experiment. Apologies for the noise!