From: ivo.clarysse@gmail.com (Ivo Clarysse)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mx31pdk: Add NAND support
Date: Fri, 26 Feb 2010 14:14:53 +0100 [thread overview]
Message-ID: <ba216b431002260514v614411b5k9671dafd1e17490f@mail.gmail.com> (raw)
In-Reply-To: <1267182306.2778.73.camel@realization>
2010/2/26 Alberto Panizzo <maramaopercheseimorto@gmail.com>
[...]
> For me it is not a problem and I think that the motivations are: Freescale
> can build different type of Product Development Kit, indeed the 3-Stack
> is the particular one -> call it mx[N]_3ds.c
> But Freescale do not produce multiple mx[N] PDKs.
>
Yes it does: i.MX25 PDK, MX27 PDK, MX31 PDK and the MX35 PDK.
Basically, everything which Freescale used to call a "i.MX[N] 3-Stack
Development System", Freescale now refers to as "i.MX[N] PDK" (Platform
Development Kit).
Best regards,
Ivo.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100226/26a11b34/attachment-0001.htm>
next prev parent reply other threads:[~2010-02-26 13:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 0:58 [PATCH] mx31pdk: Add NAND support Fabio Estevam
2010-02-25 10:58 ` Alberto Panizzo
2010-02-25 22:09 ` Fabio Estevam
2010-02-26 9:36 ` Uwe Kleine-König
2010-02-26 10:19 ` Alberto Panizzo
2010-02-26 10:46 ` Uwe Kleine-König
2010-02-26 11:05 ` Alberto Panizzo
2010-02-26 13:14 ` Ivo Clarysse [this message]
2010-02-25 11:12 ` Alberto Panizzo
2010-02-25 21:59 ` Fabio Estevam
2010-02-25 22:19 ` Alberto Panizzo
2010-02-26 9:56 ` Juergen Beisert
2010-02-26 10:33 ` Alberto Panizzo
2010-02-26 11:48 ` Juergen Beisert
2010-02-26 13:29 ` Alberto Panizzo
2010-02-26 13:40 ` Juergen Beisert
2010-02-27 1:34 ` Fabio Estevam
2010-02-27 14:25 ` Alberto Panizzo
2010-02-27 15:38 ` Fabio Estevam
2010-02-27 16:17 ` Alberto Panizzo
-- strict thread matches above, loose matches on Subject: below --
2010-02-25 22:22 Fabio Estevam
2010-02-25 22:33 ` Alberto Panizzo
2010-02-25 22:52 ` Fabio Estevam
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=ba216b431002260514v614411b5k9671dafd1e17490f@mail.gmail.com \
--to=ivo.clarysse@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).