All of lore.kernel.org
 help / color / mirror / Atom feed
From: decibel8@charter.net (David)
To: lm-sensors@vger.kernel.org
Subject: 1250
Date: Thu, 19 May 2005 06:24:02 +0000	[thread overview]
Message-ID: <200306251314.51483.decibel8@charter.net> (raw)
In-Reply-To: <200306021011.37032.decibel8@charter.net>




> This would make sense. David, correct me if I'm wrong, but I believe
> that you can actually write to the files (simply using "cat 1 2 >
> /proc/sys/dev/sensors/via686a-isa-6000/in1" for example). So, if
> "sensors -s" fails, this must be because of libsensors *thinking* it
> cannot write.
Actually no. Not using cat. I get this error if do that:

bash-2.05b# cat 1 2 > /proc/sys/dev/sensors/via686a-isa-6000/in1
cat: 1: No such file or directory
cat: 2: No such file or directory

I can though 'echo' to it:





Previous message:
On Wednesday 25 June 2003 08:52 am, you wrote:
> > I don't have my lm_sensors source handy right now, but I wanted to
> > reply so perhaps you or someone else could look into this...
> >
> > I notice that the adapter is registered at address 6000.  That's a bit
> > of a strange isa address.  I believe that the original ISA bus only
> > has I/O addresses up to 3fff.  Anything above that is either an alias
> > or a PCI bus address.
> >
> > Perhaps there is a test in the ISA write function that makes sure the
> > address you're attempting to write is in the range: 0-3fff or less and
> > if not, returns an error.
>
> This would make sense. David, correct me if I'm wrong, but I believe
> that you can actually write to the files (simply using "cat 1 2 >
> /proc/sys/dev/sensors/via686a-isa-6000/in1" for example). So, if
> "sensors -s" fails, this must be because of libsensors *thinking* it
> cannot write.
>
> David, maybe we already asked you and I'm sorry for that, but I can't
> remember (it's been so long):
>
> 1* Are you using i2c & lm_sensors 2.7.0 or CVS?
>
> 2* Are you using the mkpatch method or the traditional separated
> compilation tree method?
>
> Thanks.

  parent reply	other threads:[~2005-05-19  6:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:23 1250 David
2005-05-19  6:23 ` 1250 Mark D. Studebaker 
2005-05-19  6:23 ` 1250 Philip Pokorny
2005-05-19  6:23 ` 1250 Philip Pokorny
2005-05-19  6:23 ` 1250 Philip Pokorny
2005-05-19  6:24 ` 1250 Jean Delvare
2005-05-19  6:24 ` 1250 David
2005-05-19  6:24 ` 1250 David
2005-05-19  6:24 ` 1250 Jean Delvare
2005-05-19  6:24 ` 1250 Philip Pokorny
2005-05-19  6:24 ` 1250 DAVID
2005-05-19  6:24 ` 1250 Philip Pokorny
2005-05-19  6:24 ` 1250 Jean Delvare
2005-05-19  6:24 ` 1250 Philip Pokorny
2005-05-19  6:24 ` 1250 David
2005-05-19  6:24 ` 1250 David
2005-05-19  6:24 ` 1250 Jean Delvare
2005-05-19  6:24 ` David [this message]
2005-05-19  6:24 ` 1250 Jean Delvare
2005-05-19  6:24 ` 1250 David
2005-05-19  6:24 ` 1250 Jean Delvare
2005-05-19  6:24 ` 1250 David
2005-05-19  6:24 ` 1250 David

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=200306251314.51483.decibel8@charter.net \
    --to=decibel8@charter.net \
    --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.