[od@fet.uni-hannover.de: Trying to find device chrontel 7009 ...]

[od@fet.uni-hannover.de: Trying to find device chrontel 7009 ...]

[Frodo Looijaard]

----- Forwarded message from Oliver Dawid <od@fet.uni-hannover.de> -----

From: Oliver Dawid <od@fet.uni-hannover.de>
To: frodol@dds.nl
Subject: Trying to find device chrontel 7009 ...
X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.20
X-Spam-Level: 

Hi Frodo,

I am writing to you, because I found your E-Mail adress in lm_sensors 
source for i2c-algo-bit.c

I have a Hermes 845GL with chrontel encoder for video output. Problem 
is: although I can set in Bios that it should produce PAL signal, I 
allways get NTSC. I already found register which has to be modified 
only problem is how to find the device.

I hoped that chrontel chip is connected to i2c controller of i845, 
which can be accessed through i810 driver (afaik - or there is another 
chip inside i did not find yet).

Unfortunatelly scan_bit=1 does not find any device only a couple of 
dots or ".S <7>0<7>needed 0 jiffies" id debug=9. I am not very familar 
to i2c code, so my digging in that code ended up in nothing.

Can you give me some hints how to find the device and how to adress? Is 
ther some docu I missed to read about i2c drivers for linux (or 
lm_sensors)?

Hope, you can help me,

thanks,
od

-- 
oliver dawid * od@fli4l.de * http://www.fli4l.de/

----- End forwarded message -----

-- 
Frodo Looijaard <frodol@dds.nl>  PGP key and more: http://huizen.dds.nl/~frodol
Defenestration n. (formal or joc.):
  The act of removing Windows from your computer in disgust, usually followed
  by the installation of Linux or some other Unix-like operating system.

[od@fet.uni-hannover.de: Trying to find device chrontel 7009

[Jean Delvare]

> I have a Hermes 845GL with chrontel encoder for video output. Problem 
> is: although I can set in Bios that it should produce PAL signal, I 
> allways get NTSC. I already found register which has to be modified 
> only problem is how to find the device.
> 
> I hoped that chrontel chip is connected to i2c controller of i845, 
> which can be accessed through i810 driver (afaik - or there is another
> 
> chip inside i did not find yet).
> 
> Unfortunatelly scan_bit=1 does not find any device only a couple of 
> dots or ".S <7>0<7>needed 0 jiffies" id debug=9. I am not very familar
> 
> to i2c code, so my digging in that code ended up in nothing.
> 
> Can you give me some hints how to find the device and how to adress?
> Is ther some docu I missed to read about i2c drivers for linux (or 
> lm_sensors)?

What you need to do is scan your i2c bus. Get the sensors-detect script
that comes with lm_sensors, and run it. It should tell you which devices
are available on your system. It will probably not identify your video
decode chip, because it's mainly aimed at sensor chips, but at least
it'll tell you at which address the chips were found (you can also use
i2cdetect to obtain the same information).

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

[od@fet.uni-hannover.de: Trying to find device chrontel 7009 ...]

[Oliver Dawid]

Hi Jean,

On 2003.10.14 22:24 Jean Delvare wrote:

> What you need to do is scan your i2c bus. Get the sensors-detect
> script
> that comes with lm_sensors, and run it. It should tell you which
> devices
> are available on your system. It will probably not identify your video
> decode chip, because it's mainly aimed at sensor chips, but at least
> it'll tell you at which address the chips were found (you can also use
> i2cdetect to obtain the same information).

Yeah, thanks. Thats the information i was looking for.

Regards,
od

[od@fet.uni-hannover.de: Trying to find device chrontel 7009 ...]

[Oliver Dawid]

Hi,

I have been on vacations, so today is the first time, I could try out what you 
sent to me.

On Tuesday 14 October 2003 22:24, you wrote:
> > I have a Hermes 845GL with chrontel encoder for video output. Problem
> > is: although I can set in Bios that it should produce PAL signal, I
> > allways get NTSC. I already found register which has to be modified
> > only problem is how to find the device.
> >
..
> What you need to do is scan your i2c bus. Get the sensors-detect script
> that comes with lm_sensors, and run it. It should tell you which devices
> are available on your system. It will probably not identify your video
> decode chip, because it's mainly aimed at sensor chips, but at least
> it'll tell you at which address the chips were found (you can also use
> i2cdetect to obtain the same information).

thanks a lot for your info. I used sensors-detect to find out, on which 
adresses i2c components are connected to my system.

