From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] building .sb files for freescale i.MX processors
Date: Fri, 9 Dec 2011 19:55:54 +0100 [thread overview]
Message-ID: <20111209195554.55ee02e8@skate> (raw)
In-Reply-To: <4EDF279D.3080608@free.fr>
Le Wed, 07 Dec 2011 09:45:17 +0100,
Julien Boibessot <julien.boibessot@free.fr> a ?crit :
> We (Armadeus) are currently working on it for our i.MX28 based SOM.
> Feel free to follow our progress on our SourceForge repository.
>
> We will send our patches to Buildroot as soon as we are satisfied
> with them.
Don't hesitate to send early versions so that we can help in polishing
them.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2011-12-09 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 21:29 [Buildroot] building .sb files for freescale i.MX processors Attila Kinali
2011-12-07 8:45 ` Julien Boibessot
2011-12-07 15:34 ` Attila Kinali
2011-12-09 18:55 ` Thomas Petazzoni [this message]
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=20111209195554.55ee02e8@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