Can't Build New Device Driver

[Chris Johns]

Robert S. Grimes wrote:
> Angelo Fraietta wrote:
>> Robert S. Grimes wrote:
>>   
>> 1 - Developing the Device Driver
>> 2 - Including it in the main RTEMS tree so it will build when you build
>> RTEMS
>>
>> If it is the former, I would not worry about including in the RTEMS tree
>> until you have it working. Just develop the device driver separately and
>> link it with your app. This way you don't need to worry about bootstrap,
>> automake, and the likes. Once you have the device driver working, then
>> you can work at including it in the RTEMS tree.
>>   
> I had not even considered this option!  It certainly sounds like a way 
> of avoiding all that stuff I don't understand.  It certainly would help 
> with respect to keeping my project on schedule!  It also sounds a wise 
> approach for a couple of drivers I'll need to do that are custom, 
> proprietary, and otherwise not of interest to the community.
> 

This is excellent advice. I develop all new drivers this way plus I develop 
the test code I use to test the driver as the application. After the driver 
ends up in RTEMS I still have a way to test it.

Regards
Chris