Re: Aladdin chipset SMBus support available!
On Tue, 16 Feb 1999, Warner Losh wrote: > : Not to stop you in your tracks, but I would really love to see > : somebody (more capable than the PAO people) work out a power > : management architecture for us before we have too many more > : hacks in this area... > > I'd have to agree that a unified power management architecture would > be a good thing. There is also the new APCI to consider as well. > > Warner And hot-docking/undocking with PnP reprobing of new devices... Ouch, stop hitting me. -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Aladdin chipset SMBus support available!
: Not to stop you in your tracks, but I would really love to see : somebody (more capable than the PAO people) work out a power : management architecture for us before we have too many more : hacks in this area... I'd have to agree that a unified power management architecture would be a good thing. There is also the new APCI to consider as well. Warner To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Aladdin chipset SMBus support available!
On Sun, Feb 14, 1999 at 07:41:25PM -0500, Brian Feldman wrote: > >On Sun, 14 Feb 1999, Nicolas Souchu wrote: > >> On Sun, Feb 14, 1999 at 04:30:27PM -0500, Brian Feldman wrote: >> >> >> > >> >On spd I would get an error message, and if I ever did spd 1 it got as far >> >as printing 128 bytes used, then erred out... >> > >> >> rm alpm.o ; make CC="cc -DDEBUG" >> > >> >I'll rm alpm.o; CC='cc -DDEBUG' make alpm.o; make, if that's what you mean. >> >> any difference? > >Yes: >Feb 14 17:12:16 green /kernel: alpm: idle? STS=0x0 >Feb 14 17:12:48 green last message repeated 380 times >Feb 14 17:13:14 green last message repeated 5 times > The controller seems to stick on the bus. The Linux team has reported such problems with there own driver and couldn't do anything (reset of controller, SMBus abort...). The problem seem to have disappeared with an additional device plugged on the bus. I'll dig into your problem, but yet, I have no problem with the ASUS. I'll browse the datasheets.. > >> >> -- >> nso...@teaser.fr / nso...@freebsd.org >> FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org >> >> To Unsubscribe: send mail to majord...@freebsd.org >> with "unsubscribe freebsd-current" in the body of the message >> > > Brian Feldman _ __ ___ ___ ___ > gr...@unixhelp.org _ __ ___ | _ ) __| \ >http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | > FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ > > -- nso...@teaser.fr / nso...@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Aladdin chipset SMBus support available!
On Sun, Feb 14, 1999 at 11:09:45PM +0100, Nicolas Souchu wrote: > >On Sun, Feb 14, 1999 at 04:30:27PM -0500, Brian Feldman wrote: >>> >> >>On spd I would get an error message, and if I ever did spd 1 it got as far >>as printing 128 bytes used, then erred out... >> >>> rm alpm.o ; make CC="cc -DDEBUG" >> >>I'll rm alpm.o; CC='cc -DDEBUG' make alpm.o; make, if that's what you mean. > >any difference? I meant any difference between the two command lines? -- nso...@teaser.fr / nso...@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Aladdin chipset SMBus support available!
On Sun, 14 Feb 1999, Nicolas Souchu wrote: > On Sun, Feb 14, 1999 at 04:30:27PM -0500, Brian Feldman wrote: > >> > > > >On spd I would get an error message, and if I ever did spd 1 it got as far > >as printing 128 bytes used, then erred out... > > > >> rm alpm.o ; make CC="cc -DDEBUG" > > > >I'll rm alpm.o; CC='cc -DDEBUG' make alpm.o; make, if that's what you mean. > > any difference? Yes: Feb 14 17:12:16 green /kernel: alpm: idle? STS=0x0 Feb 14 17:12:48 green last message repeated 380 times Feb 14 17:13:14 green last message repeated 5 times > > -- > nso...@teaser.fr / nso...@freebsd.org > FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Aladdin chipset SMBus support available!
On Sun, 14 Feb 1999, Brian Feldman wrote: > Sorta. It did work. Then it stopped working. Running detect seems to kill my > SM (or at least reset it to some weird state) Ahh yes, I'm not alone. Running detect here came up with four ports (5a, 60, 9a, a0 I think). It also caused anything else trying to access smb0 to get a device busy error. Rebooting actually hung the machine before the BIOS graphic was displayed... the lovely soft power switch wasn't working.. holding reset down for about a minute seemed to fix this. Also, the lm program (from your battery of examples) crashes with a SIGFPE, but some stuff from Nat'l Semi (some Win95 stuff anyways) seems to work.. but I'm not sure if anything is really hooked up, other than the SPD stuff. intpm0: rev 0x02 on pci0.7.3 intpm0: I/O mapped 7000 ALLOCED IRQ 0 intr IRQ 9 enabled revision 0 intsmb0: smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped 8000 - alex To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Aladdin chipset SMBus support available!
On Sun, Feb 14, 1999 at 04:30:27PM -0500, Brian Feldman wrote: >> > >On spd I would get an error message, and if I ever did spd 1 it got as far >as printing 128 bytes used, then erred out... > >> rm alpm.o ; make CC="cc -DDEBUG" > >I'll rm alpm.o; CC='cc -DDEBUG' make alpm.o; make, if that's what you mean. any difference? -- nso...@teaser.fr / nso...@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Aladdin chipset SMBus support available!
On Sun, 14 Feb 1999, Nicolas Souchu wrote:
> On Sun, Feb 14, 1999 at 01:01:27PM -0500, Brian Feldman wrote:
> [...]
> >
> >Sorta. It did work. Then it stopped working. Running detect seems to kill my
> >SM (or at least reset it to some weird state)
> >
> >{"/home/green/examples"}$ ./detect
> >{"/home/green/examples"}$
>
> You mean you got some output from spd? Which? Try recompiling alpm.o with
> DEBUG defined.
>
On spd I would get an error message, and if I ever did spd 1 it got as far
as printing 128 bytes used, then erred out...
> rm alpm.o ; make CC="cc -DDEBUG"
I'll rm alpm.o; CC='cc -DDEBUG' make alpm.o; make, if that's what you mean.
>
> --
> nso...@teaser.fr / nso...@freebsd.org
> FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org
>
Brian Feldman_ __ ___ ___ ___
gr...@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: Aladdin chipset SMBus support available!
On Mon, Feb 15, 1999 at 03:55:07AM +0900, takaw...@shidahara1.planet.sci.kobe-u.ac.jp wrote: > >>d2 found. > >I want to know about this address. SMBus in my motherboard will hang >up when I issue RECV_BYTE method for this port. It does not for me. It's supposed to be the address of a clock chip, isn't it? > >>> BTW, as outlined by -pkh all this is just a first step in a huge monitoring >>> adventure where all still need to be _defined_ (architecture and interfaces) >>> and implemented. Any proposition for doing the job is wellcome, >>> since I just have enough time to do the hardware SMBus support. >> >>Sounds like fun > >I think so too. >/dev/smb? should not be used in casual use,because it is dangerous,as >banging I/O port.I want to discuss about the interface. Where did he >wrote it? He wrote nothing, just: >>> Not to stop you in your tracks, but I would really love to see somebody (more capable than the PAO people) work out a power management architecture for us before we have too many more hacks in this area... Poul-Henning In message <199902131808.kaa79...@freefall.freebsd.org>, Nicolas Souchu writes: >nsouch 1999/02/13 10:08:35 PST > > Modified files: >share/man/man4 intpm.4 > Log: > Fix the date and add an smbus declaration > > Revision ChangesPath > 1.2 +3 -2 src/share/man/man4/intpm.4 > <<< -- nso...@teaser.fr / nso...@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Aladdin chipset SMBus support available!
On Sun, Feb 14, 1999 at 01:01:27PM -0500, Brian Feldman wrote:
[...]
>
>Sorta. It did work. Then it stopped working. Running detect seems to kill my
>SM (or at least reset it to some weird state)
>
>{"/home/green/examples"}$ ./detect
>{"/home/green/examples"}$
You mean you got some output from spd? Which? Try recompiling alpm.o with
DEBUG defined.
rm alpm.o ; make CC="cc -DDEBUG"
--
nso...@teaser.fr / nso...@freebsd.org
FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: Aladdin chipset SMBus support available!
In message , Brian
Feldman wrote:
>> >> I attach you the detect.c program. It's very simple and may help us
>> >> in knowing what I2C hardware you have on your mobo.
>> >
>> >Where's my detect.c? I think you forgot to attach it :)
>>
>> :) here it is!
>
>alpm0: rev 0x00 on pci0.3.0
>alsmb0:
>smbus0: on alsmb0
>smb0: on smbus0
>
>{"/home/green/examples"}$ ./detect
>a2 found.
This is DIMM(with SPD).
#./spd 1
will show your DIMM infomation.
>d2 found.
I want to know about this address. SMBus in my motherboard will hang
up when I issue RECV_BYTE method for this port.
>> BTW, as outlined by -pkh all this is just a first step in a huge monitoring
>> adventure where all still need to be _defined_ (architecture and interfaces)
>> and implemented. Any proposition for doing the job is wellcome,
>> since I just have enough time to do the hardware SMBus support.
>
>Sounds like fun
I think so too.
/dev/smb? should not be used in casual use,because it is dangerous,as
banging I/O port.I want to discuss about the interface. Where did he
wrote it?
Takanori Watanabe
http://www.planet.kobe-u.ac.jp/~takawata/key.html";>
Public Key
Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: Aladdin chipset SMBus support available!
On Sun, 14 Feb 1999, Nicolas Souchu wrote:
> On Sun, Feb 14, 1999 at 12:11:09PM -0500, Brian Feldman wrote:
> >
> >On Sun, 14 Feb 1999, Nicolas Souchu wrote:
> >
> >> On Sun, Feb 14, 1999 at 08:40:11AM -0500, Brian Feldman wrote:
> >> >
> >> >On Sun, 14 Feb 1999, Nicolas Souchu wrote:
> >> >
> >> >> On Sat, Feb 13, 1999 at 05:22:00PM -0500, Brian Feldman wrote:
> >> >> >
> >> >> >On Sat, 13 Feb 1999, Nicolas Souchu wrote:
> >> >> >
> >> >> >> Example program to fetch temperature or voltages is available at
> >> >> >> http://www.planet.sci.kobe-u.ac.jp/~takawata/smbus/examples/
> >> >> >> There's also an example program to fetch SDRAM info over the smbus.
> >> >>
> >> >> I attach you the detect.c program. It's very simple and may help us
> >> >> in knowing what I2C hardware you have on your mobo.
> >> >
> >> >Where's my detect.c? I think you forgot to attach it :)
> >>
> >> :) here it is!
> >
> >alpm0: rev 0x00 on pci0.3.0
> >alsmb0:
> >smbus0: on alsmb0
> >smb0: on smbus0
> >
> >{"/home/green/examples"}$ ./detect
> >a2 found.
> >d2 found.
>
> So,
>
> ./spd 1
>
> will work!
Sorta. It did work. Then it stopped working. Running detect seems to kill my
SM (or at least reset it to some weird state)
{"/home/green/examples"}$ ./detect
{"/home/green/examples"}$
>
> --
> nso...@teaser.fr / nso...@freebsd.org
> FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org
>
Brian Feldman_ __ ___ ___ ___
gr...@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: Aladdin chipset SMBus support available!
On Sun, Feb 14, 1999 at 12:11:09PM -0500, Brian Feldman wrote:
>
>On Sun, 14 Feb 1999, Nicolas Souchu wrote:
>
>> On Sun, Feb 14, 1999 at 08:40:11AM -0500, Brian Feldman wrote:
>> >
>> >On Sun, 14 Feb 1999, Nicolas Souchu wrote:
>> >
>> >> On Sat, Feb 13, 1999 at 05:22:00PM -0500, Brian Feldman wrote:
>> >> >
>> >> >On Sat, 13 Feb 1999, Nicolas Souchu wrote:
>> >> >
>> >> >> Example program to fetch temperature or voltages is available at
>> >> >> http://www.planet.sci.kobe-u.ac.jp/~takawata/smbus/examples/
>> >> >> There's also an example program to fetch SDRAM info over the smbus.
>> >>
>> >> I attach you the detect.c program. It's very simple and may help us
>> >> in knowing what I2C hardware you have on your mobo.
>> >
>> >Where's my detect.c? I think you forgot to attach it :)
>>
>> :) here it is!
>
>alpm0: rev 0x00 on pci0.3.0
>alsmb0:
>smbus0: on alsmb0
>smb0: on smbus0
>
>{"/home/green/examples"}$ ./detect
>a2 found.
>d2 found.
So,
./spd 1
will work!
--
nso...@teaser.fr / nso...@freebsd.org
FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: Aladdin chipset SMBus support available!
On Sun, 14 Feb 1999, Nicolas Souchu wrote:
> On Sun, Feb 14, 1999 at 08:40:11AM -0500, Brian Feldman wrote:
> >
> >On Sun, 14 Feb 1999, Nicolas Souchu wrote:
> >
> >> On Sat, Feb 13, 1999 at 05:22:00PM -0500, Brian Feldman wrote:
> >> >
> >> >On Sat, 13 Feb 1999, Nicolas Souchu wrote:
> >> >
> >> >> Example program to fetch temperature or voltages is available at
> >> >> http://www.planet.sci.kobe-u.ac.jp/~takawata/smbus/examples/
> >> >> There's also an example program to fetch SDRAM info over the smbus.
> >>
> >> I attach you the detect.c program. It's very simple and may help us
> >> in knowing what I2C hardware you have on your mobo.
> >
> >Where's my detect.c? I think you forgot to attach it :)
>
> :) here it is!
alpm0: rev 0x00 on pci0.3.0
alsmb0:
smbus0: on alsmb0
smb0: on smbus0
{"/home/green/examples"}$ ./detect
a2 found.
d2 found.
>
> >
> >> >I tried them, and there's the problem: all the ioctl()s they perform
> >> >return
> >> >EINTR! Has this driver been tested on many motherboards? Why should I
> >> >expect
> >> >an EINTR? Just wondering :)
> >>
> >> EINTR is odd. It just mean that the device at the address requested on the
> >> I2C bus do not respond. I have to translate SMBus errors to the appropriate
> >> unix ones.
> >
> >Hmm... wouldn't the appropriate error for something not responding be an
> >ENXIO or ETIMEDOUT? EINTR seems more than a little wrong for this purpouse.
>
> Fix committed.
>
> BTW, as outlined by -pkh all this is just a first step in a huge monitoring
> adventure where all still need to be _defined_ (architecture and interfaces)
> and implemented. Any proposition for doing the job is wellcome,
> since I just have enough time to do the hardware SMBus support.
Sounds like fun
>
> Nicholas
>
> --
> nso...@teaser.fr / nso...@freebsd.org
> FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org
>
Brian Feldman_ __ ___ ___ ___
gr...@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: Aladdin chipset SMBus support available!
On Sun, Feb 14, 1999 at 08:40:11AM -0500, Brian Feldman wrote:
>
>On Sun, 14 Feb 1999, Nicolas Souchu wrote:
>
>> On Sat, Feb 13, 1999 at 05:22:00PM -0500, Brian Feldman wrote:
>> >
>> >On Sat, 13 Feb 1999, Nicolas Souchu wrote:
>> >
>> >> Example program to fetch temperature or voltages is available at
>> >> http://www.planet.sci.kobe-u.ac.jp/~takawata/smbus/examples/
>> >> There's also an example program to fetch SDRAM info over the smbus.
>>
>> I attach you the detect.c program. It's very simple and may help us
>> in knowing what I2C hardware you have on your mobo.
>
>Where's my detect.c? I think you forgot to attach it :)
:) here it is!
>
>> >I tried them, and there's the problem: all the ioctl()s they perform return
>> >EINTR! Has this driver been tested on many motherboards? Why should I expect
>> >an EINTR? Just wondering :)
>>
>> EINTR is odd. It just mean that the device at the address requested on the
>> I2C bus do not respond. I have to translate SMBus errors to the appropriate
>> unix ones.
>
>Hmm... wouldn't the appropriate error for something not responding be an
>ENXIO or ETIMEDOUT? EINTR seems more than a little wrong for this purpouse.
Fix committed.
BTW, as outlined by -pkh all this is just a first step in a huge monitoring
adventure where all still need to be _defined_ (architecture and interfaces)
and implemented. Any proposition for doing the job is wellcome,
since I just have enough time to do the hardware SMBus support.
Nicholas
--
nso...@teaser.fr / nso...@freebsd.org
FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org
/*-
* Copyright (c) 1999 Nicolas Souchu
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
*notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
*notice, this list of conditions and the following disclaimer in the
*documentation and/or other materials provided with the distribution.
*
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*
* [id for your version control system, if any]
*/
/*This program is prototype version. I'll write better one*/
#include
#include
#include
const double vfactor[]={1,1,1,1.67,4,-4,-1.67};
const char *Inpname[]={
"Vcore","Vit","VIO","+5V","+12V","-12V","-5V"
};
int doioctl(int alias, int cmd, caddr_t param)
{
int error = 1;
int retry = 3;
while (error && retry--) {
usleep(200);
error = ioctl(alias, cmd, param);
}
return (error);
}
int main (int argc,char argv[])
{
int alias, i;
unsigned char byte=0;
struct smbcmd cmd;
bzero(&cmd, sizeof(cmd));
cmd.data.byte_ptr = &byte;
alias = open("/dev/smb0", O_RDWR);
for (i=2; i<254; i+=2)
{
cmd.slave=(u_char)i;
if(doioctl(alias, SMB_RECVB, (caddr_t)&cmd)!=-1){
printf("%x found.\n",i);
}
}
close(alias);
return 0;
}
Re: Aladdin chipset SMBus support available!
On Sun, 14 Feb 1999, Nicolas Souchu wrote: > On Sat, Feb 13, 1999 at 05:22:00PM -0500, Brian Feldman wrote: > > > >On Sat, 13 Feb 1999, Nicolas Souchu wrote: > > > >> Example program to fetch temperature or voltages is available at > >> http://www.planet.sci.kobe-u.ac.jp/~takawata/smbus/examples/ > >> There's also an example program to fetch SDRAM info over the smbus. > > I attach you the detect.c program. It's very simple and may help us > in knowing what I2C hardware you have on your mobo. Where's my detect.c? I think you forgot to attach it :) > >I tried them, and there's the problem: all the ioctl()s they perform return > >EINTR! Has this driver been tested on many motherboards? Why should I expect > >an EINTR? Just wondering :) > > EINTR is odd. It just mean that the device at the address requested on the > I2C bus do not respond. I have to translate SMBus errors to the appropriate > unix ones. Hmm... wouldn't the appropriate error for something not responding be an ENXIO or ETIMEDOUT? EINTR seems more than a little wrong for this purpouse. > > -- > nso...@teaser.fr / nso...@freebsd.org > FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org > Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Aladdin chipset SMBus support available!
I had the same problem with a non Aladin system. I believe the problem is that Takanori's examples no longer work since changes were made to pcisupport.c. Why do I say this ? Because Takanori said so in email to me. I dont understand how it all works but if I show you Takanori's comments maybe you guys will. START Takanori's comments === Commited code on pcisupport.c from 1.88 to 1.89 will break it. If "intpm.h" is not included,chipset probe code is used instead of the driver probe code. P.S I have forgotten to enclose unused variable in #undef ENABLE_ALART with #ifdef ENABLE_ALART - #endif ,so the variable may deleted when it was commited. And currently ENABLE_ALART code will not work properly. END Takanori's comments == On Sun, 14 Feb 1999, Nicolas Souchu wrote: > On Sat, Feb 13, 1999 at 05:22:00PM -0500, Brian Feldman wrote: > > > >On Sat, 13 Feb 1999, Nicolas Souchu wrote: > > > >> Hi folks, > >> > >> I've just committed the alpm(4) driver to -current: the Aladdin SMBus > >> driver. > > > >Great, my newest mobo is an AcerLabs. > > > >> > >> With an onboard system management chip (lm7x or w87381), > >> it offers monitoring capabilities to recent Acer based motherboards like > >> the ASUS P5AB. > > > >I'm using a matsonic. > > > >> > >> Example program to fetch temperature or voltages is available at > >> http://www.planet.sci.kobe-u.ac.jp/~takawata/smbus/examples/ > >> There's also an example program to fetch SDRAM info over the smbus. > > I attach you the detect.c program. It's very simple and may help us > in knowing what I2C hardware you have on your mobo. > > > > >I tried them, and there's the problem: all the ioctl()s they perform return > >EINTR! Has this driver been tested on many motherboards? Why should I expect > >an EINTR? Just wondering :) > > EINTR is odd. It just mean that the device at the address requested on the > I2C bus do not respond. I have to translate SMBus errors to the appropriate > unix ones. > > > > > > >> > >> You may also want to know what smbus(4) is: > >> http://www.freebsd.org/~nsouch/iicbus.html > >> > >> Feedbacks are wellcome. > >> > >> Nicholas. > >> > >> PS: A driver is also available for the Intel PIIX4, see intpm(4). > >> > >> -- > >> nso...@teaser.fr / nso...@freebsd.org > >> FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org > >> > >> To Unsubscribe: send mail to majord...@freebsd.org > >> with "unsubscribe freebsd-current" in the body of the message > >> > > > > Brian Feldman _ __ ___ ___ ___ > > gr...@unixhelp.org_ __ ___ | _ ) __| \ > > http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | > > FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ > > > > > > -- > nso...@teaser.fr / nso...@freebsd.org > FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > > /=\ |Work: matthew.th...@dsto.defence.gov.au | Home: thy...@camtech.net.au| \=/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Aladdin chipset SMBus support available!
On Sat, Feb 13, 1999 at 05:22:00PM -0500, Brian Feldman wrote: > >On Sat, 13 Feb 1999, Nicolas Souchu wrote: > >> Hi folks, >> >> I've just committed the alpm(4) driver to -current: the Aladdin SMBus >> driver. > >Great, my newest mobo is an AcerLabs. > >> >> With an onboard system management chip (lm7x or w87381), >> it offers monitoring capabilities to recent Acer based motherboards like >> the ASUS P5AB. > >I'm using a matsonic. > >> >> Example program to fetch temperature or voltages is available at >> http://www.planet.sci.kobe-u.ac.jp/~takawata/smbus/examples/ >> There's also an example program to fetch SDRAM info over the smbus. I attach you the detect.c program. It's very simple and may help us in knowing what I2C hardware you have on your mobo. > >I tried them, and there's the problem: all the ioctl()s they perform return >EINTR! Has this driver been tested on many motherboards? Why should I expect >an EINTR? Just wondering :) EINTR is odd. It just mean that the device at the address requested on the I2C bus do not respond. I have to translate SMBus errors to the appropriate unix ones. > > >> >> You may also want to know what smbus(4) is: >> http://www.freebsd.org/~nsouch/iicbus.html >> >> Feedbacks are wellcome. >> >> Nicholas. >> >> PS: A driver is also available for the Intel PIIX4, see intpm(4). >> >> -- >> nso...@teaser.fr / nso...@freebsd.org >> FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org >> >> To Unsubscribe: send mail to majord...@freebsd.org >> with "unsubscribe freebsd-current" in the body of the message >> > > Brian Feldman _ __ ___ ___ ___ > gr...@unixhelp.org _ __ ___ | _ ) __| \ >http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | > FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ > > -- nso...@teaser.fr / nso...@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Aladdin chipset SMBus support available!
On Sat, 13 Feb 1999, Nicolas Souchu wrote: > Hi folks, > > I've just committed the alpm(4) driver to -current: the Aladdin SMBus > driver. Great, my newest mobo is an AcerLabs. > > With an onboard system management chip (lm7x or w87381), > it offers monitoring capabilities to recent Acer based motherboards like > the ASUS P5AB. I'm using a matsonic. > > Example program to fetch temperature or voltages is available at > http://www.planet.sci.kobe-u.ac.jp/~takawata/smbus/examples/ > There's also an example program to fetch SDRAM info over the smbus. I tried them, and there's the problem: all the ioctl()s they perform return EINTR! Has this driver been tested on many motherboards? Why should I expect an EINTR? Just wondering :) > > You may also want to know what smbus(4) is: > http://www.freebsd.org/~nsouch/iicbus.html > > Feedbacks are wellcome. > > Nicholas. > > PS: A driver is also available for the Intel PIIX4, see intpm(4). > > -- > nso...@teaser.fr / nso...@freebsd.org > FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Aladdin chipset SMBus support available!
Hi folks, I've just committed the alpm(4) driver to -current: the Aladdin SMBus driver. With an onboard system management chip (lm7x or w87381), it offers monitoring capabilities to recent Acer based motherboards like the ASUS P5AB. Example program to fetch temperature or voltages is available at http://www.planet.sci.kobe-u.ac.jp/~takawata/smbus/examples/ There's also an example program to fetch SDRAM info over the smbus. You may also want to know what smbus(4) is: http://www.freebsd.org/~nsouch/iicbus.html Feedbacks are wellcome. Nicholas. PS: A driver is also available for the Intel PIIX4, see intpm(4). -- nso...@teaser.fr / nso...@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
