From: Daniel Mehrmann <daniel.mehrmann@gmx.de>
To: Sean Neakums <sneakums@zork.net>, linux-kernel@vger.kernel.org
Subject: Re: Linux-2.4: Merge Emulex and Qlogic FC drivers ?
Date: Sun, 10 Nov 2002 23:47:20 +0100 [thread overview]
Message-ID: <200211102347.20278.daniel.mehrmann@gmx.de> (raw)
In-Reply-To: <200211102337.17028.daniel.mehrmann@gmx.de>
On Sunday 10 November 2002 23:37, Daniel Mehrmann wrote:
> On Sunday 10 November 2002 23:14, Sean Neakums wrote:
> > commence Daniel Mehrmann quotation:
> > > i want merge the linux driver for FC controllers from Qlogic
> > > and Emulex (All series from both) into the kernel tree,
> > > because i need this for our company.
> > >
> > > Qlogic is clear GPL but Emulex have no GPL.
> > > I think the license to use the code is free and i see no
> > > problems.
> >
> > The last time I looked at an Emulex Linux driver (for the
> > LP-7000, about six months ago), it consisted of a large
> > binary-only portion, shipped in a .a file, and the source code
> > for a shim to have the library code talk to the kernel.
> >
> > Furthermore, the driver was configured by editing a .c file and
> > rebuilding it.
> >
> > All in all, a quality experience.
>
> Mh, i have the complete source code. Only the hba access
> for IP over FC is binary, but that`s a libary api for userland
> tools. I only want merge the standalone driver for both products.
> If i do this, i must add this to a readme file.
>
Ops, you`re right. I used the wrong directory :-((
Ok, for Emulex series i can forget this plan !
next prev parent reply other threads:[~2002-11-10 22:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-10 22:02 Linux-2.4: Merge Emulex and Qlogic FC drivers ? Daniel Mehrmann
2002-11-10 22:14 ` Sean Neakums
2002-11-10 22:37 ` Daniel Mehrmann
2002-11-10 22:47 ` Daniel Mehrmann [this message]
2002-11-10 22:58 ` Sean Neakums
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=200211102347.20278.daniel.mehrmann@gmx.de \
--to=daniel.mehrmann@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sneakums@zork.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox