How difficult is it to write a device driver for ethernet card?
closed account (ypfz3TCk)
On a scale of 1 to 10 if i wanted to write a device driver for a wired ethernet card, say a Realtek or Broadcom, how much code are we talking about - roughly? How long do you reckon such a project would take working from scratch?
Im thinking about doing this for educational reasons but dont want to bite off more than i can chew.
Im thinking about doing this for educational reasons but dont want to bite off more than i can chew.
closed account (zb0S216C)
Developing drivers is risky business because it involves accessing sensitive data within the kernel. One wrong slip, and you're screwed. The amount of time to develop a driver has many contributing factors such as:
- Complexity of the driver
- The amount of people working on the driver
- The amount of time you spend debugging
- Providing support for various operating system architectures
Here's an interesting article: http://www.codeproject.com/Articles/9504/Driver-Development-Part-1-Introduction-to-Drivers
Wazzak
- Complexity of the driver
- The amount of people working on the driver
- The amount of time you spend debugging
- Providing support for various operating system architectures
Here's an interesting article: http://www.codeproject.com/Articles/9504/Driver-Development-Part-1-Introduction-to-Drivers
Wazzak
Last edited on
It is not difficult to write a device driver if you know its specifications. There are special books on programming device drives for example under Windows.
Last edited on
Topic archived. No new replies allowed.