I just got this:

> Thank you for submitting OpenRISC's application to Google Summer of Code 
> 2014. Unfortunately, we were unable to accept your organization's application 
> at this time. Every year we receive many more applications than we are able 
> to accommodate, and we would encourage you to reapply for future instances of 
> the program.
> If you would like some general feedback on why your organization was not 
> accepted, please consider attending the IRC meeting in #gsoc on Freenode on 
> Friday, 28 February, 2014 at 16:00 UTC. Please note that the feedback meeting 
> will be limited to the first 50 organizations to queue up (queuing in the 
> channel will begin at 15:30 UTC).

Too bad.
The meeting might be worth attending to know what to improve until next year.


On Fri, Feb 21, 2014 at 10:25 AM, Sébastien Bourdeauducq <[email protected]> wrote:
> On 02/17/2014 04:16 PM, Stefan Kristiansson wrote:
>> As I also mentioned before was that last I tried synthesizing mor1kx
>> in the (now dated) milkymist-ng soc, I passed the 83 MHz timing
>> constraint without errors.
>
> Ok, this works here now as well.
>
>> Let me give an example, we have a set of SPRs that gives information
>> about what units are present,
>> the version, revision etc of the core. That's stuff we want to have
>> there, and generic software cares about it.
>> Now, if you have a set of very specialized software that only care
>> about a given set of features,
>> you could probably care less about what version the core is and what
>> set of units are present.
>> Those particular SPRs doesn't of course take a lot of space, but they
>> serve a good example of the "problem".
>
> Well, no they don't, so they're not a good example :-)
>
> I will look at the resource utilization per submodule and try to get
> some hard numbers on what needs to be removed/modified first from the
> spec (or implemented in a more efficient way).
>
> Sébastien
>
> _______________________________________________
> OpenRISC mailing list
> [email protected]
> http://lists.openrisc.net/listinfo/openrisc
_______________________________________________
OpenRISC mailing list
[email protected]
http://lists.openrisc.net/listinfo/openrisc

Reply via email to