From: Rob Landley <rob@landley.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Denis Vlasenko <vda@ilport.com.ua>, Neil Brown <neilb@suse.de>,
Jon Smirl <jonsmirl@gmail.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Dave Airlie <airlied@gmail.com>, Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] Small PCI core patch
Date: Tue, 22 Nov 2005 10:33:48 -0600 [thread overview]
Message-ID: <200511221033.50351.rob@landley.net> (raw)
In-Reply-To: <20051122143055.GC24997@havoc.gtf.org>
On Tuesday 22 November 2005 08:30, Jeff Garzik wrote:
> On Tue, Nov 22, 2005 at 10:07:12AM +0200, Denis Vlasenko wrote:
> > Historically hackers were not too good at raising funds.
> >
> > Maybe we should use stuff which we are good at? Forcedeth
> > is a nice precedent. 2d and especially 3d engines
> > may be significantly harder to reverse engineer,
> > but people can scale rather nicely, as kernel development shows. ;)
> >
> > Then write specs from gained knowledge and put it on a web page.
>
> Yes, IMO this is the only realistic path, without cooperation from
> ATI/NVIDIA.
>
> This is why I dislike the ATI r300 rev-eng effort: I cannot find any
> "Chinese wall": one team rev-engs the hardware and writes a doc.
> Another team writes the drivers from the docs.
If they're reverse engineering the hardware, why would you need a chinese
wall? Compaq was turning x86 assembly code into x86 assembly code and had to
prove that the new x86 code didn't infringe the copyright on the old x86
code. They weren't turning port I/O and DMA logs into C code...
Rob
next prev parent reply other threads:[~2005-11-22 16:34 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 22:53 [RFC] Small PCI core patch Greg KH
2005-11-21 23:01 ` Greg KH
2005-11-21 23:35 ` Benjamin Herrenschmidt
2005-11-22 0:47 ` Dave Airlie
2005-11-22 1:34 ` Alan Cox
2005-11-22 2:20 ` Jon Smirl
2005-11-22 2:36 ` Benjamin Herrenschmidt
2005-11-22 3:01 ` Jon Smirl
2005-11-22 7:41 ` Rob Landley
2005-11-22 8:44 ` Dave Airlie
2005-11-22 2:27 ` Benjamin Herrenschmidt
2005-11-22 3:23 ` Jon Smirl
2005-11-22 3:44 ` Benjamin Herrenschmidt
2005-11-22 4:11 ` Neil Brown
2005-11-22 8:07 ` Denis Vlasenko
2005-11-22 14:30 ` Jeff Garzik
2005-11-22 16:33 ` Rob Landley [this message]
2005-11-22 16:38 ` Jeff Garzik
2005-11-22 10:58 ` Florian Weimer
2005-11-22 19:28 ` Adrian Bunk
2005-11-23 15:46 ` Jesper Juhl
2005-11-24 2:11 ` Lee Revell
2005-11-22 15:46 ` Avi Kivity
2005-11-22 15:51 ` Jeff Garzik
2005-11-22 16:14 ` Avi Kivity
2005-11-22 16:25 ` Jeff Garzik
2005-11-22 16:40 ` Avi Kivity
2005-11-22 16:56 ` Jeff Garzik
2005-11-22 17:11 ` Avi Kivity
2005-11-22 17:37 ` Brian Gerst
2005-11-22 17:38 ` Jeff Garzik
2005-11-22 19:39 ` Avi Kivity
2005-11-23 10:51 ` Rogério Brito
2005-11-23 14:29 ` Alan Cox
2005-11-22 18:38 ` Alan Cox
2005-11-22 19:47 ` Avi Kivity
2005-11-22 16:26 ` Diego Calleja
2005-11-22 16:35 ` Avi Kivity
2005-11-22 19:49 ` Diego Calleja
2005-11-22 20:08 ` Avi Kivity
2005-11-22 20:15 ` Lee Revell
2005-11-22 20:43 ` Diego Calleja
2005-11-22 22:00 ` Avi Kivity
2005-11-22 22:42 ` Jan Knutar
2005-11-22 14:07 ` Marc Koschewski
2005-11-22 22:53 ` Benjamin Herrenschmidt
2005-11-22 23:06 ` Marc Koschewski
2005-11-22 23:20 ` Benjamin Herrenschmidt
2005-11-22 14:25 ` Alan Cox
2005-11-22 14:26 ` today's graphics (was Re: [RFC] Small PCI core patch) Jeff Garzik
2005-11-22 18:58 ` Alan Cox
2005-11-22 18:41 ` Jeff Garzik
2005-11-22 1:21 ` [RFC] Small PCI core patch Greg KH
2005-11-22 1:28 ` Chris Wedgwood
2005-11-22 1:42 ` Greg KH
2005-11-22 5:50 ` Arjan van de Ven
2005-11-22 14:36 ` Jeff Garzik
2005-11-22 16:54 ` Jon Smirl
2005-11-22 20:17 ` Alan Cox
2005-11-22 21:13 ` Brian Gerst
2005-11-22 23:26 ` Alan Cox
2005-11-22 22:59 ` Benjamin Herrenschmidt
2005-11-22 6:57 ` Rob Landley
2005-11-22 18:26 ` Matthieu CASTET
2005-11-22 19:05 ` Greg KH
2005-11-22 20:15 ` Alan Cox
2005-11-23 3:26 ` Andrew James Wade
2005-11-21 23:28 ` Jeff Garzik
2005-11-21 23:30 ` Benjamin Herrenschmidt
2005-11-22 17:50 ` Greg KH
2005-11-22 22:31 ` Harald Dunkel
2005-11-22 23:40 ` Alan Cox
2005-11-23 6:06 ` Harald Dunkel
2005-11-23 6:26 ` Dave Jones
2005-11-23 11:11 ` Alan Cox
[not found] <5bsXq-5uy-3@gated-at.bofh.it>
[not found] ` <5bsXq-5uy-1@gated-at.bofh.it>
[not found] ` <5btqF-66n-41@gated-at.bofh.it>
[not found] ` <5bzmg-66b-1@gated-at.bofh.it>
[not found] ` <5bHtG-228-23@gated-at.bofh.it>
2005-11-25 4:06 ` Robert Hancock
2005-11-25 6:34 ` Jeff Garzik
2005-11-25 13:54 ` Alan Cox
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=200511221033.50351.rob@landley.net \
--to=rob@landley.net \
--cc=airlied@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=benh@kernel.crashing.org \
--cc=greg@kroah.com \
--cc=jgarzik@pobox.com \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=vda@ilport.com.ua \
/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