public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Collins <bcollins@debian.org>
To: Bob Gill <gillb4@telusplanet.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: SBP2 and IEEE1394 in 2.5.74
Date: Tue, 8 Jul 2003 15:59:45 -0400	[thread overview]
Message-ID: <20030708195945.GE5830@phunnypharm.org> (raw)
In-Reply-To: <1057698811.6911.8.camel@localhost.localdomain>

On Tue, Jul 08, 2003 at 03:13:31PM -0600, Bob Gill wrote:
> I have at long last had reasonable success building 2.5.74 (I configured
> ACPI out, and along with it went scheduling_while_atomic).  The only
> issue now is firewire, specifically modules SBP2 and IEEE1394.  I looked
> at the source and found it to be amazingly small (not many files and
> none larger that about 30 bytes).  Is there any timeline when these will
> be joining the kernel?  I would switch over to using 2.5.X tomorrow if
> these could be completed/working.  Is there a 2.4.X retrograde patch
> that could be applied to make these work before the complete 2.5.X
> version is completed?  Thanks,

ieee1394, sbp2 and all of the subsystem is in working order. What
problem are you having?

If all the files in drivers/ieee1394 are less than 30 bytes, I think you
have some other problem.

Also, 2.5.74 stock has a problem in sbp2.c. It needs the linux/pci.h
include added (already fixed in Linus' tree).

-- 
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-07-08 21:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-08 21:13 SBP2 and IEEE1394 in 2.5.74 Bob Gill
2003-07-08 19:59 ` Ben Collins [this message]

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=20030708195945.GE5830@phunnypharm.org \
    --to=bcollins@debian.org \
    --cc=gillb4@telusplanet.net \
    --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