public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Re: [lm-sensors] Re: I2C block reads with i2c-viapro: testers wanted
  2005-08-10 21:06   ` Jean Delvare
@ 2005-08-10 22:23     ` Martin Drab
  2005-08-11 17:12       ` Jean Delvare
  0 siblings, 1 reply; 3+ messages in thread
From: Martin Drab @ 2005-08-10 22:23 UTC (permalink / raw)
  To: Jean Delvare; +Cc: Hinko Kocevar, LKML, LM Sensors



On Wed, 10 Aug 2005, Jean Delvare wrote:

> Hi Hinko,
> 
> > > In order to verify whether I2C block reads work for you, just
> > > compare the contents of this file:
> > >   /sys/bus/i2c/devices/0-0050/eeprom
> > 
> > I've tested your patch on gericom X5 with VIA chipset and it works
> > fine without/with your patch (no diff in eeprom contents).
> > (...)
> > 0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8233 PCI to ISA Bridge
> 
> 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

Martin


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [lm-sensors] Re: I2C block reads with i2c-viapro: testers wanted
  2005-08-10 22:23     ` [lm-sensors] " Martin Drab
@ 2005-08-11 17:12       ` Jean Delvare
  0 siblings, 0 replies; 3+ messages in thread
From: Jean Delvare @ 2005-08-11 17:12 UTC (permalink / raw)
  To: Martin Drab; +Cc: LM Sensors, LKML

Hi Martin,

> > 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'd agree for VT8233 and VT8233A according to some searches I did this
morning. However, the VT8231 doesn't seem to fit in the list. Here are
the facts I am aware of that led me to this conclusion:

* It seems to appear only on specific boards, such as the Epia ones, and
is rarely mentioned on common hardware sites, compared to all the other
ones.

* It was presented by VIA at the Cebit in march 2002, which corresponds
to the release of the VT8233A.

* The support was added to the i2c-viapro driver in May 2002, that is,
after VT8233 (October 2001) and VT8233A (March 2002.)

* Its PCI ID is completely different (0x8231, while all other supported
devices are in the 0x3000-0x31FF range.)

So I think it doesn't exactly fit in the release timeline, and is more
likely a custom product derived from the VT82C686 (A or B) rather than a
linear evolution.

For this reason, I won't extrapolate the results to the VT8231. I will
only enable I2C block support for it if someone with such a chip agrees
to test the support first.

Thanks,
-- 
Jean Delvare

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [lm-sensors] Re: I2C block reads with i2c-viapro: testers wanted
@ 2005-08-11 18:30 Nick Warne
  0 siblings, 0 replies; 3+ messages in thread
From: Nick Warne @ 2005-08-11 18:30 UTC (permalink / raw)
  To: linux-kernel

>> 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..."

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2005-08-11 18:30 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-08-11 18:30 [lm-sensors] Re: I2C block reads with i2c-viapro: testers wanted Nick Warne
  -- strict thread matches above, loose matches on Subject: below --
2005-08-09 21:13 Jean Delvare
2005-08-10 20:31 ` Hinko Kocevar
2005-08-10 21:06   ` Jean Delvare
2005-08-10 22:23     ` [lm-sensors] " Martin Drab
2005-08-11 17:12       ` Jean Delvare

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox