From: Christian Trefzer <ctrefzer@web.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: fdomain SCSI driver broken in 2.6 series?
Date: Tue, 07 Jun 2005 22:17:17 +0200 [thread overview]
Message-ID: <42A600CD.6090408@web.de> (raw)
In-Reply-To: <1118161118.26661.19.camel@localhost.localdomain>
Alan Cox wrote:
> I did a bit of cleanup on it during 2.5 to get it to compile and look
> right, and it did work for a while when I had the card, but the scsi
> changed a lot after that. You are the first fdomain user I've seen in
> years so I suspect you are on your own for fixing it too tho I can try
> and help a bit.
>
Guess I'm the only person insane enough to try and build a DSL router
based on 2.6 with ancient SCSI disks on an ISA controller, but I just
can't live without some of the features anymore which 2.4 still lacks.
In the meantime, I worked around the Oops by using a tiny disk on the
onboard IDE controller, but I wouldn't quite call removing the card a
fix for the problem.
The thing is, I have no real experience in C programming, although I
sometimes read a little kernel source code and stuff. Right now I have a
bit of trouble with my studies, but once that's settled I can do some
reading about SCSI, Linux, the works. Doesn't seem to be anyone using
2.6 with Future Domain cards anyway, so I'm not in a hurry. But just for
completeness, it would be nice to have that driver cleaned up. It's in
Linux' tree, after all. I'll build a testing box with ISA bus some time
soon and try some debugging.
Thanks for your time : )
prev parent reply other threads:[~2005-06-07 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-30 11:34 fdomain SCSI driver broken in 2.6 series? Christian Trefzer
2005-06-07 16:18 ` Alan Cox
2005-06-07 20:17 ` Christian Trefzer [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=42A600CD.6090408@web.de \
--to=ctrefzer@web.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.