From: "David S. Miller" <davem@davemloft.net>
To: Martin Wilck <martin.wilck@fujitsu-siemens.com>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: SIOCGIFMAP silently broken?
Date: Mon, 31 Jan 2005 11:46:40 -0800 [thread overview]
Message-ID: <20050131114640.7e002652.davem@davemloft.net> (raw)
In-Reply-To: <41FE4745.4020003@fujitsu-siemens.com>
On Mon, 31 Jan 2005 15:57:09 +0100
Martin Wilck <martin.wilck@fujitsu-siemens.com> wrote:
> In both cases, the netdev->irq field isn't used anymore; perhaps it
> should be officially deprecated and/or removed?
It is used for explicitly setting the IRQ value on hardware
where doing so automatically via probing may not be %100
reliable, such as on ISA.
Another way to do what you're trying to do is to look for
the string name of the device you are interested in within
the output of /proc/interrupts.
prev parent reply other threads:[~2005-01-31 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-31 14:57 SIOCGIFMAP silently broken? Martin Wilck
2005-01-31 19:46 ` David S. Miller [this message]
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=20050131114640.7e002652.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.wilck@fujitsu-siemens.com \
--cc=netdev@oss.sgi.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