You can find "Linux Device Drivers 3rd Edition" online. That will give you some basics.
Using Openembedded is a bit different.
I have been using Quilt to do patch files.
On 01/20/2010 06:21 AM, Thierry Genovese wrote:
> Hi,
> You might find this blog post quite useful:
> http://www.xora.org.uk/2009/12/10/openembeddedangstrom-kernel-workflow/
> Just replace linux-elphel by linux-omap3-2.6.32 and elphel-10373 by overo.

Also read the Gumstix information on setting up a user.collection similar to the HelloWorld examples. You can then create a local recipe for the kernel and add your patches.

I assume you are writing a driver for a new device connecting to the USB Host in the OMAP? Not a gadget driver. If that question was confusing I can suggest some books for further reading.

Hope this helps.

On Tue, Jan 26, 2010 at 11:29 AM, <david@wegmuller.org> wrote:
I need to write a driver for a specific USB device that will connect to an Overo machine. I have been able to build and install a complete system from sources using bitbake.
I cannot find a good description of how to include my own kernel driver module within the overall build. I've tried using the Makefile included into the kernel source tree but I ran into path issues (both for the compiler and the include files)...
At this point, the smallest of hint would be greatly appreciated!

David Wegmuller
Sent via BlackBerry by AT&T

The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
gumstix-users mailing list

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.