linux-kernel - RE: Interphase Tachyon drivers missing.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <E8C008223DD5F64485DFBDF6D4B7F71D023BAE21@msgswbmnmsp25.wellsfargo.com>
Date:	Wed, 13 Dec 2006 10:51:29 -0600
From:	<Greg.Chandler@...lsfargo.com>
To:	<eike-kernel@...tec.de>
Cc:	<linux-kernel@...r.kernel.org>, <mkp@....net>
Subject: RE: Interphase Tachyon drivers missing.

I'm not sure about the driver being cpqfc, I know in 2.6.0 & 1 the
driver was definitely iphase.c/h/o
I do know the chipset was used by almost everyone, Compaq/HP/DEC and
Interphase's namebrand cards.

I also know that the driver is still working in 2.4.33 my slackware 11
default kernel picked up the card, which suprised me to say the least...
I won't have time to spend a weekend on it until about christmas. {or
probably christmas day is more likely} Even then I can't make any kind
of promise that I can do anything useful about it...

-----Original Message-----
From: Rolf Eike Beer [mailto:eike-kernel@...tec.de] 
Sent: Wednesday, December 13, 2006 3:14 AM
To: Chandler, Greg
Cc: linux-kernel@...r.kernel.org; Martin K. Petersen
Subject: Re: Interphase Tachyon drivers missing.

Greg.Chandler@...lsfargo.com wrote:
> I went to upgrade my kernel on a couple of boxes yesterday and noticed

> that the Interphase Tachyon chipset Fibre Channel driver was removed 
> from the kernel.  I think 2.6.1 was the last one it was still in.  Was

> there a reason it was pulled?
> If not, do I have to volunteer to put it back in or can someone with 
> more skill re-add it?

I suppose you're talking about the cpqfc driver? I have tried to clean
it up but gave up. Next try was to rewrite, but due to lack of time
there is no progress in the last month. The old driver was that horrible
coded that noone can maintain it. It was originally written for
something like Linux 2.2 and was never even forward ported completely to
2.4. With the major changes in Linux' driver model that went into 2.6 it
was nearly unusable anyway. Not that the use of it in 2.4 can be
encouraged. One of the main problems is the severe lack of error
handling which you can see alone from the fact that there are tons of
function returning void even in the critical I/O-path's.

I have heard of at least 3 different people before you (not counting me)
that would like to have a driver for this one. One even donated some
hardware to me around last christmas. But nevertheless my lack of time
stopped my work on this.

Martin, you were hacking on something there too but never showed up some
code. 
Is there anything new?

Eike

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/