From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Derald D. Woods" <woods.rt@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: i.MX21 USB OTG
Date: Fri, 23 Mar 2012 09:36:43 +0100 [thread overview]
Message-ID: <20120323083643.GI3852@pengutronix.de> (raw)
In-Reply-To: <20120322232544.GA3867@numbers.woodsts.org>
Hi Derald,
On Thu, Mar 22, 2012 at 06:25:44PM -0500, Derald D. Woods wrote:
> All,
>
> I have an existing design that uses the i.MX21 ARM9 processor. The
> design currently uses an external USB OTG chip. The chip is now
> end-of-life. I know that this is an older ARM processor. It still meets
> most of the design needs. Is the i.MX21 OTG functionality considered
> reliable? I have not seen any real success stories with the i.MX21 USB
> OTG implementation. Our board currently utilizes the USB OTG chip at
> the bootloader and Linux kernel level.
>
> I would appreciate being pointed in the right direction or warned of
> impending danger.
>
> I posted to this list because the support for i.MX2x processors is still
> fairly active in the Barebox community.
The i.MX21 is the only i.MX I never used. Maybe you should contact
Martin Fuzzey <mfuzzey@gmail.com>, he mainlined the i.MX21 USB host
driver in Linux.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-03-23 8:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 23:25 Derald D. Woods
2012-03-23 8:36 ` Sascha Hauer [this message]
[not found] <CAPhRStYbTCD6Lzhcfna4WRqYZhQRJrmiEyFm6egFovYdVso59g@mail.gmail.com>
2012-03-24 14:10 ` Martin Fuzzey
2012-03-24 16:15 ` Derald D. Woods
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=20120323083643.GI3852@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=woods.rt@gmail.com \
/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