From: Matt Porter <mporter@mvista.com>
To: Ronald Wahl <rwa@peppercon.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: iounmap
Date: Fri, 4 Aug 2000 07:19:54 -0700 [thread overview]
Message-ID: <20000804071954.C892@beef.az.mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0008041003040.653-100000@goliath.issistance.de>; from rwa@peppercon.de on Fri, Aug 04, 2000 at 10:06:26AM +0200
On Fri, Aug 04, 2000 at 10:06:26AM +0200, Ronald Wahl wrote:
> On Thu, 3 Aug 2000, Matt Porter wrote:
>
> > On Thu, Aug 03, 2000 at 02:44:12PM +0200, Geert Uytterhoeven wrote:
> > >
> > > On Thu, 3 Aug 2000, Ronald Wahl wrote:
> > > > I'm currently writing a device driver for an pci controller and have to
> > > > map very large amounts of pci memory and i/o ranges via ioremap. The
> > > > problem is that there is no iounmap and ioremap returns NULL after some
> > > > insmod/rmmod cycles. When gets this implemented?
> > >
> > > When someone steals some spare time and writes the code.
> >
> > Done. The hot swap PCI kernel patches from MCG have iounmap implemented.
> > Very useful when ripping a PCI peripheral out of its slot. :)
> >
> > See them at http://www.mcg.mot.com/linux under HA Linux/Downloads.
>
> Call me blind, but I havn't seen an implementation of iounmap in these
> patches.
Whoops, sorry. When I was at MCG I know another engineer did an iounmap
implementation for HA support. I thought it was in those patches... :-/
--
Matt Porter
MontaVista Software, Inc.
mporter@mvista.com
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-04 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-03 8:00 iounmap Ronald Wahl
2000-08-03 12:44 ` iounmap Geert Uytterhoeven
2000-08-03 22:59 ` iounmap Matt Porter
2000-08-04 8:06 ` iounmap Ronald Wahl
2000-08-04 14:19 ` Matt Porter [this message]
2000-08-04 2:13 ` iounmap Paul Mackerras
2000-08-04 8:08 ` iounmap Ronald Wahl
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=20000804071954.C892@beef.az.mvista.com \
--to=mporter@mvista.com \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=rwa@peppercon.de \
/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;
as well as URLs for NNTP newsgroup(s).