Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • L linux-vs
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • linux-arm
  • linux-vs
  • Repository
  • linux-vs
  • arch
  • xtensa
  • kernel
  • head.S
Find file BlameHistoryPermalink
  • Max Filippov's avatar
    xtensa: adjust boot parameters address when INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX is selected · c5a771d0
    Max Filippov authored Jun 09, 2013
    
    
    The virtual address of boot parameters chain is passed to the kernel via
    a2 register. Adjust it in case it is remapped during MMUv3 -> MMUv2
    mapping change, i.e. when it is in the first 128M.
    
    Also fix interpretation of initrd and FDT addresses passed in the boot
    parameters: these are physical addresses.
    
    Cc: stable@vger.kernel.org
    Reported-by: default avatarBaruch Siach <baruch@tkos.co.il>
    Signed-off-by: default avatarMax Filippov <jcmvbkbc@gmail.com>
    Signed-off-by: default avatarChris Zankel <chris@zankel.net>
    c5a771d0