Accessing hardware under RTEMS

[Jake Janovetz]

I'm using RTEMS in a few embedded applications and I think I
prefer the non-device-driver method for LEDs, hardware registers,
etc.  Specifically, I have DSPs and FPGAs that need talkin' to, 
and I don't use device drivers for them.  I use special procedures
that are called to download and/or communicate.

I tried putting together a device driver, but it didn't really
offer me any advantage.  I think the advantage would be in reuse
of a driver interface.  That is, everyone expects something like
/dev/console to be available -- it's a nice standard interface.
Who cares about my proprietary FPGA interface??

The memories, on the other hand, may be better handled with a 
device driver.  I don't about this one, though.

    Jake


On Wed, Sep 13, 2000 at 08:56:31AM -0700, OUTWATER wrote:
> Greetings all - 
> 
> I have an application in which I need to provide contol of miscellaneous 
> peripheral devices such as:
> 
> LEDs
> Memories (SRAM, FIFO)
> Hardware control registers
> 
> It seems like the best/elegant/preferred way to do this is via RTEMS device 
> drivers.
> 
> Opinions?
> 
> If a device driver is the way to go, is there a basic example of one somewhere 
> that I could use as a starting point?
> 
> Thanks!
> Keith

-- 
   janovetz at uiuc.edu    | How can it be that mathematics, being after all a 
 University of Illinois | product of human thought independent of experience,
                        | is so admirably adapted to the objects of reality?
        PP-ASEL         |                                  - Albert Einstein

Disclaimer: The policies of this University certainly do not reflect my
            own opinions, objectives, or agenda.