public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Collins <bcollins@debian.org>
To: Jocelyn Mayer <jma@netgem.com>
Cc: Georg Nikodym <georgn@somanetworks.com>,
	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 15:26:56 -0400	[thread overview]
Message-ID: <20030603192656.GE10102@phunnypharm.org> (raw)
In-Reply-To: <1054671619.4951.139.camel@jma1.dev.netgem.com>

> - Please take a look at this session:
> First, I reboot the Ibook:

You didn't read a damn thing.

Look, things changed around rc2. They changed because the old way of
sbp2 that allowed sbp2 devices to be detected on module load caused
oopses. It was very buggy and very bad. Even the old logic didn't work
when you loaded sbp2 and _then_ plugged the device in.

I HAVE NOT once said anything about fucking /sbin/hotplug, nor the
kernel's idea of CONFIG_HOTPLUG. I just said "hotplug", which is a
generic term for being able to insert devices after the bus has already
been scanned for them. So stop bring up either of the two previous
notions that you may have.

Your behavior is expected, even if it changed and is inconvient to you.
This time, _really_ read the linux1394-devel mailing list archives. And
just get the damn script and use it. If you had ever really used sbp2
previously and wanted to plug/unplug devices without unloading/reloading
sbp2.o, you would already realize that the script was a must for 2.4.
Then again, if you had been unloading/loading sbp2 you would have also
hit the oopses I mentioned before.

-- 
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo       - http://www.deqo.com/

  reply	other threads:[~2003-06-03 20:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-02 19:36 [BUG] ieee1394 sbp2 driver is broken for kernel >= 2.4.21-rc2 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
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 [this message]
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=20030603192656.GE10102@phunnypharm.org \
    --to=bcollins@debian.org \
    --cc=georgn@somanetworks.com \
    --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