From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Dominik Brodowski
<linux-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
Cc: ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: C3 support w/o ARB_DIS (P4-M on i845)
Date: 14 May 2004 02:49:54 -0400 [thread overview]
Message-ID: <1084517394.12353.273.camel@dhcppc4> (raw)
In-Reply-To: <20040513120848.GA8406-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
> On the other hand, your BIOS / hardware vendor likely disallowed C3
> for a reason, e.g. some hardware which doesn't work flawlessly with ARB_DIS.
> Note, for example, that the ipw2100 project ( http://ipw2100.sf.net )
> suffers from some strange C3-related errors.
I believe that this is a device-specific issue caused by inability
to deal with DMA buffer overflow/underruns that occur due to the
delays related to coming out of C3.
-Len
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
prev parent reply other threads:[~2004-05-14 6:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 10:25 C3 support w/o ARB_DIS (P4-M on i845) Karol Kozimor
[not found] ` <20040512102527.GA8050-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-05-12 16:03 ` Dominik Brodowski
[not found] ` <20040512160353.GA7906-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2004-05-12 19:55 ` Karol Kozimor
[not found] ` <20040512195546.GA19939-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-05-13 12:08 ` Dominik Brodowski
[not found] ` <20040513120848.GA8406-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2004-05-14 6:49 ` Len Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1084517394.12353.273.camel@dhcppc4 \
--to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox