From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: Ingo Flaschberger <if@xip.at>
Cc: linux-scsi@vger.kernel.org, "Martin K. Petersen" <mkp@mkp.net>
Subject: Re: cpqfc
Date: Mon, 13 Feb 2006 10:45:28 +0100 [thread overview]
Message-ID: <200602131045.34949@bilbo.math.uni-mannheim.de> (raw)
In-Reply-To: <Pine.GSO.4.64.0602101220450.2743@filebunker.xip.at>
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
Am Freitag, 10. Februar 2006 12:26 schrieben Sie:
>Hello again,
>
>I have not received any answer regarding implementation of a new driver
>for the cpqfc adapter.
>
>In one week I will start to port the old 2.4 driver to 2.6; with all its
>"not nice" code, because it works!
It will not (really). cpqfc uses many functions not longer available in 2.6 so
you will not even get it compile for a long time.
If you still want to do something like that you might want to have a look on
http://opensource.sf-tec.de/repos/cpqfc/ where I put my changes to this
driver online. The 2.6-branch will not compile by now but it is much cleaner
than the code that was in 2.6.
Eike
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-02-13 9:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 17:46 cpqfc gone - all compay RA4X00 Array now useless in linux? Ingo Flaschberger
2006-02-06 18:23 ` Rolf Eike Beer
2006-02-06 18:38 ` Ingo Flaschberger
2006-02-07 7:55 ` Rolf Eike Beer
2006-02-07 10:05 ` Booting from or using a Compaq RA4100 Array Ingo Flaschberger
2006-02-10 11:26 ` cpqfc Ingo Flaschberger
2006-02-10 12:59 ` cpqfc Christoph Hellwig
2006-02-10 19:04 ` cpqfc Martin K. Petersen
2006-02-13 9:45 ` Rolf Eike Beer [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-02 15:09 cpqfc lance dillon
2005-12-01 15:03 cpqfc lance dillon
2005-12-01 15:16 ` cpqfc Rolf Eike Beer
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=200602131045.34949@bilbo.math.uni-mannheim.de \
--to=eike-kernel@sf-tec.de \
--cc=if@xip.at \
--cc=linux-scsi@vger.kernel.org \
--cc=mkp@mkp.net \
/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.