Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
soc:2008:balajirrao:project_plan:start [2008/05/19 16:36] mdc |
soc:2008:balajirrao:project_plan:start [2008/06/13 03:30] (current) balajirrao |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Balaji Rao: Project Plan, USB Support ====== | ====== Balaji Rao: Project Plan, USB Support ====== | ||
| - | ===== Summary ===== | + | ===== Project Plan ==== |
| - | ===== Outline ===== | + | ==== Summary ==== |
| - | ===== Milestones and Timeline ===== | + | This project will enable gPXE to use USB Ethernet Adapters. This includes, |
| + | * Adding USB support to gPXE. | ||
| + | * Writing a network device driver for an USB Ethernet Adapter. | ||
| + | ==== Outline ==== | ||
| + | Adding USB support to gPXE mainly has two parts. | ||
| + | * Support for the USB protocol itself. | ||
| + | * Write a device driver for a USB host controller. | ||
| + | * Write a USB device driver for a USB Ethernet card. | ||
| + | === USB Protocol support === | ||
| + | USB protocol support involves adding routines to create communication structures as defined by the protocol specification. Device drivers for actual USB devices shall use these routines to communicate with their devices. The USB protocol layer also handles USB device configuration which involves assigning addresses to devices and preparing them for use. | ||
| + | |||
| + | === USB Host controller support === | ||
| + | An USB host controller is a device, mostly available as a PCI card which talks to USB devices connected to it using instructions from the USB protocol layer. Two commonly used variants of USB Host Controllers exist. They are UHCI (Universal Host Controller Interface) supporting Full Speed (12Mbps) and Low Speed (1.5 Mbps) devices and EHCI (Enhanced Host Controller Interface) in addition to Full Speed and Low Speed devices, supports devices operating at 480 Mbps, called High Speed devices. | ||
| + | |||
| + | === Device Driver for a USB NIC === | ||
| + | I propose to follow the Linux Kernel model here - to split the device driver into a generic driver and a device specific mini driver. | ||
| + | |||
| + | UCHI controller support will be done first. EHCI support is seen as a later (stretch ?) goal. | ||
| + | |||
| + | ==== Milestones ==== | ||
| + | |||
| + | * USB protocol layer completed. | ||
| + | * USB host controller layer completed. | ||
| + | * USB NIC driver completed. | ||
| + | |||
| + | ==== Timeline ==== | ||
| + | |||
| + | Here's a rough timeline. | ||
| + | |||
| + | === Week 1, 2 === | ||
| + | * Write a PCI driver fpr UHCI controller. Write support for control and bulk urbs. | ||
| + | |||
| + | === Week 3, 4=== | ||
| + | * Write a driver for dm9601 usb ethernet adapter. Factor out generic USB networking code out of dm9601 and write a pegasus usbnet driver. | ||
| + | |||
| + | === Week 5 & 6 === | ||
| + | * Clean up and sanitize the uhci source. This includes proper lifecycle management of urbs and correct error handling across all control paths. | ||
| + | |||
| + | === Week 7, 8 & 9 === | ||
| + | * Write a PCI driver for EHCI controller along with schedule management code. | ||
| + | |||
| + | === Week 10 and hence === | ||
| + | * Debugging, optimization etc. | ||
