Re: Firewire/SBP2 and the -mm tree

[Rogério Brito <rbrito@ime.usp.br>]

Hi, Stefan.

Sorry for the late reply, but I am about to be submitted to a surgery and
had to make some health tests, which prevented me from trying to debug
things regarding this problem.

On Jul 02 2005, Stefan Richter wrote:
> That is what usually happens. But the sbp2 related diffs between 2.6.13 
> and linux1394 are not an update by linux1394 but rather a rewrite by the 
> scsi folk.

Ok, I see.

> Unfortunately, that rewrite was not tested by the linux1394 team. (And
> was therefore not checked in at svn.linux1394.org. Lack of manpower was
> one factor.) So, applying the sbp2 portion of your diff is a back-out,
> not an update.

Well, it surely looked like an update, since the revision number of the svn
repo was higher than what is in the kernel right now. But that's from the
standpoint from a luser (me).

> I have a question: Do you need _both_ the sbp2 back-out and ieee1394's
> disable_irm parameter, or only one of them?

With 2.6.13-rc1, I just need the sbp2.[ch] files patched from trunk and
everything works fine (that is, BTW, what I am using right now).

But with the recently released 2.6.13-rc1-mm1, patching the sbp2.[ch] files
isn't sufficient anymore (i.e., I get results similar to what I had when I
first started this thread).

I have not yet had time to pass the disable_irm parameter to a -rc1-mm1
kernel (patched or not), but will do (or anything else, if you guys want me
to) so that we can have Linus's kernel 2.6.13 working as 2.6.12 did (but
with the nice improvements to other subsystems also). :-)


Thank you very much, Rogério.

-- 
Rogério Brito : rbrito@ime.usp.br : http://www.ime.usp.br/~rbrito
Homepage of the algorithms package : http://algorithms.berlios.de
Homepage on freshmeat:  http://freshmeat.net/projects/algorithms/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/