os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add a new ACPI mailing list.

Browse source 
PR:		65567
Submitted by:	Ion-Mihai Tetcu <itetcu@apropo.ro>
Requested by:	njl (but I forgot to add it)
This commit is contained in:
Tom Rhodes 2004-04-15 15:20:29 +00:00
parent befa2c659d
commit 23298cd3f3
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=20708
2 changed files with 30 additions and 9 deletions
en_US.ISO8859-1/books/handbook
config
chapter.sgml
eresources
chapter.sgml

24
en_US.ISO8859-1/books/handbook/config/chapter.sgml
View file

@ -2342,8 +2342,8 @@ device_probe_and_attach: cbb0 attach returned 12</screen>
<para>For those of you that want to submit a problem right away,
please send the following information to
<ulink url="mailto:acpi-jp@jp.FreeBSD.org">
acpi-jp@jp.FreeBSD.org</ulink></para>
<ulink url="mailto:freebsd-acpi@FreeBSD.org">
freebsd-acpi@FreeBSD.org</ulink></para>
<itemizedlist>
<listitem>
@ -2388,14 +2388,14 @@ device_probe_and_attach: cbb0 attach returned 12</screen>
</itemizedlist>
<para>Most of the developers watch the freebsd-current mailing
list but please submit problems to acpi-jp to be sure it is
list but please submit problems to acpi list to be sure it is
seen. Please be patient, all of us have full-time jobs
elsewhere. If your bug is not immediately apparent, we will
probably ask you to submit a <acronym>PR</acronym> via
&man.send-pr.1;. When entering a <acronym>PR</acronym>, please
include the same information as requested above. This will help
us track the problem and resolve it. Do not send a
<acronym>PR</acronym> without emailing acpi-jp first as we use
<acronym>PR</acronym> without emailing acpi list first as we use
<acronym>PR</acronym>s as reminders of existing problems, not a
reporting mechanism. It is likely that your problem has been
reported by someone before.</para>
@ -2488,7 +2488,7 @@ device_probe_and_attach: cbb0 attach returned 12</screen>
to try is <literal>S3</literal>. This is the deepest
<acronym>STR</acronym> state and requires a lot of driver
support to properly reinitialize your hardware. If you have
problems resuming, feel free to email the acpi-jp list but
problems resuming, feel free to email the acpi list but
do not expect the problem to be resolved since there are a lot
of drivers/hardware that need more testing and work.</para>
@ -2781,16 +2781,22 @@ debug.acpi.level="ACPI_LV_ERROR"</programlisting>
<itemizedlist>
<listitem>
<para>The <acronym>ACPI</acronym> Mailing List
<ulink url="mailto:acpi-jp@jp.FreeBSD.org">
acpi-jp@jp.FreeBSD.org</ulink></para>
<ulink url="mailto:freebsd-acpi@FreeBSD.org">
freebsd-acpi@FreeBSD.org</ulink></para>
</listitem>
<listitem>
<para>The <acronym>ACPI</acronym> Mailing List Archives
<ulink url="http://home.jp.FreeBSD.org/mail-list/acpi-jp/">
http://home.jp.FreeBSD.org/mail-list/acpi-jp/</ulink></para>
<ulink url="http://lists.freebsd.org/pipermail/freebsd-acpi/">
http://lists.freebsd.org/pipermail/freebsd-acpi/</ulink></para>
</listitem>
<listitem>
<para>The old <acronym>ACPI</acronym> Mailing List Archives
<ulink url="http://home.jp.FreeBSD.org/mail-list/acpi-jp/">
http://home.jp.FreeBSD.org/mail-list/acpi-jp/</ulink></para>
</listitem>
<listitem>
<para>The <acronym>ACPI</acronym> 2.0 Specification
<ulink url="http://acpi.info/spec.htm">

15
en_US.ISO8859-1/books/handbook/eresources/chapter.sgml
View file

@ -173,6 +173,11 @@
</thead>
<tbody>
<row>
<entry>&a.acpi.name;</entry>
<entry>ACPI and power management development</entry>
</row>
<row>
<entry>&a.afs.name;</entry>
<entry>Porting AFS to FreeBSD</entry>
@ -638,6 +643,16 @@
<para><emphasis>Individual list charters:</emphasis></para>
<variablelist>
<varlistentry>
<term>&a.acpi.name;</term>
<listitem>
<para><emphasis>ACPI and power management
development</emphasis></para>
</listitem>
</varlistentry>
<varlistentry>
<term>&a.afs.name;</term>