Clean up: spacing, remove obsolete comment, kill contractions.
Note: Some of these tasks were not showing on the original page due to a bad link.
This commit is contained in:
		
							parent
							
								
									9e65bb68de
								
							
						
					
					
						commit
						2664f67faa
					
				
				
				Notes:
				
					svn2git
				
				2020-12-08 03:00:23 +00:00 
				
			
			svn path=/www/; revision=23244
					 1 changed files with 32 additions and 35 deletions
				
			
		|  | @ -1,6 +1,6 @@ | |||
| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [ | ||||
| <!ENTITY base CDATA "../.."> | ||||
| <!ENTITY date "$FreeBSD: www/en/projects/acpi/index.sgml,v 1.3 2004/12/16 18:12:13 trhodes Exp $"> | ||||
| <!ENTITY date "$FreeBSD: www/en/projects/acpi/index.sgml,v 1.4 2004/12/16 18:15:22 trhodes Exp $"> | ||||
| <!ENTITY title "FreeBSD ACPI project"> | ||||
| <!ENTITY email 'marks'> | ||||
| <!ENTITY acpi-mail 'freebsd-acpi@FreeBSD.org'> | ||||
|  | @ -14,9 +14,6 @@ | |||
| <!ENTITY status.new "<font color=red>Not done</font>"> | ||||
| <!ENTITY status.unknown "<font color=red>Unknown</font>"> | ||||
| 
 | ||||
| <!-- The list of contributors was moved to a separate file so that it can | ||||
|   be used by other documents in the FreeBSD web site. --> | ||||
| 
 | ||||
| <!ENTITY % developers SYSTEM "../../developers.sgml"> %developers; | ||||
| 
 | ||||
| ]> | ||||
|  | @ -48,7 +45,7 @@ | |||
|     <a name="high-priority"></a> | ||||
|     <h3>High Priority Tasks</h3> | ||||
| 
 | ||||
|     <table border="3" rules="groups"> | ||||
|     <table border="1" width="100%"> | ||||
|       <thead> | ||||
| 	<tr> | ||||
| 	  <th> Task </th> | ||||
|  | @ -177,7 +174,7 @@ | |||
|     <a name="medium-priority"></a> | ||||
|     <h3>Medium Priority Tasks</h3> | ||||
| 
 | ||||
|     <table> | ||||
|     <table border="1" width="100%"> | ||||
|       <tbody> | ||||
| 	<tr> | ||||
| 	  <td> Hotkey/backlight/sound generic driver Add a driver | ||||
|  | @ -208,7 +205,7 @@ | |||
|     <a name="low-priority"></a> | ||||
|     <h3>Low Priority Tasks</h3> | ||||
| 
 | ||||
|     <table> | ||||
|     <table border="1" width="100%"> | ||||
|       <tbody> | ||||
| 	<tr> | ||||
| 	  <td> Implement X suspend/resume notification.  Currently, | ||||
|  | @ -223,12 +220,12 @@ | |||
| 	    Then implement the ioctls in both apm and acpi (on the apm | ||||
| 	    compat device). | ||||
| 	    <a href="http://www.root.org/~nate/freebsd/bsd_apm.diff">Here is a | ||||
| 	    patch</a> to help the X file compile.  For acpi, we don't want | ||||
| 	    patch</a> to help the X file compile.  For acpi, we do not want | ||||
| 	    a user process dying to hold up the suspend process so implement | ||||
| 	    the notification with a timeout.  That is, if the kernel generates | ||||
| 	    a APM_STANDBY_REQ notification and it doesn't receive a | ||||
| 	    APM_IOC_STANDBY within say 5 seconds, continue the suspend process. | ||||
| 	    This is needed for standby when X isn't running, for instance, or | ||||
| 	    This is needed for standby when X is not running, for instance, or | ||||
| 	    when an emergency suspend is generated by a battery going | ||||
| 	    critical.</td> | ||||
|           <td>   </td> | ||||
|  | @ -242,9 +239,9 @@ | |||
| 	    Linux has begun to test calling the "lcall" VESA reset after | ||||
| 	    PCI devices (including the video card) have been fully resumed, | ||||
| 	    including power state set to PS0. This works for many Radeon | ||||
| 	    cards but fails for others. We could implement this in vm86 | ||||
| 	    calls from a proper video driver resume method. Also, implement | ||||
| 	    the int 10h resume hack that Linux has since we don't have that yet. | ||||
| 	    cards but fails for others.  We could implement this in vm86 | ||||
| 	    calls from a proper video driver resume method.  Also, implement | ||||
| 	    the int 10h resume hack that Linux has since we do not have that yet. | ||||
| 	    It is unclear how effective it is but some systems do require it. </td> | ||||
| 	  <td>   </td> | ||||
| 	  <td>   </td> | ||||
|  | @ -253,10 +250,10 @@ | |||
| 	</tr> | ||||
| 
 | ||||
| 	<tr> | ||||
| 	  <td>  Check our DWORD access to EC regions, including endianness. | ||||
| 	  <td> Check our DWORD access to EC regions, including endianness. | ||||
| 	    Currently, we treat DWORD access as little-endian, which makes | ||||
| 	    sense on PCs. It's really not correct to do use access other than | ||||
| 	    BYTE for EC space but some ASL uses DWORD. Also, we should test | ||||
| 	    sense on PCs.  It's really not correct to do use access other than | ||||
| 	    BYTE for EC space but some ASL uses DWORD.  Also, we should test | ||||
| 	    what happens for AnyAccess reads/writes to EC space since some | ||||
| 	    ASL does this too. </td> | ||||
| 	  <td>   </td> | ||||
|  | @ -266,8 +263,8 @@ | |||
| 	</tr> | ||||
| 
 | ||||
| 	<tr> | ||||
| 	  <td>  ACPI-CA should really enable GPEs before calling \_WAK. | ||||
| 	    Currently it does the opposite. This does not match the ACPI | ||||
| 	  <td> ACPI-CA should really enable GPEs before calling \_WAK. | ||||
| 	    Currently it does the opposite.  This does not match the ACPI | ||||
| 	    spec where \_WAK should be called after the system is up | ||||
| 	    and running (\_BFS is what should be called as soon as | ||||
| 	    possible after waking.) </td> | ||||
|  | @ -280,7 +277,7 @@ | |||
| 	<tr> | ||||
| 	  <td> Potential ASL bug: We may need to work around some systems | ||||
| 	    having the S3 object listed under the LPC bus device (PNP0A03) | ||||
| 	    instead of root (\). This is ACPI-CA's responsibility. </td> | ||||
| 	    instead of root (\).  This is ACPI-CA's responsibility. </td> | ||||
| 	  <td>   </td> | ||||
| 	  <td>   </td> | ||||
| 	  <td> &status.new; </td> | ||||
|  | @ -300,7 +297,7 @@ | |||
| 	  <td> See if we can enable EC access early even if an ECDT is not | ||||
| 	    present. The _INI method for some ECs accesses the EC region | ||||
| 	    even though _REG has not been called since the region is not | ||||
| 	    initialized yet. It's likely that Windows hard-codes the EC | ||||
| 	    initialized yet. It is likely that Windows hard-codes the EC | ||||
| 	    resources and enables the region before initializing the device | ||||
| 	    even though this is not allowed by the spec. </td> | ||||
| 	  <td>   </td> | ||||
|  | @ -320,9 +317,9 @@ | |||
| 
 | ||||
| 	<tr> | ||||
| 	  <td> Be sure not to try to disable ACPI on systems that do not have | ||||
| 	    SMI_CMD or ACPI_ENABLE/DISABLE values in the FADT. The ia64 machines | ||||
| 	    SMI_CMD or ACPI_ENABLE/DISABLE values in the FADT.  The ia64 machines | ||||
| 	    specify ACPI-only (no legacy mode) so they have 0 for these | ||||
| 	    values and we shouldn't enable/disable ACPI on them. Doing so | ||||
| 	    values and we should not enable/disable ACPI on them.  Doing so | ||||
| 	    gives a "failed to switch modes" warning but no real problems,  | ||||
| 	    apparently. </td> | ||||
| 	  <td>   </td> | ||||
|  | @ -333,7 +330,7 @@ | |||
| 
 | ||||
| 	<tr> | ||||
| 	  <td> Check our implementation of AcpiOsDerivePciId(). | ||||
| 	    It is probably not quite right. Compare against Linux. </td> | ||||
| 	    It is probably not quite right.  Compare against Linux. </td> | ||||
| 	  <td>   </td> | ||||
| 	  <td>   </td> | ||||
| 	  <td> &status.new; </td> | ||||
|  | @ -341,7 +338,7 @@ | |||
| 	</tr> | ||||
| 
 | ||||
