On Fri, Dec 29, 2000 at 02:26:39PM -0500, Andrew Gallatin wrote:
>
> I know what chips they are (From the UP1000 Tech. Ref. Manual):
>
> The UP1000 has one main SM bus and two sub-SM busses. Acces to the
> sub-SM bus is controlled by a multiplexer (MUX) which sits on the main
> SM bus.
Nicolas Souchu writes:
> > If I beat on lm.c from
> > http://www.planet.sci.kobe-u.ac.jp/~takawata/smbus/examples/lm.c
> > enough and use 0x90 as cmd.slave, I can get the CPU temp of 41 C.
> > This is the same as firmware gives me, which is encouraging.
> >
> > As you can probably tell, I
> Grab the linux lm_sensor documentation and see if these I2C addresses
> are listed and which chips they are potentially assigned to. At this
> point, it is not SMBus dependent, but chip/vendor dependent.
FWIW, Ralf Brown's interrupt list contains a fairly extensive set of I2C
address assignmen
On Thu, Dec 28, 2000 at 02:57:33PM -0500, Andrew Gallatin wrote:
>
> Nicolas Souchu writes:
> > Gasp! This is part of my fault. I shouldn't have left this old style
> > driver in the tree :( You should have contacted me, I would have adviced
> > you.
> >
> > Takanori is right, you should lo
Nicolas Souchu writes:
> Gasp! This is part of my fault. I shouldn't have left this old style
> driver in the tree :( You should have contacted me, I would have adviced
> you.
>
> Takanori is right, you should look at intpm to get info about how
> to cleanly newbusify your driver. This is
Gasp! This is part of my fault. I shouldn't have left this old style
driver in the tree :( You should have contacted me, I would have adviced
you.
Takanori is right, you should look at intpm to get info about how
to cleanly newbusify your driver. This is what I'm currently doing
for alpm ;)
By t
In message <[EMAIL PROTECTED]>, "M
atthew C. Forman" さんいわく:
>
>First, sorry this is a bit long; I probably should have split it up, but
>when I get going... Y'Know...
>
>I've done some work on a driver for the SMBus functions of the AMD 756
>chip found on K7-based motherboards, based on
>
> First, sorry this is a bit long; I probably should have split it up, but
> when I get going... Y'Know...
Size is not a problem.
> My newbus efforts are not going too well; specifically I'm having a hard
> time with bus_alloc_resource, which refuses to allocate any I/O space for
> me. I've t
First, sorry this is a bit long; I probably should have split it up, but
when I get going... Y'Know...
I've done some work on a driver for the SMBus functions of the AMD 756
chip found on K7-based motherboards, based on alpm.c from -CURRENT. This
works nicely on my system (Gigabyte GA7IXE-4 with
9 matches
Mail list logo
