From: Nick Teen <xpage_de-LWAfsSFWpa4@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>,
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: i2c_smbus_write_block_data does not send all bytes?!
Date: Tue, 15 Jul 2008 17:28:34 +0000 (GMT) [thread overview]
Message-ID: <968764.38783.qm@web27601.mail.ukl.yahoo.com> (raw)
In-Reply-To: <20080715185223.7f2f39aa-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
--- Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org> wrote:
> Which bus do you see the device on in i2cdetect? You said
> earlier that you were using the i2c-i801 driver, which is expected for
> an Intel motherboard. However you say that the PIC is connected to
> an SMSC chip, and not the Intel south bridge? Are you sure? If you are,
> what is the name of the SMSC chip in question?
Okay, i was wrong. The smsc47m192 _and_ the PIC is connected to the SMBus I801 (at a040). If i type "sensors", i get sensor data from 0x2d.
> Which i2c bus are you running your program on? The
> "SMBus I801" one?
I'm afraid so.
> Note that it is not entirely impossible that the block
> write support in the i2c-i801 driver is broken. This is a driver which is
> mostly used to access SPD EEPROMs and hardware monitoring chips, to which
> you never write blocks.
Okay... so i've no chance to send the PIC block data. :'-(
Thanks a lot! I give up. ;-)
Nick
__________________________________________________________
Gesendet von Yahoo! Mail.
Dem pfiffigeren Posteingang.
http://de.overview.mail.yahoo.com
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
next prev parent reply other threads:[~2008-07-15 17:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 8:29 i2c_smbus_write_block_data does not send all bytes?! Nick Teen
[not found] ` <884255.29098.qm-WOTGQye7mknGRxTy+Q50vsz6deESKz/lQQ4Iyu8u01E@public.gmane.org>
2008-07-15 10:57 ` Jean Delvare
[not found] ` <20080715125702.48c9569b-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-07-15 12:22 ` Nick Teen
[not found] ` <952972.59634.qm-WQsacCdWWGLGRxTy+Q50vsz6deESKz/lQQ4Iyu8u01E@public.gmane.org>
2008-07-15 12:32 ` Jean Delvare
[not found] ` <20080715143258.2bef9c1e-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-07-15 13:02 ` Nick Teen
[not found] ` <732644.12112.qm-qWTMlLQujKzGRxTy+Q50vsz6deESKz/lQQ4Iyu8u01E@public.gmane.org>
2008-07-15 13:13 ` Jean Delvare
[not found] ` <785052.52325.qm@web27604.mail.ukl.yahoo.com>
[not found] ` <785052.52325.qm-qWTMlLQujKzGRxTy+Q50vsz6deESKz/lQQ4Iyu8u01E@public.gmane.org>
2008-07-15 16:52 ` Jean Delvare
[not found] ` <20080715185223.7f2f39aa-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-07-15 17:28 ` Nick Teen [this message]
[not found] ` <968764.38783.qm-fkCdBXra523GRxTy+Q50vsz6deESKz/lQQ4Iyu8u01E@public.gmane.org>
2008-07-15 17:52 ` Jean Delvare
-- strict thread matches above, loose matches on Subject: below --
2008-07-15 7:29 Nick Teen
[not found] ` <180252.53613.qm-WQsacCdWWGLGRxTy+Q50vsz6deESKz/lQQ4Iyu8u01E@public.gmane.org>
2008-07-15 7:47 ` Jean Delvare
2008-07-14 20:32 Nick Teen
[not found] ` <247321.99325.qm-SFSZVIN0dfnGRxTy+Q50vsz6deESKz/lQQ4Iyu8u01E@public.gmane.org>
2008-07-14 20:54 ` Jean Delvare
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=968764.38783.qm@web27601.mail.ukl.yahoo.com \
--to=xpage_de-lwafssfwpa4@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.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.