public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Flameeyes <daps_mls@libero.it>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test2, sensors and sysfs
Date: 31 Jul 2003 20:02:26 +0200	[thread overview]
Message-ID: <1059674546.1173.14.camel@laurelin> (raw)
In-Reply-To: <20030731211732.5591495d.vsu@altlinux.ru>

On Thu, 2003-07-31 at 19:17, Sergey Vlasov wrote:
> (Not sure if replying via news.gmane.org will work...)
> 
> Currently (2.6.0-test2) i2c-viapro and via686a don't work together -
> you can use only one of them. This is because they want to work with
> the same PCI device - and having multiple drivers for one device is
> not allowed for obvious reasons.
> 
> This issue is already known to the lm_sensors developers.
> 
> So you will need to remove i2c-viapro for now (but leave i2c-isa);
> then you will see the via686a sensors again.

In this way, I can access all the data of the via686a sensors from the
sysfs without problems (yes, I need a compatible userland, but this
isn't a problem... i can wrote some myself).
I haven't found information about this problem in the post halloween or
in other 2.5 documents, I think is an important thing to know, via686a
chipsets are quite used, AFAIK.

-- 
Flameeyes <dgp85@users.sf.net>


  parent reply	other threads:[~2003-07-31 18:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-31 16:36 2.6.0-test2, sensors and sysfs Flameeyes
2003-07-31 16:50 ` Greg KH
2003-07-31 17:01   ` Flameeyes
2003-07-31 17:36     ` Greg KH
2003-07-31 16:52 ` Sergey Vlasov
     [not found] ` <20030731211732.5591495d.vsu@altlinux.ru>
2003-07-31 18:02   ` Flameeyes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-31 17:21 Tomasz Torcz
2003-07-31 17:34 ` Greg KH

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=1059674546.1173.14.camel@laurelin \
    --to=daps_mls@libero.it \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox