DragonFly BSD
DragonFly kernel List (threaded) for 2005-04
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: [PR] acpi module related bug in 1.2.0R


From: YONETANI Tomokazu <qhwt+dfly@xxxxxxxxxx>
Date: Sat, 16 Apr 2005 19:53:44 +0900

On Fri, Apr 15, 2005 at 07:33:42PM +0800, Sepherosa Ziehau wrote:
> >Probably `set debug.acpi.avoid' alone should also work, because
> 
> I have read through that code, it just uses testenv().  Will it be better  
> if we can add `debug.acpi.avoidpath' env?

Committed with a slightly different name `debug.acpi.avoid.paths' .

> >                Device (CRD0)
> >                {
> >                    Name (_ADR, 0x00010000)
> >                    Method (_INI, 0, NotSerialized)
> >                    {
> >                        // SMI (0x95, 0x04)
> 
> After this line and the similar line in `Device (CRD1)' block have been  
> commented out, everything works fine.

It translates to something as below. I don't know what it does though,
as I have zero knowledge of the SMI register.

  #define SMIC 0xB2
  #define SMID 0xB3
  int val;
  /* acquire mutex for this operation here */
  outb(SMID, 0x04);
  outb(SMIC, 0x95);
  while (inb(SMIC) != 0)
	  ;
  val = inb(SMID);
  /* release mutex for this operation here */




[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]