From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [lm-sensors] Re: I2C block reads with i2c-viapro: testers wanted
Date: Thu, 11 Aug 2005 19:30:27 +0100 [thread overview]
Message-ID: <200508111930.27935.nick@linicks.net> (raw)
>> This is a surprising result, as the VT8233 datasheet didn't mention the
>> I2C block mode. I'll add this model to the list. This also suggests that
>> the VT8233A may support it as well - if someone could test that.
>>
>> I have to admit I don't know exactly in which order the different south
>> bridges were designed and released by VIA. I think the following order
>> is correct:
>>
>> VT82C596
>> VT82C596B
>> VT82C686A
>> VT82C686B
>> VT8235
>> VT8237
>>
>> But I don't know where the VT8231, VT8233 and VT8233A should be inserted
>> in this list. If anyone can tell me...
>
> I guess it's just the way it seems:
>
> VT82C596
> VT82C596B
> VT82C686A
> VT82C686B
> VT8231
> VT8233
> VT8233A
> VT8235
> VT8237
I have a VIA board, and remember when I config'ed I2C I was a bit confused
with what I have - I guessed logically in the end that VT82C686 _became_
VT82C686A _after_ VT82C686B was released. It all seems to work OK though.
bash-2.05b# lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev
22)
00:07.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C/VT8235 PIPC Bus Master IDE (rev 10)
00:07.2 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0 controller]
(rev 10)
00:07.3 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0 controller]
(rev 10)
00:07.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev
30)
00:09.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev
78)
00:0f.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07)
00:0f.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev
07)
01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX 440]
(rev a3)
I am OK for testing the patch if you need.
Nick
--
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."
next reply other threads:[~2005-08-11 18:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 18:30 Nick Warne [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-09 23:13 [lm-sensors] I2C block reads with i2c-viapro: testers wanted Jean Delvare
2005-08-10 5:56 ` [lm-sensors] " Salah Coronya
2005-08-10 12:15 ` Jean Delvare
2005-08-10 22:32 ` Hinko Kocevar
2005-08-10 23:06 ` Jean Delvare
2005-08-10 22:23 ` Martin Drab
2005-08-11 0:25 ` Martin Drab
2005-08-11 17:12 ` Jean Delvare
2005-08-11 19:12 ` Jean Delvare
2005-08-11 1:13 ` Hinko Kocevar
2005-08-11 18:56 ` Jean Delvare
2005-08-11 21:14 ` Krzysztof Halasa
2005-08-11 21:59 ` Jean Delvare
2005-08-11 23:40 ` Krzysztof Halasa
2005-08-11 23:49 ` Jean Delvare
2005-08-12 0:08 ` Krzysztof Halasa
2005-08-12 8:26 ` Jean Delvare
2005-08-12 17:30 ` Krzysztof Halasa
2005-08-12 19:58 ` 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=200508111930.27935.nick@linicks.net \
--to=nick@linicks.net \
--cc=linux-kernel@vger.kernel.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.