Hi Team,
My status update of last two weeks.
WEEK1 (May, 19-23)
Tasks assigned:
1 - Setup and document the development environment to compile and run the linux kernel using device tree on QEMU - CO
2 - Study related code and documents to understand device tree - CO
WEEK2 (May, 26-30)
Tasks assigned
1 - Build the testcase data into a separate .dtb file (instead of including it into the platform dtb) - CO
2 - Link the testcase data into the kernel using the %.dtb.S rule - CO
3 - At selftest init time, obtain the pointer to the selftest dtb and use printk to dump out some of the header information - CO
4 - Send Grant a patch file using git send-email that covers the above. - CO
CO - Completed; IP - In Process; NP - Not started
Note: It is also available on GSOC tracking document
Please let me know if I'm missing something.
--
Regards
Gaurav Minocha
Hi Gaurav,
As promised, here is my script for building a super simple root
filesystem with busybox. All it needs is for you to download a copy of
the busybox source code and have the required cross compiler. You can
pass the result to the QEMU with the -initrd parameter. You'll also
need to pass "rdinit=/sbin/init" to the kernel when using these
images.
I've also attached the images I've built for aarch64, arm and powerpc
and the (really, really ugly) script I use for building and booting
the kernel. My build and boot script probably isn't going to work for
you out of the box. A lot of it is specific to my setup and has been
hacked together over many years.
g.
Hi folks,
Just a quick reminder - mid-term evaluations are due this
week. Deadline is 19:00 UTC Friday. If you need help, please shout...
Cheers,
--
Steve McIntyre steve.mcintyre(a)linaro.org
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs
Hello all,
Here is the report for the first two weeks of the "Lightweight IP Stack on top of OpenDataPlane" project. Fortunately no blocking issues were found for now, and I believe the work is progressing well (on schedule). I have written the progress on a per-week basis, and included the current plans for this week as well.
=== Week 1 Progress ===
Worked Hours: 44
-> Set up the development environment for the project, including necessary dependencies and documentation / testing tools.
-> Started porting LwIP from a bottom up approach, using the ODP API as adequate.
-> Started porting the sys_arch / netif layer to use ODP as a platform. This layer abstracts low level I/O operations and other platform-specific behavior from the userspace IP stack itself. I believe ODP fits well in terms of architecture and functionality here. It is important to note that the linux-generic implementation is used as a basis for this project.
=== Week 2 Progress ===
Worked Hours: 40
-> Finished porting the LwIP sys_arch / netif layers. Now all platform-specific behavior and low-level I/O operations is based on OpenDataPlane; for now only the linux-generic implementation was considered, but after this initial work other ports should be relatively straightforward.
-> Fixed (hopefuly) a buffer usage issue that blocked me from testing what was already implemented. It was actually a programming mistake on my part that went unnoticed, so I did not report it earlier.
-> A set of LwIP examples were tested using ODP as a platform, to test current functionality.
-> Generated a call-graph diagram from LwIP. This should assist the porting and optimization of the next layers in the stack.
=== Plans for Week 3 ===
-> Start porting the IP Layer to use ODP platform-independent features (Milestone 2 of the project proposal). Now the fun part starts :)
-> Post available project information/documentation (both past and current) to the gsoc.linaro.org wiki, organized into sub-sections. [High priority]
-> Create a git repository and make available the first version of LwIP-ODP on it.
=== Issues ===
-> During the Community Bonding phase, it was suggested that I could study the QNX networking code and see how it applies to this project and ODP in general. However, it seems the QNX source code is not really open, or at least not easily acessible [1]. I really don't know how to proceed on this front, or how to fit it in the GSOC project scope... [Non-blocker; low priority?]
[1] http://community.qnx.com/sf/wiki/do/viewPage/projects.core_os/wiki/Os_sourc…
[2] http://community.qnx.com/sf/wiki/do/viewPage/projects.community/wiki/Update…
---
Ricardo de Freitas Gesuatto
Hi folks,
*tumbleweed*
We're near the end of week 2 of GSOC, but I've not seen any reports
for week 1 yet. I hope that our students have just forgotten to CC
this list...?
Cheers,
--
Steve McIntyre steve.mcintyre(a)linaro.org
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs
Hi all,
After several weeks of review and discussion, the application and
selection period for the 2014 Google Summer of Code is over. 4,420
students proposed a total of 6,313 projects for this summer. From
those, 1,307 students have been accepted [1], and Linaro is one of the
190 Open Source projects that will be working with students this year.
In our first year as a GSOC mentoring organisation, we received 17
applications and Google allocated us 3 slots for student projects. It
was quite a challenge to pick just 3 projects from the excellent
field, and it's a shame that the limited number of slots meant we had
no choice but to disappoint some people. Thanks to all those who
applied!
I'm delighted to announce our 3 chosen interns for 2014:
* Gaurav Minocha is a graduate student at the University of British
Columbia, Vancouver, Canada. His project is Linux Flattened Device
Tree Self-checking, mentored by Grant Likely from Linaro's Office
of the CTO.
* Ricardo de Freitas Gesuatto is a student at Federal University of
São Carlos (UFSCar), Brazil. He will be working on a project
entitled "Lightweight IP Stack on top of OpenDataPlane", mentored
by Maxim Uvarov from the Linaro Networking Group.
* Varad Gautam is a student at Birla Institute of Technology and
Science, Pilani, India. He will be Porting UEFI to Low-Cost
Embedded Platform (BeagleBoneBlack). Leif Lindholm from the Linaro
Enterprise Group will be mentoring.
Please join me in welcoming these three new engineers to the Linaro
team!
We have a GSOC wiki ready for our students to use at
https://gsoc.linaro.org/
and hopefully they will start adding content there soon about
themselves and their projects (hint!). In the meantime, we have more
information about our original proposals and the GSOC program in the
main Linaro wiki [2].
Starting today, the next phase of the program is the so-called
"bonding period". Students are encouraged to get to know people within
Linaro (especially their mentors!) and prepare to start work on their
projects, whatever is needed. The official start of the work period
for GSOC is May 19th, and it runs through to August 18th. [3] We will
give updates on progress through the summer, and we're hoping to talk
about our results at the next Linaro Connect in September.
Good luck, folks!
[1] http://google-opensource.blogspot.co.uk/2014/04/students-announced-for-goog…
[2] https://wiki.linaro.org/SummerOfCode2014
[3] http://www.google-melange.com/gsoc/events/google/gsoc2014
Cheers,
--
Steve McIntyre steve.mcintyre(a)linaro.org
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs
Hi to Gaurav, Ricardo and Varad!
I've just made sure that you're all signed up for the mailing list
here. By all means change your subscriptions to use a more-preferred
email address, but please stay subscribed somehow as this is the
easiest way to get in touch.
First of all, congratulations on being accepted for the Google Summer
of Code 2014 and welcome to Linaro! Now the real hard work
starts... :-)
Today (22nd April) is the start of the bonding period. You're strongly
encouraged to get to know your mentors and prepare for your summer
project. Exactly what that entails is up to you and your mentors, but
try to spend some time and be ready. It's also worth signing up for
other Linaro mailing lists related to your project, and please join us
on the various IRC channels too if you can. freenode.org, #linaro-gsoc
is a good place to be.
Timings
=======
Google's timeline page at
http://www.google-melange.com/gsoc/events/google/gsoc2014
is an important thing to use - it contains all the key dates for the
summer. Key highlights:
* 22nd April - Bonding period start
* 19th May - Official project start
* 27th June - Midterm evaluation deadline
* 11th August - Suggested "pencils down" date
* 22nd August - Final evaluation deadline, code submissions to Google
Resources
=========
We have a GSOC-specific wiki set up at
https://gsoc.linaro.org/
with some boiler-plate text in place so far. Hopefully you *should* be
able to register for accounts and add some text about yourselves and
your projects now. Please try and do that ASAP, and let me know if you
have any problems with that.
I'd like to encourage you to post to the Linaro mailing lists, and
definitely to blog about what you're working on! planet.linaro.org is
our obviously-named blog aggregator - please point me at your
Linaro-related feeds and I'll get you added there.
In terms of code hosting, please work out with your mentors the best
system / place to do that. Your code needs to be public, so obvious
possibilities are places like github.
If you've got random questions that you're not sure who to ask, please
ask here on the linaro-gsoc list, or on IRC, or we have a more generic
linaro-mentors mailing list (and matching #linaro-mentors IRC channel)
too.
Reporting
=========
On top of the mandatory mid-term and final evaluations that Google
require, once you've started the main coding phase we will ask you to
send in a weekly progress report describing how you're getting
on. Please send them to the mailing list. They don't have to be
*vastly* detailed, but please keep us up to date on what you're doing!
Your mentor should be on top of this even more, but how and how often
you talk to them is up to you and them to work out - irc, mail, phone,
skype, hangouts are all an option here. Your (primary) mentor should
also introduce you to secondary mentor(s) in case of vacation etc. -
please ask!
Problems?
=========
If you have issues, don't get down. Ask us - we're here to help. We
don't bite! Obviously, your mentor should be your first port of call
if you need anything. If there are problems there, by all means
contact me and the other admins:
Steve McIntyre <steve.mcintyre(a)linaro.org>
Leif Lindholm <leif.lindholm(a)linaro.org>
Wookey <wookey(a)linaro.org>
and we'll do what we can to help. If there's still an issue at that
point, please talk to the GSOC admins at Google and they'll help to
resolve things.
We're expecting a lot of work from you this summer, but we also
understand that you're not that experienced and this could be quite
daunting! The main thing is - please stay in touch. If you go quiet
and we can't talk to you then that's the worst option.
In case of emergency, let us know. If you haven't already provided
them, please give me emergency contact phone numbers privately (or to
the list if you're happy for them to be public!). I doubt we'll need
them, but it's best to have them *just in case*. I'll happily give you
my own number in return.
Finally
=======
Welcome aboard! I hope you all have a fun summer and achieve some
great results in your projects!
Cheers,
--
Steve McIntyre steve.mcintyre(a)linaro.org
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs
Hi folks,
The nice people at Google have given us *3* slots for student projects
this summer. Based on past experience and guidance this year, they've
been very generous to us. Let's do our best to not let them down!
Cheers,
--
Steve McIntyre steve.mcintyre(a)linaro.org
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs
Hi folks,
We're just 1 day away from the deadline for student applications in
this year's Summer of Code. What does that mean?
Deadline
========
**************************************************************
* *
* STUDENT APPLICATION DEADLINE: 19:00 UTC, Friday 21st March *
* *
**************************************************************
At that point (just over 24 hours from now), students will no longer
be able to make new applications in Google's melange web
app. *Existing* applications will be editable after that deadline, but
may need some mentor/admin intervention to do so. (I'm told there will
be a toggle to make an application ediable again.)
So: if you're a student considering applying to work with Linaro this
summer, you *must* have an application posted in Melange by the
deadline. If you've been holding back and have not applied yet, don't
delay!
Equally, if you're a mentor and you've been discussing a possible
application with a prospective student, please pass this information
along to them as well. Once that deadline has passed, Google will not
accept any more applications for 2014.
What happens beyond that point - tweaks, ranking and slots
==========================================================
Mentors and admins should review all the applications posted, working
out which of the applications they consider good enough. If there are
any questions for the students, or suggestions on how to improve the
applications or further things that should be done: this is the last
possible stage for this dialogue to happen.
The next deadline is the 6th of April. By this point, the admins and
mentors must have worked out which of the student applications are
best and marked them accordingly in Melange.
As an organisation, we must then decide how many project slots to
request from Google. If we have 5 really good applications for 5
different projects, then clearly we will apply for 5 slots. If we have
4 really good applications but they're only covering 2 different
projects (i.e. 2 each), then we should only apply for *2*
slots. There's no scope for multiple instances of a single project
here. So, here's a hint to the students: if you're applying for a
project then try and make your stand out. Either make it the clear
*best* proposal for a project, or come up with a distinct project
proposal so that it makes sense as a separate slot.
Google will then review all the slot requests from all the
organisations and will allocate them as they see fit. That's when we
and the other orgs get to decide which student proposals to accept for
the summer. Then the fun starts!
Students - how to apply
=======================
I was hoping to have our wiki set up for student access by now, but
it's not happened yet. We *will* have something in the next few days
so it's working for the summer, but don't wait for that now. Student
applications should be made through Melange, ideally using our
application template from
https://wiki.linaro.org/SummerOfCode2014/StudentApplicationTemplate
as a basis. Don't feel constrained to *only* give us the information
that's requested there - please make applications as complete and as
creative as possible. Suggested timelines and milestones are good
here. Show us evidence that you've researched the topic of your
project and you're not just regurgitating what we suggested in the
posted project ideas page. Make it clear why you think *you* are the
right person to work on your project.
At this stage, make sure that you're responsive to feedback and
questions too. Now is the time to impress your potential mentors. Join
us on the mailing list or on irc and discuss things.
Mentors - ranking process
=========================
I'll be in touch shortly with a plan for this. Watch this space! In
the meantime, please provide timely feedback and help to
students. Things may be about to get very busy... :-) In the meantime,
you should be able to read some more background in the (internal) wiki
at
https://wiki.linaro.org/Internal/SummerOfCode2014/Mentors
Finally
=======
Good luck to all of you, and let's hope we get some awesome student
proposals that will lead to successful projects.
Cheers,
--
Steve McIntyre steve.mcintyre(a)linaro.org
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs
Hi. I am interested in participating in Google Summer of Code - 2014 with
Linaro and working on two of the ideas from Ideas page [1]:
AArch64 porting of Free Software Packages - I am amazed going through the
details mentioned at [2] about the use of assembly in packages. I would
like to discover more, and figure out where I could contribute.
Port UEFI to Low-Cost Embedded Platform - Although I have not used a system
with UEFI before, I want to know more about the low level interaction that
occurs between the kernel and the hardware.
Please help me get started and gain a better understanding of what
implementing each of these ideas would involve.
About me:
I can program with C, Perl, Python, Processing and Shell Scripts. I built a
game for the Intel Perceptual Computing Challenge-2013 [3] and have
experience with development for the Beagleboard and Pandaboard. I am
currently reading Greg K-H's Linux Device Drivers to figure out how drivers
work. I am also learning the x86 assembly language. I have been an open source
user for a long time, and have a commit integrated into GNOME's Anjuta IDE
[4]
I recently worked with Red Hat on testing the effectiveness of random
number generators on a virtual machine with qemu.[5]
I also have a fair know-how of git.
[1] https://wiki.linaro.org/SummerOfCode2014/ProjectIdeas
[2] https://wiki.linaro.org/LEG/Engineering/OPTIM/Assembly
[3]
http://varadgautam.wordpress.com/2013/09/26/bender-a-game-using-the-intel-p…
[4]
https://git.gnome.org/browse/anjuta/commit/?id=eb10532632014b59505c788ffad4…
[5]
http://varadgautam.wordpress.com/2013/12/17/dieharder-tests-on-a-qemu-vm-1-…
Thanks.
Varad
