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 unifie
: 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
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,
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 -DDEB
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
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 try
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
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
> >{"/h
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,
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 sp
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:
>sm
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 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 wro
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:
> >> >
> >>
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 availab
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/
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
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 chi
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
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 a
20 matches
Mail list logo
