From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Edwards To: Gary Thomas Cc: ecos-discuss@sources.redhat.com Subject: Re: [ECOS] RedBoot serial rx interrupts Date: Sat, 13 Jan 2001 14:31:00 -0000 Message-id: <20010113163524.A829@visi.com> References: <20010113154902.A32172@visi.com> X-SW-Source: 2001-01/msg00225.html On Sat, Jan 13, 2001 at 03:11:34PM -0700, Gary Thomas wrote: > This looks OK and I think I mispoke before. GDB_BREAK can and will > be set, even for RAM based RedBoot. Does that mean that it's normal for RedBoot to unmask serial interrupts? > However, interrupts should never actually get turned on in the > RedBoot environment. The only place where interrupts are > enabled is in the path where the kernel scheduler is enabled. > > Are you seeing otherwise? If so, where? My Ethernet driver initialization routine ends up calling cyg_drv_isr_lock() and cyg_drv_isr_unlock(). The latter enables interrupts. I can add #defines to my driver code to turn those into noops unless CYGPKG_NET is defined. This raises the question: is it OK to call those two routines during network device initialization? -- Grant Edwards grante@visi.com