[2756] in linux-net channel archive
Re: Network module autoprobing in 1.3
daemon@ATHENA.MIT.EDU (Martin Kraemer)
Wed May 1 12:46:26 1996
To: gpg109@rsphy6.anu.edu.au (Paul Gortmaker)
Date: Tue, 30 Apr 1996 15:44:00 +0200 (MET DST)
From: Martin Kraemer <Martin.Kraemer@mch.sni.de>
Cc: apenwarr@foxnet.net, linux-net@vger.rutgers.edu
In-Reply-To: <9604300133.AA09136@rsphy6.anu.edu.au> from Paul Gortmaker at "Apr 30, 96 11:33:02 am"
Paul Gortmaker wrote,...
> 2) In a modular configuration, a device is only protected by
> address allocation while its driver is loaded/resident. In other
> words, a device is only protected from other device probes after it has
> been insmod-ed and thus called request_region() to protect itself.
But why doesn't the autoprobe code protect itself with request_region()
as well? Any regions which have been allocated already can hardly be
candidates for a device-still-to-be-loaded!!?!
If autoprobing for said region fails, the device can release the
region again. If it doesn't get access in the first place,
autoprobing continues with the remaining address choices.
Martin
--
| S I E M E N S | Martin.Kraemer@mch.sni.de | Siemens Nixdorf
| ------------- | Voice: +49-89-636-46021 | Informationssysteme AG
| N I X D O R F | FAX: +49-89-636-44994 | 81730 Munich, Germany
~~~~~~~~~~~~~~~~My opinions only, of course; pgp key available on request
