public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jocelyn Mayer <jma@netgem.com>
To: Ben Collins <bcollins@debian.org>
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: 03 Jun 2003 20:11:57 +0200	[thread overview]
Message-ID: <1054663917.4967.99.camel@jma1.dev.netgem.com> (raw)
In-Reply-To: <20030603113636.GX10102@phunnypharm.org>

On Tue, 2003-06-03 at 13:36, Ben Collins wrote:
> On Mon, Jun 02, 2003 at 11:20:32PM +0200, Jocelyn Mayer wrote:
> > On Mon, 2003-06-02 at 22:34, Georg Nikodym wrote:
> > > On 02 Jun 2003 21:36:22 +0200
> > > Jocelyn Mayer <jma@netgem.com> wrote:
> > > 
> > > > ... at least for PPC targets.
> > > 
> > > As a datapoint, works fine for me with my x86 laptop:
> > 
> > Hi,
> > 
> > OK, so it should be an endianness related problem...
> > I didn't test this on a PC because I need (want ?)
> > to always use the same kernel on my Mac & my PC
> > so I can test my patches always in the same conditions.
> > It gives me a start point to investigate...
> 
> No, it's a rescan-scsi-bus.sh issue. Get the script, and execute it.
> Hotplug for 2.4.x scsi is a fantasy. Just so happens it used to work,
> but that "work" used to cause oopses.

Hi,

Thanks for your help, but I think you're wrong:

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...) ?

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...

Regards.

-- 
Jocelyn Mayer <jma@netgem.com>


  reply	other threads:[~2003-06-03 17:57 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 [this message]
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
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=1054663917.4967.99.camel@jma1.dev.netgem.com \
    --to=jma@netgem.com \
    --cc=bcollins@debian.org \
    --cc=georgn@somanetworks.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