From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Nils Rennebarth <nils.rennebarth@funkwerk-ec.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
"Kok, Auke" <auke-jan.h.kok@intel.com>,
Marian Balakowicz <m8@semihalf.com>,
"linux-pci@atrey.karlin.mff.cuni.cz"
<linux-pci@atrey.karlin.mff.cuni.cz>,
"len.brown@intel.com" <len.brown@intel.com>,
NetDev <netdev@vger.kernel.org>
Subject: Re: quirk_e100_interrupt() called too early
Date: Mon, 02 Jul 2007 12:03:27 -0700 [thread overview]
Message-ID: <46894BFF.70405@intel.com> (raw)
In-Reply-To: <4688B258.4000501@funkwerk-ec.com>
Nils Rennebarth wrote:
> Bjorn Helgaas wrote:
>> On Thursday 28 June 2007 10:01:08 am Kok, Auke wrote:
>> I copied Nils Rennebarth, who originally reported the bug:
>> http://bugzilla.kernel.org/show_bug.cgi?id=5918
>> in case he can test your patch.
>
> Most of the embedded boards we now work with appear to exhibit the same
> behaviour: During boot the
>
> Firmware left 0000:01:05.0 e100 interrupts enabled, disabling
>
> message appears for all four e100 nics. (The mainboard is a em-8510A
> btw.) When I have time I could try if the quirk still works with the
> mentioned patch, but I am quite busy with other things at the moment.
well, we're too late for 2.6.22 I think so you have some time. However I'd like
to make sure we can get this in with 2.6.23. Alternatively, someone could always
send me one of these boards ;)
Thanks for taking the time to test
Auke
next prev parent reply other threads:[~2007-07-02 19:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4683A80F.5020605@semihalf.com>
2007-06-28 16:01 ` quirk_e100_interrupt() called too early Kok, Auke
2007-06-29 2:07 ` Bjorn Helgaas
2007-07-02 8:07 ` Nils Rennebarth
2007-07-02 19:03 ` Kok, Auke [this message]
2007-07-03 9:00 ` Marian Balakowicz
2007-07-03 9:03 ` [PATCH] PCI: " Marian Balakowicz
2007-07-17 17:21 ` patch pci-quirk_e100_interrupt-called-too-early.patch added to gregkh-2.6 tree gregkh
2007-07-17 17:26 ` Kok, Auke
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=46894BFF.70405@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=bjorn.helgaas@hp.com \
--cc=len.brown@intel.com \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=m8@semihalf.com \
--cc=netdev@vger.kernel.org \
--cc=nils.rennebarth@funkwerk-ec.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 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.