From: "Hiroshi Itoh" <hiroit-s3IJUFpODnp4Eiagz67IpQ@public.gmane.org>
To: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Cc: Linus Torvalds <torvalds-3NddpPZAyC0@public.gmane.org>,
Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: Re: [BKPATCH] ACPI for 2.6
Date: Sat, 13 Nov 2004 03:18:15 +0900 [thread overview]
Message-ID: <004401c4c8e3$fb077d80$7bbdbd09@TPHIROIT> (raw)
In-Reply-To: 20041112174248.GA4267@openzaurus.ucw.cz
>> Useful to workaround C3 ipw2100 packet loss,
>> reducing noise or boot issues on some models.
>> http://bugme.osdl.org/show_bug.cgi?id=3549
>>
>> For static processor driver, boot cmdline:
>> processor.acpi_cstate_limit=2
>You certainly win "ugliest parameter of the month" contest :-).
>What about processor.max_cstate= or something?
Always you are not so gentle, but often cool. :-)
-Hiro
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
WARNING: multiple messages have this Message-ID (diff)
From: "Hiroshi Itoh" <hiroit@mcn.ne.jp>
To: "Pavel Machek" <pavel@ucw.cz>
Cc: "Linus Torvalds" <torvalds@osdl.org>,
"Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"ACPI Developers" <acpi-devel@lists.sourceforge.net>,
"Len Brown" <len.brown@intel.com>
Subject: Re: [ACPI] Re: [BKPATCH] ACPI for 2.6
Date: Sat, 13 Nov 2004 03:18:15 +0900 [thread overview]
Message-ID: <004401c4c8e3$fb077d80$7bbdbd09@TPHIROIT> (raw)
In-Reply-To: 20041112174248.GA4267@openzaurus.ucw.cz
>> Useful to workaround C3 ipw2100 packet loss,
>> reducing noise or boot issues on some models.
>> http://bugme.osdl.org/show_bug.cgi?id=3549
>>
>> For static processor driver, boot cmdline:
>> processor.acpi_cstate_limit=2
>You certainly win "ugliest parameter of the month" contest :-).
>What about processor.max_cstate= or something?
Always you are not so gentle, but often cool. :-)
-Hiro
next prev parent reply other threads:[~2004-11-12 18:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 7:47 [BKPATCH] ACPI for 2.6 Len Brown
2004-11-09 7:47 ` Len Brown
2004-11-12 17:42 ` Pavel Machek
2004-11-12 18:18 ` Hiroshi Itoh [this message]
2004-11-12 18:18 ` [ACPI] " Hiroshi Itoh
[not found] ` <20041112174248.GA4267-u08AdweFZfgxtPtxi4kahqVXKuFTiq87@public.gmane.org>
2004-12-01 23:13 ` Len Brown
2004-12-01 23:13 ` Len Brown
-- strict thread matches above, loose matches on Subject: below --
2004-06-25 2:13 Wang, Zhenyu Z
[not found] ` <6E0C289723A0564F9A8279E236E8565F07A9E170-4yWAQGcml64divtuJNk2fFDQ4js95KgL@public.gmane.org>
2004-06-25 16:35 ` Stefan Seyfried
2004-06-24 4:22 Wang, Zhenyu Z
[not found] ` <6E0C289723A0564F9A8279E236E8565F07A55A53-4yWAQGcml64divtuJNk2fFDQ4js95KgL@public.gmane.org>
2004-06-24 20:16 ` Stefan Seyfried
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='004401c4c8e3$fb077d80$7bbdbd09@TPHIROIT' \
--to=hiroit-s3ijufpodnp4eiagz67ipq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pavel-+ZI9xUNit7I@public.gmane.org \
--cc=torvalds-3NddpPZAyC0@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.