From: Ben Collins <bcollins@debian.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
linux-scsi@vger.kernel.org,
linux1394-devel@lists.sourceforge.net
Subject: Re: sbp2: modprobe -r fails, module allegedly in use
Date: Sun, 10 Jul 2005 13:46:43 -0400 [thread overview]
Message-ID: <20050710174643.GG14956@phunnypharm.org> (raw)
In-Reply-To: <20050710174054.GA28623@infradead.org>
On Sun, Jul 10, 2005 at 06:40:54PM +0100, Christoph Hellwig wrote:
> On Sun, Jul 10, 2005 at 11:31:26AM -0400, Ben Collins wrote:
> > Yeah, seems like every two months we have to change sbp2 to accomodate
> > changes to the scsi layers whole reference scheme which never seems
> > simple, and never stays the same.
>
> While the implementation has changed a little the exposed interface
> never changed at all since before 2.6.0.
The exposed implementation might not have, but atleast 3 times now, since
the driver model started being used, I've had to change the way I use the
exposed implementation in order to get bean counting right with the device
and host devices.
Prior, we were using one scsi host per ieee1394 host, with each sbp2
device being one device and even supporting real LUN's to make things as
close to looking like a real scsi host as possible.
Had to ditch all that and do one-host-per-device like USB does in order
save myself all the headache involved. This kind of sucks because the
plug/unplug can quickly increment the scsi-host counter to a point where
things like cdrecord don't work with firewire cd/dvd/rw devices anymore
(until a reboot or the scsi module is removed/inserted). But that's a
whole different issue :)
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
SwissDisk - http://www.swissdisk.com/
next prev parent reply other threads:[~2005-07-10 17:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-10 14:42 sbp2: modprobe -r fails, module allegedly in use Stefan Richter
2005-07-10 15:07 ` Stefan Richter
2005-07-10 15:31 ` Ben Collins
2005-07-10 17:40 ` Christoph Hellwig
2005-07-10 17:46 ` Ben Collins [this message]
2005-07-10 17:49 ` Christoph Hellwig
2005-07-10 17:52 ` Ben Collins
2005-07-10 17:29 ` James Bottomley
2005-07-10 17:37 ` Ben Collins
2005-07-10 17:51 ` Stefan Richter
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=20050710174643.GG14956@phunnypharm.org \
--to=bcollins@debian.org \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.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