All of lore.kernel.org
 help / color / mirror / Atom feed
From: r.marek@sh.cvut.cz (Rudolf Marek)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] HT-1000 smbus
Date: Tue, 14 Feb 2006 08:58:21 +0000	[thread overview]
Message-ID: <43F19BAD.3030601@sh.cvut.cz> (raw)
In-Reply-To: <43F105D6.7000500@cdi.cz>

Hi,

> 00:02.0 Host bridge: Broadcom HT1000 Legacy South Bridge
>          Subsystem: Broadcom: Unknown device 0201
>          Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
> ParErr- Stepping- SERR+ Fast B2B-
>          Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium 
>  >TAbort- <TAbort- <MAbort- >SERR - <PERR-
>          Latency: 64
> 
> -n will tell you that it IS 1166:0205.

Hmm subsytem ID is 201 maybe it will say that it is in fact CSB5?

> this is exactly what I did:
> piix4_smbus 0000:00:02.0: Found 0000:00:02.0 device
> piix4_smbus 0000:00:02.0: Unusual config register value
> piix4_smbus 0000:00:02.0: Try using fix_hstcfg=1 if you experience problems
> piix4_smbus 0000:00:02.0: Illegal Interrupt configuration (or code out 
> of date)!
> piix4_smbus 0000:00:02.0: SMBREV = 0x0
> piix4_smbus 0000:00:02.0: SMBA = 0x580
> 
> after using fix_hstcfg=1, machine freeze...
> If you will have again a long time (just interested, what faculty and 
> year, FEL ?) 

Yes diagnose is FEL. One week left ;)

>I will not leave the effort un-appreciated ;-)
> Going to dig into smbus.sys more for now.

Good. I must study for final exams...

If you find anything I can take a look.

regards
Rudolf


  parent reply	other threads:[~2006-02-14  8:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-13 22:19 [lm-sensors] HT-1000 smbus Martin Devera
2006-02-13 23:24 ` Rudolf Marek
2006-02-14  8:23 ` Martin Devera
2006-02-14  8:58 ` Rudolf Marek [this message]
2006-02-14 16:21 ` Martin Devera
2006-02-15 22:38 ` 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=43F19BAD.3030601@sh.cvut.cz \
    --to=r.marek@sh.cvut.cz \
    --cc=lm-sensors@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.