From: Avi Kivity <avi@argo.co.il>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: 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 19:11:13 +0200 [thread overview]
Message-ID: <43835131.5070608@argo.co.il> (raw)
In-Reply-To: <20051122165638.GE32684@havoc.gtf.org>
Jeff Garzik wrote:
>
>
>>However the situation with video drivers is already bad, and
>>deteriorating. I had to hunt on the Internet to get my recent (FC4)
>>distro to support my low-end embedded video (via). In the future it
>>looks like even that won't work.
>>
>>
>
>VIA is working with open source community. They are small enough
>(comparatively) that they need every advantage. VIA is one of the
>positive examples.
>
>
>
I'm aware of that. But look at the trouble we have even with the
cooperative vendors. I'm sure they had a Windows driver from day zero.
>
>
>>>Dumb with a capital 'D'.
>>>
>>>
>>>
>>>
>>I hope you have a better solution.
>>
>>
>
>Almost all of the solutions listed in this thread are better:
>Chinese wall rev-eng,
>
As others pointed out, rev-eng of programmable 3D hardware will be
difficult. There will be a perpetual (and long) lag between the
introduction of hardware and Linux support. The effort has to repeat for
new revisions of the hardware. And a rev-eng driver can still not be
trusted: who knows whether the register you just wrote into doesn't have
some subtle side-effect.
> funding, ...
>
>
I want some too.
I don't think Windows drivers are the best, or even a good solution. But
that may be the only realistic one. And I believe quite doable.
next prev parent reply other threads:[~2005-11-22 17:11 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
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 [this message]
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=43835131.5070608@argo.co.il \
--to=avi@argo.co.il \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.