Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • U uPython-mirror
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TASTETASTE
  • uPython-mirror
  • Repository
  • uPython-mirror
  • zephyr
  • uart_core.c
Find file Blame History Permalink
  • Paul Sokolovsky's avatar
    zephyr/uart_core: Access console UART directly instead of printk() hack. · 56a514c1
    Paul Sokolovsky authored Dec 17, 2016
    This is required to avoid extra level of output "cooking" ("\r\r\n") and
    make test infrastructure work. On the other hand, this breaks somewhat
    Zephyr console abstraction.
    56a514c1