From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "David Brownell" <david-b@pacbell.net>
Cc: "Felipe Balbi" <me@felipebalbi.com>,
"Tony Lindgren" <tony@atomide.com>,
"Bryan Wu" <cooloney@kernel.org>,
linux-omap@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] MUSB: 2 patches to fix some bug found on Blackfin
Date: Wed, 21 May 2008 16:10:00 -0400 [thread overview]
Message-ID: <8bd0f97a0805211310t650ccbb1u9a2ecf789ce74458@mail.gmail.com> (raw)
In-Reply-To: <200805211304.53082.david-b@pacbell.net>
On Wed, May 21, 2008 at 4:04 PM, David Brownell wrote:
> That said, I'm looking forward to seeing the www.beagleboard.org
> hardware [1] become more generally available. That will make some
> musb_hdrc hardware available in a more developer-friendly rig than,
> say, an N810 tablet. And it might well get more folk in a position
> where they can use that driver! (I think some Blackfin devboards
> are available already, but they're more pricey.)
unfortunately, that is the case. the BF527 EZKit is ~$900 while the
BF548 EZKit is ~$1000. i'm hoping us software guys keep complaining
enough for the hardware guys to put out a bare bone kit at a
reasonable price (sub $300).
-mike
prev parent reply other threads:[~2008-05-21 20:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 11:01 Bryan Wu
2008-05-17 11:01 ` [PATCH 1/2] MUSB: fix bug - since 2.6.24 urb API changed, giveback function return wrong status Bryan Wu
2008-05-17 11:01 ` [PATCH 2/2] MUSB: Real fix bug 4 usb bugs found on Blackfin Bryan Wu
2008-05-19 15:16 ` Gadiyar, Anand
2008-05-19 15:28 ` Mike Frysinger
2008-05-17 14:37 ` [PATCH 0/2] MUSB: 2 patches to fix some bug " David Brownell
2008-05-19 6:39 ` Bryan Wu
2008-05-19 7:49 ` Felipe Balbi
2008-05-19 8:05 ` Bryan Wu
2008-05-21 15:50 ` Tony Lindgren
2008-05-21 17:14 ` David Brownell
2008-05-21 19:06 ` Felipe Balbi
2008-05-21 20:04 ` David Brownell
2008-05-21 20:10 ` Mike Frysinger [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=8bd0f97a0805211310t650ccbb1u9a2ecf789ce74458@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=cooloney@kernel.org \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=me@felipebalbi.com \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®