Date: Sat, 23 Jun 2001 15:43:47 +0100 From: j mckitrick <jcm@FreeBSD-uk.eu.org> To: freebsd-hackers@freebsd.org Subject: Re: how to invalidate scsi connection to driver module Message-ID: <20010623154347.A90902@dogma.freebsd-uk.eu.org> In-Reply-To: <20010623145429.D29940@ringworld.oblivion.bg>; from roam@orbitel.bg on Sat, Jun 23, 2001 at 02:54:29PM %2B0300 References: <20010622183909.A60256@dogma.freebsd-uk.eu.org> <20010623145429.D29940@ringworld.oblivion.bg>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jun 23, 2001 at 02:54:29PM +0300, Peter Pentchev wrote: | On Fri, Jun 22, 2001 at 06:39:09PM +0100, j mckitrick wrote: | > | > Here is the code for a scsi removable media drive. If this is to become a | > module, the cam/scsi attachment must be removed. I have tried calling | > cam_sim_free() and xpt_bus_deregister() but when the module is reloaded, the | > cam system assigns the next higher minor device number, and then crashes | > when accessed. Any ideas here how to reset cam to a state where it knows | > nothing about the device? | | I might be dead wrong here, but I think the different *types* of SCSI | devices are compiled statically in the kernel, and not intended to be | unloaded. See the kernel options 'da', 'cd', 'pass' et al. | | What I mean is that what you are trying to do might not be even possible, | at least with the current state of the CAM code. And of course, I may | have completely misunderstood what you are trying to do :) Ah, i see what you mean. Hmmm. could be a problem. Oh, well. Loadable is good enough, if that's the best we can do. Unloadable would be nice, but maybe impractical right now. Jonathon -- Microsoft complaining about the source license used by Linux is like the event horizon calling the kettle black. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010623154347.A90902>