Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • lava lava
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 142
    • Issues 142
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 32
    • Merge requests 32
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • lava
  • lavalava
  • Merge requests
  • !1759

Open
Created May 23, 2022 by Larry Shen@atlineContributor
  • Report abuse
Report abuse

device-type:imx:allow to use address in uboot env.

  • Overview 0
  • Commits 1
  • Pipelines 1
  • Changes 5

We had next changes for i.mx:

MLK-25823 imx8/imx8m: Update kernel load address to 2MB aligned

Since 5.10, kernel has removed the 0x80000 offset requirement to kernel image load address. Using old address like 0x80280000 by booti will introduce a additional copy to 2MB aligned address.

So set default kernel load address to 0x80200000 for iMX8/iMX8ULP, and 0x80400000 for iMX8M. For old kernel, booti will handle the 0x80000 offset by adding a copy.

Another word, for >=5.10 kernel, we need to change loadaddr for kernel address to increase the speed for boot. But looks LAVA just maintain one copy of value, can't distinguish between different uboot settings.

So, we propose this MR which boot from the addr specified in i.mx uboot environment, with this way, we no need to put an eye on later changes, as uboot build will handle the difference between different kernels, or other kinds of address changes.

Still, we will remain the referenced value, e.g. if any community uboot build doesn't have loadaddr, fdt_addr, etc, they still could boot using NXP referenced address. But, we will just keep/maintain the latest value of loadaddr etc. Do you think this strategy ok? Please help to comments on this MR, we need your inputs, thanks.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: imx_dt_env