From: Georg Nikodym <georgn@somanetworks.com>
To: Jocelyn Mayer <jma@netgem.com>
Cc: Ben Collins <bcollins@debian.org>,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] ieee1394 sbp2 driver is broken for kernel >= 2.4.21-rc2
Date: Tue, 3 Jun 2003 14:27:12 -0400 [thread overview]
Message-ID: <20030603142712.6e7da879.georgn@somanetworks.com> (raw)
In-Reply-To: <1054663917.4967.99.camel@jma1.dev.netgem.com>
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
On 03 Jun 2003 20:11:57 +0200
Jocelyn Mayer <jma@netgem.com> wrote:
> Thanks for your help, but I think you're wrong:
I doubt it. Ben's one of the authorities on this stuff.
> First, I never trust hotplug or other tools like this:
> I do all insmod by hand, so I know all drivers have been loaded.
> What is hotplug supposed to do (but wasn't in previous driver
> version...) ?
I compile this stuff directly into my kernel. Doesn't make a
difference.
> The second thing I see is that it used to work,
> before 2.4.21-rc2. The only difference is in the kernel driver,
> so it should work with no user-space tool, as it used to.
> If not, the driver is now buggy...
Well, I've _always_ needed either rescan-scsi-bus.sh (or scsiadd -s
since I switched to Debian). If there's some magic that you've been
doing that obviates this requirement, we're all ears.
-g
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-06-03 18:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 19:36 Jocelyn Mayer
2003-06-02 20:34 ` Georg Nikodym
2003-06-02 21:20 ` Jocelyn Mayer
2003-06-03 11:36 ` Ben Collins
2003-06-03 18:11 ` Jocelyn Mayer
2003-06-03 18:27 ` Georg Nikodym [this message]
2003-06-03 19:01 ` Jocelyn Mayer
2003-06-03 19:34 ` Richard B. Johnson
2003-06-03 18:54 ` Ben Collins
2003-06-03 20:20 ` Jocelyn Mayer
2003-06-03 19:26 ` Ben Collins
2003-06-03 21:12 ` Jocelyn Mayer
2003-06-03 19:28 ` Ben Collins
2003-06-03 20:25 ` Matthew Dharm
2003-06-03 21:12 ` Jocelyn Mayer
2003-06-03 23:01 ` Matthew Dharm
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=20030603142712.6e7da879.georgn@somanetworks.com \
--to=georgn@somanetworks.com \
--cc=bcollins@debian.org \
--cc=jma@netgem.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®