* True SMBus host support for VIA southbridges
Supports PCI devices:
1106:3050 VT82C596 "Via Apollo Pro / Pro+"
1106:3057 VT82C686 "Via Apollo MVP4"
I have no hardware to test these..
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@498 7894878c-1315-0410-8ee3-d5d059ff63e0
* Fixed adapter drivers to compile with the new i2c structs.
They might, or they might not work..
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@497 7894878c-1315-0410-8ee3-d5d059ff63e0
* The i2c package can no longer be compiled as part of the lm_sensors tree
* The archive of the i2c package is removed
* smbus, i2c-dev and i2c-proc modules and headers have been removed; they
are now completely integrated into the i2c package
* The fake i2c.h header has been removed; this also allowed us to remove
the ugly LM_SENSORS and TBD defines.
* A new variable I2C_HEADERS is introduced in the Makefile. This allows
us to install the i2c headers in, for example, /usr/local/include/linux.
* All files now include <linux/i2c.h> instead of "i2c.h" and "smbus.h"
Status: 'make dep' works, all the right include files are found. 'make all'
does not yet work.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@496 7894878c-1315-0410-8ee3-d5d059ff63e0
Never put a semicolon after an if :-(
I have a SiS5595 here, which reports his chip monitor address as 0x0000.
Strange thing...
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@493 7894878c-1315-0410-8ee3-d5d059ff63e0
in the root dir of the CVS archive. (a complete backup was made before
doing this, of course ;')
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@489 7894878c-1315-0410-8ee3-d5d059ff63e0
the results to the display. Only the first four lines are read, and only
the first 20 chars of each line are displayed.
Example use:
echo -e "hi\nthere,\nhow are\nyou?" | displayit.pl
Displays this on the display:
hi
there,
how are
you?
It doesn't get much simpler than this!
TODO: The code isn't very efficient and goes slow for what it is doing.
It assumes that the display is 20x4 (easily changable). And, it assumes
that there is only one display. This is really more of a simple example
than a feature-rich app.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@483 7894878c-1315-0410-8ee3-d5d059ff63e0
There is only one file 'disp'. To send bytes (like chars to be displayed)
you send a series of unsigned base-10 values separated by spaces.
For example:
echo "hi there" | perl -e \
'$_=<STDIN>; while (/(.)/gc) { print ord($1)," "; }' \
> /proc/sys/dev/sensors/matorb*/disp
This is equivelent to doing:
echo "104 105 32 116 104 101 114 101" > /proc/sys/dev/sensors/matorb*/disp
I was going to create more files for doing things like clearing the screen,
but it is easier and probably better to do this in user-space. For example,
to clean the screen, you can do:
echo "254 88" > /proc/sys/dev/sensors/matorb*/disp
(As documented in the manual from Matrix-Orbital)
If the folks at Matrix-Orbital added device ID on a read (we talked about
this), then I will add an ID file to indicate that info.
TODO: finish detection. Right now it looks for a device at a particular
address and assumes it is a display.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@482 7894878c-1315-0410-8ee3-d5d059ff63e0
The HW still generates the alarm, but the output is masked. The mask comes
useful also once I start fine-tuning that iteration code for reading all 4
voltages.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@478 7894878c-1315-0410-8ee3-d5d059ff63e0
* Made i2c-voodoo3.c compile with 2.0 kernels
It should also run without problem, but obviously I could not test it
Changes are in the memory mapping of PCI address space
* Removed several warning from i2c-voodoo3.c
It compiles now without any warnings, even with WARN=1
* Removed several warnings from matorb.c
It compiles now without any warnings, even with WARN=1
In the proces, I fixed one serious bug (assignment instead of comparison)
* Removed a warning from w83781d.c
It compiles now without any warnings, even with WARN=1
Hint: Once in a while, try to compile with WARN=1 and remove warnings. It
helps to find serious, hidden problems. Really!
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@472 7894878c-1315-0410-8ee3-d5d059ff63e0
is right now, it should clear the LCD screen. But, I discovered that
the display simply can't cope with I2C read commands - it completely
locks up *both* the data and the *clock* lines! (That's new.) So,
it kills the bus when probes or other reads are done to the device.
Matrix-Orbital has to fix this before we can get anything
usable working. :'(
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@464 7894878c-1315-0410-8ee3-d5d059ff63e0
need these 'special' modelines for XF86Config:
ModeLine "640x480NTSC" 28.195793 640 656 658 784 480 520 525 600
ModeLine "800x600NTSC" 38.769241 800 812 814 880 600 646 649 735
My monitor really doesn't like these modes, but they seem to work well
for TV output. Oh, and this is only for a screen depth of 16bits
right now.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@459 7894878c-1315-0410-8ee3-d5d059ff63e0
bad like 'oops' when there is more than one voodoo3 in the system or when
there is none.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@456 7894878c-1315-0410-8ee3-d5d059ff63e0
during a transaction. It also can detect a 'hung' bus prior to starting
a transaction. It seems to properly read and write to the BT869.
Todo: support for multiple voodoo3 cards. Support for other transaction
types (fairly simple). Use code as a start for a better algo-bit
adapter template? Complete the bt869 driver.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@452 7894878c-1315-0410-8ee3-d5d059ff63e0
Voodoo3 I2C notes (or short commings):
* only one type of read supported: type 'byte' (no 'command')
* only one type of write supported: type 'byte_data'
(The two above are more the limitation of the BT869 rather than
the I2C bus.)
* I used the SMBus 'model' rather than the 'bit' model because
I thought it was easier this way.
* failed bus transactions yeild 0xFF, not an error! So, this means
that many drivers instantly latch onto this adapter because all
reads and writes succeed without error. Without the datasheet for
the chip, I can't do much to fix this. (Amazing I got this far!)
BT869/868 notes:
* the BT869 has lots and lots of registers (~50), but can
only read 3 (fairly uninteresting) status registers(!). Right
now all three status registers are read through the 'status' file,
but I haven't decided on the best method for writing to the rest
of the registers.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@448 7894878c-1315-0410-8ee3-d5d059ff63e0
