linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stian Jordet <liste@jordet.nu>
To: gene.heskett@verizon.net
Cc: Sebastian Kaps <seb-keyword-linux.637a6e@toyland.sauerland.de>,
	linux-kernel@vger.kernel.org
Subject: Re: sensors vs 2.6
Date: Tue, 09 Dec 2003 15:54:16 +0100	[thread overview]
Message-ID: <1070981656.26479.7.camel@chevrolet.hybel> (raw)
In-Reply-To: <200312090741.31290.gene.heskett@verizon.net>

tir, 09.12.2003 kl. 13.41 skrev Gene Heskett:
> I have this:
> -----------------------
> [root@coyote linux-2.6]# grep I2C .config
> # I2C support
> CONFIG_I2C=y
> CONFIG_I2C_CHARDEV=y
> # I2C Algorithms
> CONFIG_I2C_ALGOBIT=y
> # CONFIG_I2C_ALGOPCF is not set
> # I2C Hardware Bus support
> # CONFIG_I2C_ALI1535 is not set
> # CONFIG_I2C_ALI15X3 is not set
> # CONFIG_I2C_AMD756 is not set
> # CONFIG_I2C_AMD8111 is not set
> # CONFIG_I2C_I801 is not set
> # CONFIG_I2C_I810 is not set
> # CONFIG_I2C_NFORCE2 is not set
> # CONFIG_I2C_PHILIPSPAR is not set
> # CONFIG_I2C_PIIX4 is not set
> # CONFIG_I2C_PROSAVAGE is not set
> # CONFIG_I2C_SAVAGE4 is not set
> # CONFIG_I2C_SIS5595 is not set
> # CONFIG_I2C_SIS630 is not set
> # CONFIG_I2C_SIS96X is not set
> CONFIG_I2C_VIA=y
> CONFIG_I2C_VIAPRO=y
> # CONFIG_I2C_VOODOO3 is not set
> # I2C Hardware Sensors Chip support
> CONFIG_I2C_SENSOR=y

You seem to be missing support for a sensor chip.

Best regards,
Stian


  parent reply	other threads:[~2003-12-09 14:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-09  7:58 sensors vs 2.6 Gene Heskett
2003-12-09 10:33 ` Sebastian Kaps
2003-12-09 12:41   ` Gene Heskett
2003-12-09 14:18     ` Tomasz Torcz
2003-12-09 16:00       ` Gene Heskett
2003-12-09 14:54     ` Stian Jordet [this message]
2003-12-09 15:21       ` Gene Heskett
2003-12-09 15:32         ` Stian Jordet
2003-12-09 15:43 Matt

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=1070981656.26479.7.camel@chevrolet.hybel \
    --to=liste@jordet.nu \
    --cc=gene.heskett@verizon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seb-keyword-linux.637a6e@toyland.sauerland.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).