From: dashie@sigpipe.me (Dashie)
To: linux-arm-kernel@lists.infradead.org
Subject: Stuck getting DTS working for a new kirkwood board
Date: Sat, 22 Feb 2014 20:44:07 +0100 [thread overview]
Message-ID: <5308FE07.5070809@sigpipe.me> (raw)
In-Reply-To: <20140222193031.GG6667@lunn.ch>
On 02/22/2014 08:30 PM, Andrew Lunn wrote:
>> root at debian:~# i2cdetect 0
>> WARNING! This program can confuse your I2C bus, cause data loss and worse!
>> I will probe file /dev/i2c-0.
>> I will probe address range 0x03-0x77.
>> Continue? [Y/n]
>> 0 1 2 3 4 5 6 7 8 9 a b c d e f
>> 00: -- -- -- -- -- -- -- -- -- UU -- -- --
>> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>> 40: -- -- -- -- -- -- -- -- -- UU -- -- -- -- -- --
>> 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>> 60: -- -- -- -- 64 -- -- -- -- -- -- -- -- -- -- --
>> 70: -- -- -- -- -- -- -- --
> The datasheet for M41TC8025 says it uses 0x64.
>
> Could you of read the part wrong from the photo?
>
> Andrew
The only readings on the chip is :
"M41T80
ST(logo) E9927"
I have a picture here :
http://wiki.sigpipe.me/lib/exe/fetch.php?media=hacking:img_3329.jpg
next prev parent reply other threads:[~2014-02-22 19:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 21:22 Stuck getting DTS working for a new kirkwood board Dashie
2014-02-21 1:34 ` Jason Cooper
2014-02-21 7:39 ` Dashie
2014-02-21 15:15 ` Jason Cooper
2014-02-21 19:21 ` Dashie
2014-02-21 20:08 ` Jason Cooper
2014-02-21 22:01 ` Dashie
2014-02-21 22:12 ` Andrew Lunn
2014-02-22 8:54 ` Dashie
2014-02-22 18:41 ` Andrew Lunn
2014-02-22 18:50 ` Dashie
2014-02-22 19:30 ` Andrew Lunn
2014-02-22 19:44 ` Dashie [this message]
2014-02-22 22:25 ` Sebastian Hesselbarth
2014-02-22 18:44 ` Gerhard Sittig
2014-02-22 19:00 ` Dashie
2014-02-22 19:30 ` Jason Cooper
2014-03-26 1:01 ` Jason Cooper
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=5308FE07.5070809@sigpipe.me \
--to=dashie@sigpipe.me \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.