From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: MUSB multiplatform work?
Date: Fri, 31 May 2013 10:52:30 -0700 [thread overview]
Message-ID: <20130531175228.GP6467@atomide.com> (raw)
In-Reply-To: <20130531040004.GA7879@arwen.pp.htv.fi>
* Felipe Balbi <balbi@ti.com> [130530 21:06]:
> On Thu, May 30, 2013 at 01:54:49PM -0700, Tony Lindgren wrote:
> > * Tony Lindgren <tony@atomide.com> [130530 13:25]:
> > >
> > > TUSB we can make depend on ARMv7, the only implementation we have
> > > is for omap2420, which is ARMv6. This should solve the issue for
> > > ARMv7 multiplatform builds for now.
> >
> > Sorry mean depend on !ARMv7. But thinking about it more, that does
> > not make much sense as it would break things for omap2plus_defconfig
> > at least which is multiplatform v6 and v7. For now TUSB can be made
> > to depend on MACH_NOKIA_N8X0. I doubt that anybody is using the add
> > on cards for H4 boards any longer..
>
> could also be made to depend on BROKEN. I don't think anyone *really*
> cares about that glue layer other than the very few in the world who
> still like the nostalgic feeling of booting current linux releases on
> n8x0 devices.
Unfortunately that's the best test case we have for GPMC and DMA stress
testing so it's good to keep around.
And n8x0 is still quite usable general purpose pocket computer with
keyboard and WLAN and tons of storage :)
Regards,
Tony
prev parent reply other threads:[~2013-05-31 17:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 15:02 MUSB multiplatform work? Arnd Bergmann
2013-05-28 16:35 ` Felipe Balbi
2013-05-30 20:18 ` Tony Lindgren
2013-05-30 20:21 ` Linus Walleij
2013-05-30 20:31 ` Tony Lindgren
2013-05-30 21:19 ` Linus Walleij
2013-06-12 10:05 ` Vinod Koul
2013-06-12 11:57 ` Jassi Brar
2013-06-17 13:43 ` Vinod Koul
2013-06-17 15:57 ` Jassi Brar
2013-06-01 11:41 ` Jassi Brar
2013-05-30 20:54 ` Tony Lindgren
2013-05-31 4:00 ` Felipe Balbi
2013-05-31 17:52 ` Tony Lindgren [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=20130531175228.GP6467@atomide.com \
--to=tony@atomide.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).