Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
V
virtual-dev-docs
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
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
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Moritz Knaut
virtual-dev-docs
Commits
b0419133
There was a problem fetching the pipeline summary.
Commit
b0419133
authored
9 years ago
by
Moritz Knaut
Browse files
Options
Downloads
Patches
Plain Diff
* Added protocol for 14.05.2016
parent
b1a1f590
Branches
Branches containing commit
No related tags found
No related merge requests found
Pipeline
#
Changes
1
Pipelines
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
protocols/PROTOCOL_14_05_2016
+25
-0
25 additions, 0 deletions
protocols/PROTOCOL_14_05_2016
with
25 additions
and
0 deletions
protocols/PROTOCOL_14_05_2016
0 → 100644
+
25
−
0
View file @
b0419133
TODOs for next week:
- Search the kernel data structures which contain the objects we want to supply as virtual 'devices'
- Search the specific abstraction layer for each group of devices
- Think about the connection to the application program emulating the hardware.
[- Keep in mind the other direction: real devices connected to virtual operating system(FAUMachine).]
Device groups to implement:
- USB:
- Abstraction layer could be the layer of usb controllers
- Define driver for 'virtual' usb controller and append it to the usb controller list
- Harddrive ATA:
- Block I/O?
- Network interface:
- Abstraction layer could be the lowest layer in OSI/IP stack (Between IP and MAC)
- Register as network card driver.
- Character devices:
- Abstraction layer could be just read/write/...
- Register as character device driver.
[ - Other devices: ]
[ - Just replace the normal driver, abstraction layer is ioctl,read,write,open,close,... ]
[ - Is there in some drivers a abstraction layer between driver code and in/out/mem? ]
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