On Wed, 27 Jul 2005, Lee Revell wrote:
> On Wed, 2005-07-27 at 02:13 -0600, Zwane Mwaikambo wrote:
> > > What about audio? If there is a sound server running then you're going
> > > to have a constant stream of interrupts and DMA activity from the sound
> > > card even if the machine is idle
On Wed, 27 Jul 2005 16:43:07 EDT, Lee Revell said:
> As far as legacy support, AFAIK esd and artsd both grab the sound device
> on startup and never release it.
'man esd' on a FC4 system includes:
-as SECS free audio device after SECS of inactivity
and has '-as 2' specified in
On Wed, 2005-07-27 at 02:13 -0600, Zwane Mwaikambo wrote:
> > What about audio? If there is a sound server running then you're going
> > to have a constant stream of interrupts and DMA activity from the sound
> > card even if the machine is idle and there aren't any sounds playing.
>
> Doesn't
On Mon, 25 Jul 2005, Lee Revell wrote:
> On Mon, 2005-07-25 at 17:19 -0400, Brown, Len wrote:
> > >>>Question one, are there other actions to consider?
> > >>
> > >>
> > >> Yes.
> > >> Speaking for ACPI C3 state, note that DMA also
> > >> wakes up the CPU -- even if there was no device
On Mon, 25 Jul 2005, Lee Revell wrote:
On Mon, 2005-07-25 at 17:19 -0400, Brown, Len wrote:
Question one, are there other actions to consider?
Yes.
Speaking for ACPI C3 state, note that DMA also
wakes up the CPU -- even if there was no device interrupt.
(aka, the trouble
On Wed, 2005-07-27 at 02:13 -0600, Zwane Mwaikambo wrote:
What about audio? If there is a sound server running then you're going
to have a constant stream of interrupts and DMA activity from the sound
card even if the machine is idle and there aren't any sounds playing.
Doesn't artsd at
On Wed, 27 Jul 2005 16:43:07 EDT, Lee Revell said:
As far as legacy support, AFAIK esd and artsd both grab the sound device
on startup and never release it.
'man esd' on a FC4 system includes:
-as SECS free audio device after SECS of inactivity
and has '-as 2' specified in
On Wed, 27 Jul 2005, Lee Revell wrote:
On Wed, 2005-07-27 at 02:13 -0600, Zwane Mwaikambo wrote:
What about audio? If there is a sound server running then you're going
to have a constant stream of interrupts and DMA activity from the sound
card even if the machine is idle and there
Brown, Len wrote:
Question one, are there other actions to consider?
Yes.
Speaking for ACPI C3 state, note that DMA also
wakes up the CPU -- even if there was no device interrupt.
(aka, "the trouble with USB")
Trouble? Why would USB do DMA unless there was a device activity?
look
>>>Trouble? Why would USB do DMA unless there was a device activity?
>>
>>
>> look here:
>> http://www.google.com/search?hl=en=usb+selective+suspend
>>
>> Linux is working on it too, but it is in development.
>
>Somehow I didn't ask that right... The stuff on selective disable is
Trouble? Why would USB do DMA unless there was a device activity?
look here:
http://www.google.com/search?hl=enq=usb+selective+suspend
Linux is working on it too, but it is in development.
Somehow I didn't ask that right... The stuff on selective disable is
interesting, but my
Brown, Len wrote:
Question one, are there other actions to consider?
Yes.
Speaking for ACPI C3 state, note that DMA also
wakes up the CPU -- even if there was no device interrupt.
(aka, the trouble with USB)
Trouble? Why would USB do DMA unless there was a device activity?
look here:
On Mon, 2005-07-25 at 17:19 -0400, Brown, Len wrote:
> >>>Question one, are there other actions to consider?
> >>
> >>
> >> Yes.
> >> Speaking for ACPI C3 state, note that DMA also
> >> wakes up the CPU -- even if there was no device interrupt.
> >> (aka, "the trouble with USB")
> >
> >Trouble?
>>>Question one, are there other actions to consider?
>>
>>
>> Yes.
>> Speaking for ACPI C3 state, note that DMA also
>> wakes up the CPU -- even if there was no device interrupt.
>> (aka, "the trouble with USB")
>
>Trouble? Why would USB do DMA unless there was a device activity?
look here:
Brown, Len wrote:
I was thinking about variable tick times, and I can think of three
classes of action needing CPU attention.
- device interrupts, which occur at no predictable time but would pull
the CPU out of a HLT or low power state.
- process sleeps of various kinds, which have a known
>I was thinking about variable tick times, and I can think of three
>classes of action needing CPU attention.
>- device interrupts, which occur at no predictable time but would pull
>the CPU out of a HLT or low power state.
>- process sleeps of various kinds, which have a known time of
I was thinking about variable tick times, and I can think of three
classes of action needing CPU attention.
- device interrupts, which occur at no predictable time but would pull
the CPU out of a HLT or low power state.
- process sleeps of various kinds, which have a known time of
occurence.
Brown, Len wrote:
I was thinking about variable tick times, and I can think of three
classes of action needing CPU attention.
- device interrupts, which occur at no predictable time but would pull
the CPU out of a HLT or low power state.
- process sleeps of various kinds, which have a known
Question one, are there other actions to consider?
Yes.
Speaking for ACPI C3 state, note that DMA also
wakes up the CPU -- even if there was no device interrupt.
(aka, the trouble with USB)
Trouble? Why would USB do DMA unless there was a device activity?
look here:
On Mon, 2005-07-25 at 17:19 -0400, Brown, Len wrote:
Question one, are there other actions to consider?
Yes.
Speaking for ACPI C3 state, note that DMA also
wakes up the CPU -- even if there was no device interrupt.
(aka, the trouble with USB)
Trouble? Why would USB do DMA unless
20 matches
Mail list logo
