68302 IMR init

[russ]

I had the same problem. I also OR the bit. 

It would probably be better that way. Only when this is the first
interrupt configured is it not a problem. 


Joel Sherrill wrote:
> 
> Was there ever any feedback on this?  I am curious if it is needed
> or not.
> 
> --joel
> 
> Antti P Miettinen wrote:
> >
> > Is there a reason for the clock driver just setting IMR, not ORing the
> > TIMER1 bit into IMR? I'm trying to make ^C work for the debugger stub
> > so I have to enable interrupts for a SCC but the clock driver as it is
> > now masks the SCC interrupt.
> >
> > --- c/src/lib/libbsp/m68k/gen68302/clock/ckinit.c~      Tue Jan 11 19:34:20 2000
> > +++ c/src/lib/libbsp/m68k/gen68302/clock/ckinit.c       Mon Aug  7 23:52:17 2000
> > @@ -93,7 +93,7 @@
> >    /*
> >     * Enable TIMER1 interrupts only.
> >     */
> > -  m302.reg.imr  = RBIT_IMR_TIMER1;     /* set 68302 int-mask to allow ints */
> > +  m302.reg.imr |= RBIT_IMR_TIMER1;     /* set 68302 int-mask to allow ints */
> >
> >    atexit( Clock_exit );
> >  }
> >
> > --- c/src/lib/libbsp/m68k/ods68302/clock/ckinit.c~      Tue Jan 11 19:34:20 2000
> > +++ c/src/lib/libbsp/m68k/ods68302/clock/ckinit.c       Mon Aug  7 23:54:08 2000
> > @@ -94,7 +94,7 @@
> >    /*
> >     * Enable TIMER1 interrupts only.
> >     */
> > -  m302.reg.imr  = RBIT_IMR_TIMER1;     /* set 68302 int-mask to allow ints */
> > +  m302.reg.imr |= RBIT_IMR_TIMER1;     /* set 68302 int-mask to allow ints */
> >
> >    atexit( Clock_exit );
> >  }
> 
> --
> Joel Sherrill, Ph.D.             Director of Research & Development
> joel at OARcorp.com                 On-Line Applications Research
> Ask me about RTEMS: a free RTOS  Huntsville AL 35805
>    Support Available             (256) 722-9985