Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
pthreads-emb
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
redox-os
pthreads-emb
Commits
3933b540
Commit
3933b540
authored
13 years ago
by
Jason Schmidlapp
Browse files
Options
Downloads
Patches
Plain Diff
Added README
parent
747ec726
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README
+16
-0
16 additions, 0 deletions
README
with
16 additions
and
0 deletions
README
0 → 100644
+
16
−
0
View file @
3933b540
POSIX Threads for embedded systems (PTE)
PTE is an open source implementation of the POSIX API for multithreaded
applications (pthreads). It is intended to be used to provide a pthreads
API for embedded operating systems that do not natively provide a pthreads
API. PTE is designed to be easily portable to such operating systems and only
relies on basic primitives (e.g. semaphores) that are widely supported on most
embedded operating systems.
Currently, PTE has been ported to Texas Instrument's DSP/BIOS and Sony's PSP OS.
PTE is based heavily on Pthreads Win32, and implementation of pthreads
for Windows.
Information on building and porting PTE is available at
https://github.com/jschmidlapp/pthreads-emb/wiki.
\ No newline at end of file
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment