Registers are not shared. However, interrupts are. But I can modify
the ISR to determine which device is generating the interrupt and
process it accordingly.
John
On Fri, 2 Nov 2007 14:47:41 -0400, "Don Burn"
<burn@xxxxxxxxxxxxxxxxxxxx> wrote:
If you device has nothing shared, i.e. no control registers or interrupts
look at mf.sys see http://msdn2.microsoft.com/en-us/library/ms794938.aspx.
If things are shared, you need to create a bus driver and then provide a
device interface for the shared functionality.
Re: [PATCH] Documentation: Make fujitsu/frv/kernel-ABI.txt 80 columns wide ... -The internal FRV kernel ABI is not quite the same as the userspace ABI. ... -most of them do not have any scratch registers, thus requiring at least one general purpose ... +single-stepping will blithely go on stepping into things like interrupts.... -to read and once to write), we don't actually disable interrupts at all if we don't have to. ... (Linux-Kernel)
Re: bits 32 oddities in NASM ...registers.... But, since dosinterrupts are 16-bit code, Nasm needs to be generating 16-bit code to operate there. ... without resorting to the C library or the evil Win32 API.... (alt.lang.asm)
Re: Strange problem with semFlush/semTake ... As I stated in one of my previous messages, the cmpTime task takes only ... As for the use of semGive instead of semFlush,... If the ISR fires, let's say, while your task is ... I am using binary semaphores to sync between interrupts and tasks and I ... (comp.os.vxworks)
Re: arm-elf-gcc building erroneous code for ISR (long posting) ... > example from Keil which should demonstrate the use of interrupts and of ... > essentially an empty loop now) and simply let the timer ISR toggle a LED ... > suspect a bug in gcc.... this include the correct subs pc,lr,#4 that performs a return from interrupt ... (comp.arch.embedded)