All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Ron Bianco <ronb@junction.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 8260 - Spurious interrupt when calling __sti()
Date: Wed, 10 Apr 2002 17:25:21 -0400	[thread overview]
Message-ID: <3CB4ADC1.6070007@embeddededge.com> (raw)
In-Reply-To: 000b01c1e0cd$b8f02d30$4d012ac7@warp-speed


Ron Bianco wrote:

> For OpenPIC/EPIC hardware:

The 8260 family doesn't use EPIC.  It has a custom integrated controller.

Your point is taken that in general someone has to ensure devices and
interrupt controllers are properly initialized.  I thought I did this
in the kernel, but perhaps something was missed.  Sometimes, a boot rom
can leave something in a weird state (like the I2C for reading an EEPROM)
that the kernel doesn't always use.

Thanks.


	-- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-04-10 21:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-10 18:30 8260 - Spurious interrupt when calling __sti() Jean-Denis Boyer
2002-04-10 18:33 ` Dan Malek
2002-04-10 20:24   ` Ron Bianco
2002-04-10 21:25     ` Dan Malek [this message]
2002-04-15 18:33       ` Val Henson
2002-04-16 18:58         ` Dan Malek
  -- strict thread matches above, loose matches on Subject: below --
2002-04-10 17:16 Re[2]: " Jean-Denis Boyer
2002-04-10 17:04 ` Dan Malek
2002-04-10 16:31 Jean-Denis Boyer
2002-04-10 15:50 ` Dan Malek
2002-04-09 14:53 Jean-Denis Boyer
2002-04-09 17:09 ` Ricardo Scop
2002-04-09 18:26 ` Dan Malek

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=3CB4ADC1.6070007@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=ronb@junction.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.