Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Device Driver & Interrupts
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
John Kofler  
View profile  
 More options Nov 8 2003, 8:29 am
Newsgroups: linux.dev.kernel
From: "John Kofler" <eda...@pacbell.net>
Date: Sat, 08 Nov 2003 08:26:57 GMT
Local: Sat, Nov 8 2003 3:26 am
Subject: Device Driver & Interrupts
Hi.  I've done a lot of RTOS (VxWorks and VRTX) and NON-RTOS work creating
device drivers; i.e., working at the hardware interfacing level.  I've also
done some real-time UNIX work and some Linux Embedded application
development, but I've never worked at the device driver level w/ either of
these OS's.  In general, I have been told that it is much more difficult to
interface to devices via Linux and it takes much longer.  Where I use to
work, the guys have a lot of war stories of how long it took to do the
development at this level and I am about to step into it myself.

Is there a general rule, say it takes me a week to write the software to a
SEEPROM in an RTOS would it take twice as long (or longer) with Linux?  For
example, I have a friend that was given a sample device driver to a device
very similiar to a SEEPROM and it took him a little over 3 weeks to complete
(and this is after inheriting it from the guy that was working on it).  To
me using VxWorks, I believe I could have pumped this out in a week.

Secondly, I need to be able to sit on an interrupt from a UART FIFO and
stuff characters into to it everytime the flag says half-empty (hi-speed
stuff).  I do not want to 'poll' this, I want to write an ISR to handle
this.  Is this difficult to do in Linux and is there any place that I can
find an example of this type of work?

Thanks.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »