From: Gary Thomas <gthomas@cambridge.redhat.com>
To: Grant Edwards <grante@visi.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] RedBoot serial rx interrupts
Date: Sat, 13 Jan 2001 15:13:00 -0000 [thread overview]
Message-ID: <XFMail.20010113161347.gthomas@cambridge.redhat.com> (raw)
In-Reply-To: <20010113163524.A829@visi.com>
On 13-Jan-2001 Grant Edwards wrote:
> 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.
Maybe we should improve this interface to return an indication of
whether the interrupts _were_ on when "isr_lock()" was called to
avoid this in the future. I'll think about it.
>
> 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?
It's not necessary. Interrupts are always off during any system
initialization, so you could just leave this out [and feel safe].
next prev parent reply other threads:[~2001-01-13 15:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-12 15:09 Grant Edwards
2001-01-13 7:17 ` Gary Thomas
2001-01-13 12:37 ` Grant Edwards
2001-01-13 12:52 ` Gary Thomas
2001-01-13 12:57 ` Grant Edwards
2001-01-13 13:45 ` Grant Edwards
2001-01-13 14:11 ` Gary Thomas
2001-01-13 14:31 ` Grant Edwards
2001-01-13 15:13 ` Gary Thomas [this message]
2001-01-13 15:32 ` Grant Edwards
2001-01-15 4:02 ` Nick Garnett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=XFMail.20010113161347.gthomas@cambridge.redhat.com \
--to=gthomas@cambridge.redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=grante@visi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).