From: Andre Hedrick <andre@aslab.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Arjan van de Ven <arjanv@redhat.com>
Subject: BSD-Linux FlameWar over SoftRAID.
Date: Wed, 26 Sep 2001 00:03:06 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.31.0109251448490.29600-100000@postbox.aslab.com> (raw)
It is clear that BSD is going off the deep end.
Linux ATA Development has a Legal signed NDA for the proper development of
the complete and correct FastTrak(tm) open sources driver.
I will soon publish the complete header codes in a original header w/
a Linux ATA Development Copyright and Promise Technologies Copyright.
The driver will have a GPL statement be issued in the headers and source
files to prevent the usage in BSDish environments. I have not tolerance
for being labled a thief.
I will prove the point that Linux does not "STEAL IP", then watch BSD
"borrow" from Linux. Just like we will watch 48-BIT Addressing be
borrowed without credit. Just like we will watch the new Ultra133 drivers
be borrowed without credit. BSD has no legal documentation to develop
these changes or access to hardware. We will watch and prove where IP
comes from in the world of storage.
Ever noticed how Linux had Ultra100 support 10 minutes after the release
of public information on June 5, 2000 8:00am PDT?
For now the Linux Open Source drivers for SoftRAID need to go away.
Not to worry they will return in full swing.
**********************
Date: Wed, 10 Nov 1999 11:32:52 -0800
From: ---deleted---
To: 'Andre Hedrick' <andre@suse.com>
Subject: RE: [Research] FastTrak66 Ultra ATA/66
Hi Andre,
Very interesting work, I can't guess how you did it. Here is our beta
driver for the Fasttrak. This is the one I told you about. It uses our Raid
engine (engine3.a). Sorry, but as I mentioned there is no possibility of us
releasing the source code for this. However you can get a good idea of how
the engine works by viewing our driver source. Please do not distribute
this driver or the engine binary to anyone. I've included some quick
documentation too, I remember there is one step missing but it is obvious.
begin 600 FT03.TGZ
M'XL(`);\_C<``^0\:W/;1I+^BE3E/XR5DA:D(!&DJ$=$05L42=FL6(](\N:R
M.16*)$ ):Q)@`-"6UO;^]NON>6 `@HQLV55W=4Q,`3,],ST]_9J>'F[77GSW
<BIG SNIP>
M`UT#``-=`P`#70,``UT#``-=`P`%5@%=`P`%5@%=`P`%5@%=`P`%5@%=`P`%
35@%=`P`%5@%=`P`%5@%=`P``%@`%
`
end
**********************
Here is the proof that I could have done this long before the BSD folks
had a clue about soft raid engines wrt addon cards.
Regards,
Andre Hedrick
CTO ASL, Inc.
Linux ATA Development
-----------------------------------------------------------------------------
ASL, Inc. Tel: (510) 857-0055 x103
38875 Cherry Street Fax: (510) 857-0010
Newark, CA 94560 Web: www.aslab.com
next reply other threads:[~2001-09-26 7:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 7:03 Andre Hedrick [this message]
2001-09-26 8:55 ` Alexander Viro
2001-09-26 16:13 ` Alan Cox
2001-09-26 16:04 ` Andre Hedrick
2001-09-26 14:12 Warner Losh
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=Pine.LNX.4.31.0109251448490.29600-100000@postbox.aslab.com \
--to=andre@aslab.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®