From: Martin Zwickel <martin.zwickel@technotrend.de>
To: linux-kernel@vger.kernel.org
Subject: net_device: set_multicast_list called from interrupt?
Date: Mon, 4 Oct 2004 17:26:21 +0200 [thread overview]
Message-ID: <20041004172621.3dd8945f@phoebee> (raw)
[-- Attachment #1: Type: text/plain, Size: 698 bytes --]
Hi there!
I don't know if this is the right place, but I hope so.
I wrote a network-driver years ago for the 2.4er kernel's.
Now I ported it to the 2.6er kernel but I get some problems because
set_multicast_list is called from an interrupt and my driver want's to
free/allocate some memory.
Why did the driver work under 2.4, and now stops running on 2.6?
I had a look at http://lwn.net/Articles/30107/:
Driver porting: Network drivers
but there was nothing about newly implemented soft-interrupts.
Thanks,
Martin
--
MyExcuse:
The cord jumped over and hit the power switch.
Martin Zwickel <martin.zwickel@technotrend.de>
Research & Development
TechnoTrend AG <http://www.technotrend.de>
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-10-04 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 15:26 Martin Zwickel [this message]
2004-10-04 15:35 ` net_device: set_multicast_list called from interrupt? Martin Zwickel
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=20041004172621.3dd8945f@phoebee \
--to=martin.zwickel@technotrend.de \
--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 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.