From: Aaro Koskinen <firstname.lastname@example.org> To: Benoit Cousson <email@example.com> Cc: Tony Lindgren <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, Sakari Ailus <email@example.com> Subject: Re: [RFC/RFT] ARM: dts: add minimal DT support for Nokia N950 & N9 Date: Wed, 29 May 2013 23:56:48 +0300 [thread overview] Message-ID: <20130529205648.GC3345@blackmetal.musicnaut.iki.fi> (raw) In-Reply-To: <519DC39C.firstname.lastname@example.org> Hi, On Thu, May 23, 2013 at 09:22:04AM +0200, Benoit Cousson wrote: > On 05/22/2013 09:44 PM, Aaro Koskinen wrote: > > Add minimal DT support for Nokia N950 & N9. The basic boot works. I can > > connect to both devices with USB networking & ssh. dmesg output looks OK. > > That's great! Tony will like that :-) > It is too bad I just have a N900 :-( > > > Functionality compared to the legacy board file: > > > > - MMC not detected - reason unknown, any tips welcome > > On OMAP4 panda I used to have the similar issue due to the pbias not set > properly. > > > - OneNAND missing completely > > The GPMC for OMAP3 support is pretty new, so maybe some tweak are still > needed. > > Is it RFC because you are still working on the missing functionalities? > Otherwise the patches are already good to be merged if you want. > As soon as you don't break legacy boot, we can merge even half-working DTS. I was hoping to get the MMC working and OneNAND binding added before merging this... If we could do that, we could deprecate the legacy board file as DT would offer the same functionality. Anyway, if half-working DTS is also fine, I'll resend this as "PATCH" in a few days. A.
next prev parent reply other threads:[~2013-05-29 20:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-22 19:44 Aaro Koskinen 2013-05-23 7:22 ` Benoit Cousson 2013-05-29 20:56 ` Aaro Koskinen [this message] 2013-05-30 0:08 ` 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=20130529205648.GC3345@blackmetal.musicnaut.iki.fi \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [RFC/RFT] ARM: dts: add minimal DT support for Nokia N950 & N9' \ /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
This is a public inbox, see mirroring instructions on how to clone and mirror all data and code used for this inbox