From: Andre Hedrick <andre@linux-ide.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Dan Hollis <goemon@sasami.anime.net>, Martin Mares <mj@suse.cz>,
Adam Lackorzynski <al10@inf.tu-dresden.de>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PCI-Devices and ServerWorks chipset
Date: Thu, 18 Jan 2001 02:01:45 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.10.10101180133460.20569-100000@master.linux-ide.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1010118092306.8140D-100000@delta.ds2.pg.gda.pl>
On Thu, 18 Jan 2001, Maciej W. Rozycki wrote:
> On Wed, 17 Jan 2001, Dan Hollis wrote:
>
> > They require not only an NDA, but that you also do all development on-site
> > at their santa clara HQ under their direct supervision.
>
> I haven't went that far -- I'm not going to sign any NDA anytime soon, so
> I haven't asked them for details. I recall someone writing here it's
> restrictive, indeed.
>
> > The only people who have ever got info out of serverworks are the lm78
> > guys and (i think) andre hedrick.
I can get any info needed, you just have to define the scope.
Then will not can and will not give out details on a generic form.
In short no one person can see the entire design docs or will they get
them without a NDA. I have seen why this is the case, cause the toy are
cool.
> I was asking for a few I/O APIC details -- apparently there are problems
> with 8254 interoperability and we have to use the awkward through-8259A
> mode for the timer tick.
Narrow the point.
> > What magic incantations they chanted, or which mafia thugs they hired to
> > manage this, I don't know...
>
> And I don't actually care. If they want to lose in the Linux area, it's
> their own choice.
You don't get it, they OEM board designs for Compaq and Dell.
These guys will work with you on-site but in their sand-box not yours.
I wish I could say more, but I have something more powerfully than any NDA
ever written. I have given my word and a handshake, and that has more
value to me than any stupid NDA. The very fact that I value this so much
and so many in the industry know this about me, I have been shown things
without NDA's that you never see otherwise.
They are very friendly to Linux, but can we be friendly to them?
You just can not barge in and demand to see their IP.
Regards,
Andre Hedrick
Linux ATA Development
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-18 10:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 17:12 Adam Lackorzynski
2001-01-17 8:52 ` Martin Mares
2001-01-17 10:14 ` Adam Lackorzynski
2001-01-17 11:25 ` Maciej W. Rozycki
2001-01-17 21:17 ` Dan Hollis
2001-01-18 8:37 ` Maciej W. Rozycki
2001-01-18 10:01 ` Andre Hedrick [this message]
2001-01-18 11:08 ` Maciej W. Rozycki
2001-01-18 17:40 ` Andre Hedrick
2001-01-19 12:24 ` Maciej W. Rozycki
2001-01-23 3:01 ` Tim Hockin
2001-02-08 8:34 ` Martin Mares
2001-01-23 18:18 ` Adam Lackorzynski
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.10.10101180133460.20569-100000@master.linux-ide.org \
--to=andre@linux-ide.org \
--cc=al10@inf.tu-dresden.de \
--cc=goemon@sasami.anime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
--cc=mj@suse.cz \
/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®