Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Google Summer of Code 2013
Date: Sun, 3 Mar 2013 19:26:30 +0100	[thread overview]
Message-ID: <20130303192630.4e730af4@skate> (raw)
In-Reply-To: <51338DA1.3090000@relinux.de>

Dear Stephan Hoffmann,

On Sun, 03 Mar 2013 18:51:29 +0100, Stephan Hoffmann wrote:

> I think all the suggestions are good, but the ARM SoC multimedia
> libraries are most important. These chips seem to become very popular,
> especially since there are low-cost platforms available as Beaglebone,
> Pengwyn, Wandboard or Raspberry Pi. As I have seen at the Embedded World
> in Nuremberg last week there are lots of industrial grade boards and
> modules especially with iMX5x, iMX6 and AM335x available or introduced.
> I expect that these systems will get a significant market share soon. So
> it might be really important to have good support for them in buildroot.
> 
> There are gazillions of such SoC available, but I think that Freescale
> and Texas are the most wide spread. Of course we cannot leave out RPi,
> although  I do not think that it has a significance in the industrial
> sector.
> 
> Maybe we should think about splitting this up into different projects,
> since the three platforms might be to much for one student.

I think we should maybe get started with only one GSoC project, since
we don't have much experience in mentoring a student.

The only issue with the topic related to multimedia packages for ARM
SoCs is that it requires some hardware, and I'm not sure where to get
the funding for that. Google says they pay $500 to the mentoring
organization, but I think this gets paid at the end of the GSoC, and
anyway we don't have any legal organization to receive this money.

Another solution is to get a little bit of sponsoring: getting one
BeagleBone and one i.MX6 based board sponsored shouldn't be too hard.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-03-03 18:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-08 23:42 [Buildroot] Report from the Buildroot Developers Meeting Thomas Petazzoni
2013-02-12 10:30 ` Stephan Hoffmann
2013-02-12 10:36   ` Thomas Petazzoni
2013-02-12 11:49     ` Stephan Hoffmann
2013-02-12 11:53       ` Thomas Petazzoni
2013-02-12 11:55   ` Stefan Fröberg
2013-02-12 14:14 ` Daniel Nyström
2013-02-12 14:18   ` Thomas Petazzoni
2013-02-12 15:57     ` Daniel Nyström
2013-02-13 18:55 ` Yann E. MORIN
2013-02-13 19:54   ` Thomas Petazzoni
2013-02-14 14:25   ` [Buildroot] Google Summer of Code 2013 Thomas Petazzoni
2013-03-03 13:43     ` Thomas Petazzoni
2013-03-03 17:29       ` Thomas De Schampheleire
2013-03-03 17:51       ` Stephan Hoffmann
2013-03-03 18:26         ` Thomas Petazzoni [this message]
2013-03-05  6:25           ` Arnout Vandecappelle
2013-03-05 18:32             ` Thomas Petazzoni
2013-03-06  8:57             ` Jérôme Pouiller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130303192630.4e730af4@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox