My own driver

[Joel Sherrill <joel@OARcorp.com>]

Adam Piotrowski wrote:
>>You seem to be on the right track but you didn't mention what type of
>>device you are writing a driver for.  At least serial ports,
>>disks/non-volatile storage for filesystems, real-time clocks, and
>>network interface controllers have frameworks to adhere to in
>>order to plug into standard subsystems.
>>
>>What tpe of device is it?  Then we can point you to a good example
>>or maybe a template for the device driver.
>>
>>For example, a clock tick or serial port driver can often just be a
>>few lines of BSP specific glue code.
>>
> 
> 
> First, I try understood this system and driver model. I planed write simple
> memory driver (driver that will remember what I write, and send back that
> information when I read), but the final project will be driver for Flash
> memory (non-volatile storage for filesystems). In documentation I found
> information that somewhere in rtems is driver for non-volatine memory but I
> couldn't have found it.

Then you do have to adhere to a framework.  In this case, I would
probably start by looking at the ram disk driver as an example block 
device driver.

Does anyone have a better place for him to look?

--joel