From: Stanislav Brabec <utx@penguin.cz>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andy Green <andy@warmcat.com>, Eric Miao <eric.y.miao@gmail.com>,
dbaryshkov@gmail.com, Cyril Hrubis <metan@ucw.cz>,
arminlitzel@web.de, kernel list <linux-kernel@vger.kernel.org>,
Dirk@opfer-online.de, lenz@cs.wisc.edu, rpurdie@rpsys.net,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
thommycheck@gmail.com, zaurus-devel@www.linuxtogo.org,
omegamoon@gmail.com
Subject: Re: bit errors on spitz
Date: Mon, 29 Mar 2010 20:52:08 +0200 [thread overview]
Message-ID: <1269888728.3972.73.camel@hammer.suse.cz> (raw)
In-Reply-To: <20100329182736.GA1373@ucw.cz>
Pavel Machek wrote:
> > Alternatively, it is possible to write a driver. It is just one byte
> > write and one byte read via I2C.
>
> Do you know what byte it is? That sounds easy enough...
Yes, it should be easy driver. One byte address and then one byte write
or one byte read.
See the datasheet:
http://www.penguin.cz/~utx/zaurus/datasheets/power/XScale/ISL6271A.pdf
Page 11: address
Pages 8 and 9: Data interpretation
--
Stanislav Brabec
http://www.penguin.cz/~utx/zaurus
prev parent reply other threads:[~2010-03-29 18:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 21:27 Pavel Machek
2010-03-08 5:37 ` Eric Miao
2010-03-08 7:28 ` Pavel Machek
2010-03-08 8:25 ` Cyril Hrubis
2010-03-08 11:48 ` Stanislav Brabec
2010-03-08 12:16 ` Cyril Hrubis
2010-03-08 12:42 ` Russell King - ARM Linux
2010-03-08 13:32 ` Cyril Hrubis
2010-06-03 0:01 ` [URGENT] Re: bit errors on spitz + voipac Marek Vasut
2010-06-03 2:30 ` Eric Miao
2010-03-21 20:40 ` bit errors on spitz Pavel Machek
2010-03-11 13:25 ` Andy Green
2010-03-11 15:42 ` Stanislav Brabec
2010-03-11 21:21 ` Andy Green
2010-03-12 9:07 ` Stanislav Brabec
2010-03-12 9:33 ` Andy Green
2010-03-12 10:43 ` Stanislav Brabec
2010-03-12 11:13 ` Andy Green
2010-03-21 20:43 ` Pavel Machek
2010-03-21 21:42 ` Stanislav Brabec
2010-03-29 18:27 ` Pavel Machek
2010-03-29 18:52 ` Stanislav Brabec [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=1269888728.3972.73.camel@hammer.suse.cz \
--to=utx@penguin.cz \
--cc=Dirk@opfer-online.de \
--cc=andy@warmcat.com \
--cc=arminlitzel@web.de \
--cc=dbaryshkov@gmail.com \
--cc=eric.y.miao@gmail.com \
--cc=lenz@cs.wisc.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=metan@ucw.cz \
--cc=omegamoon@gmail.com \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.net \
--cc=thommycheck@gmail.com \
--cc=zaurus-devel@www.linuxtogo.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
all inboxes | Powered by JetHome®