#9318 NORM 1.5-ATe: Why is vmalloc=256M required for viafb?

[Zarro Boogs per Child]

#9318: Why is vmalloc=256M required for viafb?
--------------------------------+-------------------------------------------
           Reporter:  cjb       |       Owner:  dsaxena      
               Type:  defect    |      Status:  new          
           Priority:  normal    |   Milestone:  1.5-ATest    
          Component:  kernel    |     Version:  not specified
         Resolution:            |    Keywords:               
        Next_action:  diagnose  |    Verified:  0            
Deployment_affected:            |   Blockedby:               
           Blocking:            |  
--------------------------------+-------------------------------------------

Comment(by cjb):

 Actually, the output pasted above is from Phoenix.  There is an option to
 select the fb size in Phoenix -- it was set to 256M by default, when that
 error was generated, and moving it to 64M got viafb working.

 OFW seems to set 64M, not 256M, and yet the ioremap() failure still
 happens; you can see it by removing the vmalloc= boot param.

-- 
Ticket URL: <http://dev.laptop.org/ticket/9318#comment:7>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system