Sorry for bothering you again :-))
 
I still have the problem described below, but are already some steps further...
 
I installed a Fedora 9 on this hardware and also the lm_sensors packet.
lm_sensors finds the following:
 
sensors-detect:
...
Next adapter: SMBus I801 adapter at 18e0 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x2e
...
Probing for `SMSC DME1737'...                               Success!
    (confidence 6, driver `dme1737')
...
 
sensors output:
dme1737-i2c-0-2e
Adapter: SMBus I801 adapter at 18e0
V5stby:      +1.84 V  (min =  +0.00 V, max =  +6.64 V)
Vccp:        +0.95 V  (min =  +0.00 V, max =  +2.99 V)
V3.3:        +3.39 V  (min =  +0.00 V, max =  +4.38 V)
V5:          +5.03 V  (min =  +0.00 V, max =  +6.64 V)
V12:        +12.12 V  (min =  +0.00 V, max = +15.94 V)
V3.3stby:    +3.39 V  (min =  +0.00 V, max =  +4.38 V)
Vbat:        +3.40 V  (min =  +0.00 V, max =  +4.38 V)
CPU_Fan:    1738 RPM  (min =  500 RPM)
Fan2:          0 RPM  (min =    0 RPM)
Fan3:       4202 RPM  (min =  500 RPM)
Fan4:       1502 RPM  (min =  500 RPM)
RD1 Temp:    +33.9°C  (low  =  +0.0°C, high = +100.0°C)
Int Temp:    +33.4°C  (low  =  +0.0°C, high = +80.0°C)
CPU Temp:    +35.1°C  (low  =  +0.0°C, high = +80.0°C)
cpu0_vid:   +1.600 V

all right, so my motherboard seems to have a DME1737 on I2C-bus.
 
what I did next was installing "lspci" on Solaris 10x86.
 
output of lspci is:
bash-3.00# pciutils-3.0.0/lspci -xvv -d 8086:27da
00:1f.3 Class 0c05: Device 8086:27da (rev 01)
        Subsystem: Device 8086:1999
        Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Interrupt: pin ? routed to IRQ 255
        Region 4: I/O ports at 18e0
00: 86 80 da 27 01 00 80 02 01 00 05 0c 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: e1 18 00 00 00 00 00 00 00 00 00 00 86 80 99 19
30: 00 00 00 00 00 00 00 00 00 00 00 00 ff 00 00 00
 
device 8086:27da is the only one pointing to sensors.... (at least "prtconv -v" 
tells for that address that it's
an SMBus)
 
so.... I'm now assuming that I need to configure a pci-device for my sensor 
(connected to I2C), am I right?
and if so... again the question... what should be the settings for "reg" within 
my driver.conf ??
 
thanks a lot for helping a newbie !
christian
 
 

--
"I sense much NT in you, NT leads to Blue Screen.
Blue Screen leads to downtime, downtime leads to suffering. NT is the path to 
the darkside."

- Unknown Unix Jedi 

 


________________________________

        From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of 
Masopust, Christian
        Sent: Monday, August 18, 2008 1:33 PM
        To: [email protected]
        Subject: [driver-discuss] Trying to create driver for accessing SMBus 
of anIntel 82801G
        
        
        Dear all,
         
        first of all I'd like to say that I'm very new to driver development in 
Solaris X86....
         
        What I like to do is accessing the "sensors" of my motherboard which 
has an
        Intel-Chipset (ICH7).
         
        I already know about ddi_... have read the "device driver tutorial" and 
also searched
        the driver-discuss archive.
         
        What I'm currently needing is how to find out the correct settings of 
"reg" within
        my driver.conf, I know the address of the SMBus is 0x3fe (on my 
motherboard)
        but I don't know about the size (according to "man isa")...
         
        any help?  any hint where to search?  or even better... any driver 
already there? :-))
         
        christian
         

        

        --
        "I sense much NT in you, NT leads to Blue Screen.
        Blue Screen leads to downtime, downtime leads to suffering. NT is the 
path to the darkside."
        
        - Unknown Unix Jedi 

        

        

_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss

Reply via email to