StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POUnderstanding Device Driver code with running commmentary
primarykey
Id
15215582
data
AcceptedAnswerId
0
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-03-05T03:59:51.170
FavoriteCount
1
LastActivityDate
2013-03-05T21:37:29.443
LastEditDate
LastEditorUserId
0
OwnerUserId
1521550
ParentId
0
PostTypeId
1
Score
2
ViewCount
1078
LastEditorDisplayName
text
Body
I have a basic understand of the following: <ul> <li>How to read hardware device Data Sheets</li> <li>How hardware devices work in theory</li> <li>What does a device driver do</li> <li>General concepts of C programming</li> <li>Linux OS</li> </ul> I have always believed that if I can understand all the code of a given device driver and can ultimately write the same code from scratch just with the help of above (without looking at the source code), I will be able to get a very good understand of C language and how device drivers work and interact with OS. For me, this would be like a major milestone in my career. So, over the last few years, I have always thought to learn how to write device drivers (mostly for Linux OS). I always start (this has happened at least 6-7 times) with great enthusiasm and pick a few good online resources and read them. I then take an existing driver code from the Linux kernel (say an Ethernet driver code), obtain a datasheet and start to read the driver code but after reading few lines I kind of get confused and then ultimately give up because I could not follow the rest of the code. My Question: I know such a tutorial is too good to be true but I still want to ask - Does anybody know a good resource which explains how a Linux device driver was written from starting with detailed references to data sheet and how the existing line of code related with it and then explaining each function/block of code as to why it exists and what does it do exactly.
Tags
<linux-device-driver>
Title
Understanding Device Driver code with running commmentary
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USmodest
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POUnderstanding Device Driver code with running commmentary
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POUnderstanding Device Driver code with running commmentary
 UserUserId
 USAnshul
 VoteTypeVoteTypeId
 VTFavorite
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.