| 	<tr> | ||||
| 	  <td> Run instructions on cpu0 for suspend/resume. We currently do | ||||
| 	  <td> Run instructions on cpu0 for suspend/resume.  We currently do | ||||
| 	    this for shutdown in kern_shutdown.c:boot().  This will also be | ||||
| 	    required for SMP cpufreq drivers that set the frequency via a | ||||
| 	    CPU-specific MSR. </td> | ||||
|  | @ -354,7 +351,7 @@ | |||
| 	<tr> | ||||
| 	  <td> Implement passive cooling in ACPI thermal.  It should use the | ||||
| 	    cpufreq interface to cool the processor, based on the various _PSV | ||||
| 	    settings. Also, we need to implement variable polling intervals | ||||
| 	    settings.  Also, we need to implement variable polling intervals | ||||
| 	    for thermal zones based on both the passive settings and polling | ||||
| 	    explicitly specified in the ASL. </td> | ||||
| 	  <td>   </td> | ||||
|  | @ -401,9 +398,9 @@ | |||
| 	  <td> Fix stray irq 9 on reboot -- | ||||
| 	    AcpiTerminate -> AcpiEvTerminate unhooks the SCI and then we | ||||
| 	    get a stray irq.  Debug why. Also, disable/ re-enable acpi gives | ||||
| 	    "SCI already attached". Check flags for AcpiDisable vs. | ||||
| 	    AcpiTerminate. This looks uncommon and doesn't cause any problems | ||||
| 	    so I am ignoring it for now. </td> | ||||
| 	    "SCI already attached".  Check flags for AcpiDisable vs. | ||||
| 	    AcpiTerminate. This looks uncommon and does not cause any problems | ||||
| 	    so it will be ignored for now. </td> | ||||
| 	  <td> &a.njl; </td> | ||||
| 	  <td>   </td> | ||||
| 	  <td> &status.wip; </td> | ||||
|  | @ -412,9 +409,9 @@ | |||
| 
 | ||||
| 	<tr> | ||||
| 	  <td> Add EC burst mode -- Code was written before to add burst mode to | ||||
| 	    the EC. Unfortunately, it had to be disabled since it did not | ||||
| 	    appear to work on all systems. I am guessing that some systems | ||||
| 	    do not function correctly without burst mode, so I will add it | ||||
| 	    the EC.  Unfortunately, it had to be disabled since it did not | ||||
| 	    appear to work on all systems.  Perhaps on some systems | ||||
| 	    do not function correctly without burst mode, so it will be added | ||||
| 	    back with some logic to fallback if it fails. </td> | ||||
| 	  <td>   </td> | ||||
| 	  <td>   </td> | ||||
|  | @ -425,7 +422,7 @@ | |||
| 	<tr> | ||||
| 	  <td> Add smart battery support -- Smart batteries use the SMBus | ||||
| 	    to communicate data instead of the embedded controller for | ||||
| 	    control-method batteries. Newer ACER laptops have this and | ||||
| 	    control-method batteries.  Newer ACER laptops have this and | ||||
| 	    it will be needed for battery status on them.  This is rather | ||||
| 	    difficult since it involves interfacing with the SMBus drivers | ||||
| 	    (likely need some kobj methods for this.) </td> | ||||
|  | @ -437,11 +434,11 @@ | |||
| 
 | ||||
| 	<tr> | ||||
| 	  <td> Intel firmware seems to describe the PCI root bridge where | ||||
| 	    chipset configuration space lives with _STA==0x8. The spec | ||||
| 	    says this means "functional, but not present". The current | ||||
| 	    chipset configuration space lives with _STA==0x8.  The spec | ||||
| 	    says this means "functional, but not present".  The current | ||||
| 	    code ignores things that are "not present" | ||||
| 	    (<a href="https://sourceforge.net/mailarchive/message.php?msg_id=6923358"> | ||||
| 	    msg</a>). It is suggested that this should be handled by not | ||||
| 	    msg</a>).  It is suggested that this should be handled by not | ||||
| 	    attaching a driver to the device (i.e. bridge) but probe its children. | ||||
| 	    Present on Big Sur and Bull systems. </td> | ||||
| 	  <td>   </td> | ||||
|  | @ -498,7 +495,7 @@ | |||
| 	  <td> HP/Toshiba Satellite driver -- Enabling the extra | ||||
| 	    one-touch/multimedia keys, console blanking, battery and | ||||
| 	    temperature reporting, etc.  Get an idea of what is needed from | ||||
| 	    the <a href="http://sourceforge.net/projects/omke/>Linux OMKE project"> | ||||
| 	    the <a href="http://sourceforge.net/projects/omke/">Linux OMKE project | ||||
| 	    </a>. </td> | ||||
| 	  <td>   </td> | ||||
| 	  <td>   </td> | ||||
|  |  | |||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue