From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/3] ARM: omap3: add Seagate Wireless Plus board
Date: Wed, 8 May 2013 12:51:53 -0700 [thread overview]
Message-ID: <20130508195152.GE32546@atomide.com> (raw)
In-Reply-To: <cover.1368038129.git.jason@lakedaemon.net>
* Jason Cooper <jason@lakedaemon.net> [130508 12:29]:
>
> Current Problem:
>
> There are several gaps in my understanding of how far along TI's conversion to
> DT is. Should I be doing a separate board file for initializing the legacy
> items? I was hoping to do it all with DT.
Sorry forgot to reply to this.. No seprate board file should be needed,
some devices may still need to be initialized with pdata based on the
compatible flag.
> Obviously, I don't expect anybody to run out and buy one of these, take it
> apart, and try to boot this code. But if the omap guys could take a look at
> this and give me a few pointers, I'd appreciate it. I'm kind of spinning my
> wheels at the moment.
>
> Primarily, I'd like to get nand and usb working, so that I can read/write,
> mount a rootfs and do better testing.
The USB should be doable with device tree. At least both echi and
musb are working properly on pandaboard. I think people have been
using NAND with the gpmc DT patches, but I don't know the current
status for sure.
Is the hard drive on the EHCI bus or how is it connected to omap?
Regards,
Tony
next prev parent reply other threads:[~2013-05-08 19:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 19:23 [RFC PATCH 0/3] ARM: omap3: add Seagate Wireless Plus board Jason Cooper
2013-05-08 19:23 ` [RFC PATCH 1/3] ARM: omap3: " Jason Cooper
2013-05-08 19:23 ` [RFC PATCH 2/3] ARM: omap3: Seagate Wireless Plus DT entry Jason Cooper
2013-05-08 19:23 ` [RFC PATCH 3/3] ARM: omap3: wireless plus gpmc wip Jason Cooper
2013-05-08 19:45 ` [RFC PATCH 0/3] ARM: omap3: add Seagate Wireless Plus board Tony Lindgren
2013-05-09 0:36 ` Jason Cooper
2013-05-09 15:56 ` Tony Lindgren
2013-05-09 16:05 ` Tony Lindgren
2013-05-08 19:51 ` Tony Lindgren [this message]
2013-05-08 21:58 ` Jason Cooper
2013-05-08 22:30 ` Tony Lindgren
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=20130508195152.GE32546@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).