From: Gary Thomas <gary@mlbassoc.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Initialization order
Date: Tue, 02 Sep 2008 15:39:16 -0600 [thread overview]
Message-ID: <48BDB284.1070603@mlbassoc.com> (raw)
In-Reply-To: <20080902213312.GA18146@ld0162-tx32.am.freescale.net>
Scott Wood wrote:
> On Tue, Sep 02, 2008 at 03:28:19PM -0600, Gary Thomas wrote:
>> I'm working with a couple FreeScale platforms and having
>> trouble getting the RTC which is connected via I2C to work.
>> I had this working fine in the old arch/ppc tree, but it's
>> failing in the arch/powerpc world.
>
> Make sure the rtc chip is described in the device tree (search existing
> trees for rtc@ for examples).
That did it, thanks :-)
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2008-09-02 21:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 21:28 Initialization order Gary Thomas
2008-09-02 21:33 ` Scott Wood
2008-09-02 21:39 ` Gary Thomas [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=48BDB284.1070603@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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;
as well as URLs for NNTP newsgroup(s).