[haiku-bugs] Re: [Haiku] #5449: ACPI: AcpiInitializeTables fails on Acer Aspire One AOA110

  • From: "bonefish" <trac@xxxxxxxxxxxx>
  • Date: Tue, 23 Feb 2010 17:47:21 -0000

#5449: ACPI: AcpiInitializeTables fails on Acer Aspire One AOA110
--------------------------+-------------------------------------------------
 Reporter:  vegardw       |       Owner:  nobody        
     Type:  bug           |      Status:  new           
 Priority:  normal        |   Milestone:  R1            
Component:  Drivers/ACPI  |     Version:  R1/Development
 Keywords:                |   Blockedby:                
 Platform:  All           |    Blocking:                
--------------------------+-------------------------------------------------

Comment(by bonefish):

 Replying to [comment:9 phoudoin]:
 > Replying to [comment:7 bonefish]:
 > > Not that I think it makes a difference in this case, but is there a
 reason why the map_physical_memory() call in AcpiOsMapMemory() uses
 B_ANY_KERNEL_BLOCK_ADDRESS?
 >
 > None that I know. This change was introduced in r33781.
 > Does B_ANY_KERNEL_BLOCK_ADDRESS semantic means that byte 0 at the
 virtual address returned doesn't always map to the byte 0 at physical
 address? That will do a big difference!

 No, B_ANY_KERNEL_BLOCK_ADDRESS only affects the placement of the area, not
 the mapping. It works like B_ANY_KERNEL_ADDRESS just with a stricter
 alignment for the (virtual) base address of the area.

-- 
Ticket URL: <http://dev.haiku-os.org/ticket/5449#comment:10>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.

Other related posts: