public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: David Woodhouse <dwmw2@infradead.org>
Cc: lkml <linux-kernel@vger.kernel.org>, David Hinds <dhinds@sonic.net>
Subject: Re: [patch] ip autoconfig for PCMCIA NICs
Date: Fri, 19 Oct 2001 15:33:30 -0700	[thread overview]
Message-ID: <3BD0AA3A.D3C61F0D@zip.com.au> (raw)
In-Reply-To: <3BD092A6.26A1CFE9@zip.com.au>, <3BD092A6.26A1CFE9@zip.com.au> <29471.1003530166@redhat.com>

David Woodhouse wrote:
> 
> akpm@zip.com.au said:
> >  Also, yenta_open() currently defers device initialisation to keventd,
> > so there is a good chance that cardbus init hasn't completed by the
> > time we hit ip autoconf, so the yenta_open_bh functionality is made
> > synchronous.
> 
> That was async at Linus' request - if we register the irq early, some
> boards die in an interrupt storm. Linux is currently fairly crap at
> noticing and recovering from interrupt storms.
> 

So any change in this area is untestable in the 2.4 context.  Sigh.

But how can the current code prevent IRQ problems?  AFAICT it just
delays the yenta_open_bh() operations by a short-but-random time
interval.

Should the IRQ be registered _after_ the call to cardbus_register()
when, presumably, the hardware is set up and has negated the IRQ
signal?


-

  reply	other threads:[~2001-10-19 22:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-19 20:52 [patch] ip autoconfig for PCMCIA NICs Andrew Morton
2001-10-19 22:22 ` David Woodhouse
2001-10-19 22:33   ` Andrew Morton [this message]
2001-10-20  3:24 ` David Hinds

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=3BD0AA3A.D3C61F0D@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=dhinds@sonic.net \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /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