Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • V vme_core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Rimfaxe
  • vme_core
  • Merge requests
  • !4

Latch in out

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Håkan Johansson requested to merge latch_in_out into master Aug 27, 2020
  • Overview 1
  • Commits 3
  • Pipelines 2
  • Changes 1

Two commits: first one separates the latch flip flops for the read and write data directions in the vme core. Not sharing flip-flops means that the router has more freedom in placement. (And might rid it of LUTs in the path to them). Please check the changes, especially in the commented out sections.

The second commit tried to only get data for the low 16 bits if we are not in 32/64 bit mode. Please check if I got the polarity of lword* right. Also not sure if the test for MBLT is needed there.

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