There are some interesting news:
I can load i2c-i810 driver but only DDC (what's that?) can be initialized.
Your script detected a i2c-i801 which has some devices attached to
its bus.

Output of sensors-detect looks like this below. I kicked out all lines which 
failed. Can you please help me interpret this? Does this mean, that there are 
8 devices connected to this bus? 0x00, 0x08, 0x30, 0x44 and 0x69 are unknown 
so one of thouse can be my video codec? How can I identify which device it 
is? I have a paper about chrontel 7009 chip with all register adresses but it 
don't seem to contain something like an identifier.

Client found at address 0x00
Client found at address 0x08
Client found at address 0x2e
Probing for `National Semiconductor LM80'... Success!
    (confidence 3, driver `lm80')
Client found at address 0x2f
Probing for `National Semiconductor LM80'... Success!
    (confidence 3, driver `lm80')
Client found at address 0x30
Client found at address 0x44
Client found at address 0x50
Probing for `Serial EEPROM'... Success!
    (confidence 8, driver `eeprom')
Client found at address 0x69

Thanks,
od
-- 
od@fli4l.de * http://www.fli4l.de/ * the on(e) disk router

[od@fet.uni-hannover.de: Trying to find device chrontel 7009

[Jean Delvare]

> There are some interesting news:
> I can load i2c-i810 driver but only DDC (what's that?) can be
> initialized.

This is a protocol that allows one to retrieve a monitor's capabilities.
We have a module (ddcmon) that handles it rather well (if you have
lm_sensors 2.8.1) and a perl script that can convert this information
into something XFree86 can read in its configuration.

That said, I'm surprised. I'd have expected the Chrontel to be on that
(video) i2c bus, not on the other one.


> Your script detected a i2c-i801 which has some devices
> attached to its bus.
> 
> Output of sensors-detect looks like this below. I kicked out all lines
> which failed. Can you please help me interpret this? Does this mean,
> that there are 8 devices connected to this bus? 0x00, 0x08, 0x30, 0x44
> and 0x69 are unknown so one of thouse can be my video codec? How can I
> identify which device it is? I have a paper about chrontel 7009 chip
> with all register adresses but it don't seem to contain something like
> an identifier.
> 
> Client found at address 0x00

General call address. I don't know exactly how it works, but I can tell
for sure it's not a regular device.

> Client found at address 0x08

This address is called "SMB host" in my docs. Don't know what it means
either, but I'd guess it's not a regular device (and it's probably
linked with whatever appears at 0x00).

> Client found at address 0x2e
> Probing for `National Semiconductor LM80'... Success!
>     (confidence 3, driver `lm80')
> Client found at address 0x2f
> Probing for `National Semiconductor LM80'... Success!
>     (confidence 3, driver `lm80')

The LM80 is hard to detect, so it might not be LM80's. Load lm80, run
sensors (and sensors -s before that) and see if the values make sense.

> Client found at address 0x30

A shadow image of the EEPROM at 0x50, which you can safely ignore.

> Client found at address 0x44

Might be what you're after.

> Client found at address 0x50
> Probing for `Serial EEPROM'... Success!
>     (confidence 8, driver `eeprom')

EEPROM as found on your first memory module.

> Client found at address 0x69

Clock device, dangerous and uninteresting playing with. Forget about it.

Use i2cdump on the unknown address, this will help us identify the chip
there:
i2cdump 1 0x44 b
(assuming the i2c-i801 has bus id 1). You can also try the same on 0x2e
and 0x2f if the lm80 module did not give good results.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

[od@fet.uni-hannover.de: Trying to find device chrontel 7009 ...]

[Oliver Dawid]

Hi Jean,

On Tuesday 04 November 2003 22:59, you wrote:

> > Client found at address 0x2e
> > Probing for `National Semiconductor LM80'... Success!
> >     (confidence 3, driver `lm80')
> > Client found at address 0x2f
> > Probing for `National Semiconductor LM80'... Success!
> >     (confidence 3, driver `lm80')
>
> The LM80 is hard to detect, so it might not be LM80's. Load lm80, run
> sensors (and sensors -s before that) and see if the values make sense.

sensors output:
flex scanner jammed

I have lm_sensors 2.7.0. I downloaded 2.8.1 but got this problem while 
compiling:
In file included from /lib/modules/2.4.20/build/include/asm/semaphore.h:39,
                 from /lib/modules/2.4.20/build/include/linux/fs.h:200,
                 from /lib/modules/2.4.20/build/include/linux/capability.h:17,
                 from /lib/modules/2.4.20/build/include/linux/binfmts.h:5,
                 from /lib/modules/2.4.20/build/include/linux/sched.h:9,
                 from /lib/modules/2.4.20/build/include/linux/mm.h:4,
                 from /lib/modules/2.4.20/build/include/linux/slab.h:14,
                 from /lib/modules/2.4.20/build/include/asm/pci.h:32,
                 from /lib/modules/2.4.20/build/include/linux/pci.h:622,
                 from kernel/busses/i2c-nforce2.c:35:
/lib/modules/2.4.20/build/include/asm/system.h: In function `__set_64bit_var':
/lib/modules/2.4.20/build/include/asm/system.h:190: warning: dereferencing 
type-punned pointer will break strict-aliasing rules
/lib/modules/2.4.20/build/include/asm/system.h:190: warning: dereferencing 
type-punned pointer will break strict-aliasing rules
kernel/busses/i2c-nforce2.c: In function `nforce2_access':
kernel/busses/i2c-nforce2.c:242: warning: implicit declaration of function 
`i2c_delay'
kernel/busses/i2c-nforce2.c: In function `nforce2_probe_smb':
kernel/busses/i2c-nforce2.c:317: error: structure has no member named `owner'
kernel/busses/i2c-nforce2.c:320: error: `I2C_HW_SMBUS_NFORCE2' undeclared 
(first use in this function)
kernel/busses/i2c-nforce2.c:320: error: (Each undeclared identifier is 
reported only once
kernel/busses/i2c-nforce2.c:320: error: for each function it appears in.)
make: *** [kernel/busses/i2c-nforce2.o] Error 1

Seems that you depend on different kernel header than 2.4.20?

> > Client found at address 0x44
>
> Might be what you're after.

i2cdump 1 0x44 b
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 00 00 0f 04 00 00 00 00 00 00 00 00 00 00 00 00    ..??............

i2cdump 1 0x2e b
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 01 3f 80 20 5d 5d c7 00 5a 00 1e 21 00 00 00 00    ??? ]]?.Z.?!....
10: ff ff 5d 5d 3c 00 46 5d 50 00 64 5d 50 00 64 5d    ..]]<.F]P.d]P.d]
20: 5d 5d 00 d1 41 33 61 5d 5d 5d 5d 5d 5d 5d 5d 5d    ]].?A3a]]]]]]]]]
30: 5d 5d 5d 5d 5d 5d 5d 5d 5d 5d 5d 5d 5d 30 41 83    ]]]]]]]]]]]]]0A?
40: 01 3f 00 20 5d 5d c7 00 5a 00 1e 21 00 00 00 00    ??. ]]?.Z.?!....
50: ff ff 5d 5d 3c 00 46 5d 50 00 64 5d 50 00 64 5d    ..]]<.F]P.d]P.d]
60: 5d 5d 00 d1 41 33 61 5d 5d 5d 5d 5d 5d 5d 5d 5d    ]].?A3a]]]]]]]]]
70: 5d 5d 5d 5d 5d 5d 5d 5d 5d 5d 5d 5d 5d 30 41 83    ]]]]]]]]]]]]]0A?
80: 01 3f 00 20 5d 5d c7 00 5a 00 1e 21 00 00 00 00    ??. ]]?.Z.?!....
90: ff ff 5d 5d 3c 00 46 5d 50 00 64 5d 50 00 64 5d    ..]]<.F]P.d]P.d]
a0: 5d 5d 00 d1 41 33 61 5d 5d 5d 5d 5d 5d 5d 5d 5d    ]].?A3a]]]]]]]]]
b0: 5d 5d 5d 5d 5d 5d 5d 5d 5d 5d 5d 5d 5d 30 41 83    ]]]]]]]]]]]]]0A?
c0: 01 3f 00 20 5d 5d 07 00 5a 00 1f 21 00 00 00 00    ??. ]]?.Z.?!....
d0: ff ff 5d 5d 3c 00 46 5d 50 00 64 5d 50 00 64 5d    ..]]<.F]P.d]P.d]
e0: 5d 5d 00 d1 41 33 61 5d 5d 5d 5d 5d 5d 5d 5d 5d    ]].?A3a]]]]]]]]]
f0: 5d 5d 5d 5d 5d 5d 5d 5d 5d 5d 5d 5d 5d 30 41 83    ]]]]]]]]]]]]]0A?

i2cdump 1 0x2f b
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 01 ff 0f 00 00 ff 0f 00 00 ff 06 00 00 07 85 00    ?.?...?...?..??.
10: c0 11 00 60 ff ff ff ff ff ff ff ff ff ff ff ff    ??.`............

Seems like you are right and only one of 0x2e and 0x2f is a real lm80. Can you 
tell me from dump which one it probably is? Hopefully its 0x2f because 
chrontel 7009 has tons of registers and it better fits to 0x2e ' s dump.

maybe none of these devices is my chrontel so i will have to search on.

Regards,
od

-- 
od@fli4l.de * http://www.fli4l.de/ * the on(e) disk router