mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: roberto@dicosmo.org
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Roberto Di Cosmo <roberto@dicosmo.org>,
	linux-kernel@vger.kernel.org, fedor@karpelevitch.net
Subject: Re: Full specifications available for RealTek 8180 wireless chipset
Date: Thu, 16 Oct 2003 14:45:55 +0200	[thread overview]
Message-ID: <16270.37635.176658.541909@gargle.gargle.HOWL> (raw)
In-Reply-To: <3F8E7F2F.3060109@pobox.com>


Who told you the document is stolen?

I received it *officially* from RealTek's support people.

Nevetheless, since you seem to imply that people inside RealTek might "leak"
this document against the orders of their hierarchy, I am removing it, and
I will only put it back online, and reannounce it, when I have _written_
authorization from their headquarters, instead of just a mail.

Thanks for casting doubt on the honesty and reliability of RealTek's
employees, something I would never have imagined before your post

--Roberto Di Cosmo

>>>>> "Jeff" == Jeff Garzik <jgarzik@pobox.com> writes:

    Jeff> Roberto Di Cosmo wrote:
    >> Having experienced a large set of delusions using the closed source
    >> drivers for the RealTek 8180 wireless chipset available on RealTek web
    >> site on a stock kernel 2.4.20, that do confirm the posting of
    >> fedor@karpelevitch.net on September 11 2003 about kernel freeze with
    >> stock 2.4.22, I politely complained with RealTek, suggesting they open
    >> the code or release the chipset specifications to the community.
    >> 
    >> I received today the full chipset specifications, that I uploaded to
    >> http://www.dicosmo.org/RTL8180spec_1_3.pdf
    >> 
    >> I hope this may help, if somebody is willing to undertake writing a real,
    >> full fledged, Linux-quality driver for this chipset.
    >> 
    >> Sorry for not being able to do this myself.


    Jeff> Having announced this to thousands of people -- including RealTek
    Jeff> subscribers, no doubt -- you have poisoned any effort to write a
    Jeff> driver off this obviously-stolen document.

    Jeff> I hope others learn from your example, of what NOT to do.

    Jeff> Thanks for damaging my efforts to work on this through RealTek,

    Jeff> 	Jeff



      reply	other threads:[~2003-10-16 12:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-16  8:56 Roberto Di Cosmo
2003-10-16 11:21 ` Jeff Garzik
2003-10-16 12:45   ` roberto [this message]

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=16270.37635.176658.541909@gargle.gargle.HOWL \
    --to=roberto@dicosmo.org \
    --cc=fedor@karpelevitch.net \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    /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®