Abraham vd Merwe wrote:
>
> Hi Jens!
>
> > > > Sure, Monday at 5pm pacific time works for me. We'll see how many
> > > > questions do show up. If nothing else, we can catch up with the old
> > > > team :-)
> > >
> > > Could we perhaps change this. All of us scattered around the middle of earth
Hi Jens!
> > > Sure, Monday at 5pm pacific time works for me. We'll see how many
> > > questions do show up. If nothing else, we can catch up with the old
> > > team :-)
> >
> > Could we perhaps change this. All of us scattered around the middle of earth
> > (europe, south africa, etc.) strike
Abraham vd Merwe wrote:
>
> Hi Jens!
>
> > > > So, the question is how to we get that process going. As a suggestion,
> > > > maybe
> > > > a weekly IRC meeting would help where new developers can ask the experts,
> > > > and
> > > > each other, questions about DRI, XFree or 3D graphics. I am
Hi Jens!
> > > So, the question is how to we get that process going. As a suggestion,
> > > maybe
> > > a weekly IRC meeting would help where new developers can ask the experts,
> > > and
> > > each other, questions about DRI, XFree or 3D graphics. I am sure it would
> > > be
> > > much easier
On Thu, Jan 17, 2002 at 02:15:32PM -0800, Gareth Hughes wrote:
> To continue the comparisons with the kernel, how much documentation
> do you think there is on the bleeding-edge work being done by the
> core developers? Is there a "How To Hack On The New 2.4.10 VM"
> document anywhere? Or "Ten
Ian D Romanick wrote:
> It might be
> better to gradually add documentation to the source that could be
> automatically be extracted...
I agree. Developers are *much* more likely to keep the inline
documentation up to date. Downside is the documentation becomes very
blocky and it's difficult t
On Thu, 2002-01-17 at 21:28, Daryll Strauss wrote:
> On Thu, Jan 17, 2002 at 08:01:14PM +, David Johnson wrote:
> > So, the question is how to we get that process going. As a suggestion,
> > maybe a weekly IRC meeting would help where new developers can ask the experts,
> > and each other,
On Thu, Jan 17, 2002 at 03:11:46PM -0800, David Bronaugh wrote:
> Perhaps a good idea here would be to have some sort of a function
> documentation tracking project.. I have been doing a hell of a lot of PHP
> programming lately, and I'd be willing to put in the time to get something
> like th
--- Begin Message ---
On Thu, 17 Jan 2002 12:28:22 Daryll Strauss wrote:
> On Thu, Jan 17, 2002 at 08:01:14PM +, David Johnson wrote:
> > So, the question is how to we get that process going. As a suggestion,
>
> > maybe
> > a weekly IRC meeting would help where new developers can ask the
Daryll Strauss wrote:
>
> On Thu, Jan 17, 2002 at 08:01:14PM +, David Johnson wrote:
> > So, the question is how to we get that process going. As a suggestion,
> > maybe
> > a weekly IRC meeting would help where new developers can ask the experts,
> > and
> > each other, questions about DRI,
Brian Paul wrote:
>
> Even before VA Linux laid-off everyone we were losing momentum on the
> DRI project because the engineers had to work on other projects that
> generated revenue. After everyone was laid-off we all went in different
> directions. I think I'm one of the few who still reads t
On Thu, Jan 17, 2002 at 08:01:14PM +, David Johnson wrote:
> So, the question is how to we get that process going. As a suggestion,
> maybe
> a weekly IRC meeting would help where new developers can ask the experts,
> and
> each other, questions about DRI, XFree or 3D graphics. I am sure i
this is actually sufficient for me at this point.
tnx!
johnu
ps: you might think of pasting this part of your response the into the dri
homepage, it would save a bit of bandwidth perhaps:
> All OpenGL drivers
> are made up of 3 parts:
>
> A DRI aware 2D driver which lives in
> xc/programs/X
d
>From: Daryll Strauss <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>CC: [EMAIL PROTECTED], [EMAIL PROTECTED]
>Subject: Re: [Dri-devel] DRM/DRI porting guide?
>Date: Thu, 17 Jan 2002 09:56:03 -0800
>
>On Thu, Jan 17, 2002 at 02:40:15AM -0800, [EMAIL PROTECTED] wrote:
> >
i wont mess with trying to respond in line.
but i have been lurking on this list for the last year ( which is more of
an investment than you might think! ) and it appears that adoniz makes
some valid points, tho perhaps in an overly vigourous fashion. :-)
well, every OS project is different (
On Thu, Jan 17, 2002 at 02:40:15AM -0800, [EMAIL PROTECTED] wrote:
>
> Okay, sorry, I just had to laugh. Not your fault, I admit that. You are as innocent
>as I used to be.
>
> Here's the deal bro:
Now I'm going to turn this around a bit. You've already seen the answers
from most of us. We're
This may be OT...
On Thu, 2002-01-17 at 14:58, Brian Paul wrote:
[snip]
> I think I'm one of the few who still reads this list.
>
[snip]
> We thought it was more important to invest
> our time in the drivers and infrastructure code than writing/updating
> design documents. The DRI is very compl
On Thu, Jan 17, 2002 at 07:58:01AM -0700, Brian Paul wrote:
> [EMAIL PROTECTED] wrote:
> >
> > Okay, sorry, I just had to laugh. Not your fault, I admit that. You are as
>innocent as I used to be.
> >
> > Here's the deal bro:
> >
> > [RANT MODE ON]
> >
> > [...]
> >
> > [RANT MODE OFF]
> >
[EMAIL PROTECTED] wrote:
>
> Okay, sorry, I just had to laugh. Not your fault, I admit that. You are as innocent
>as I used to be.
>
> Here's the deal bro:
>
> [RANT MODE ON]
>
> [...]
>
> [RANT MODE OFF]
>
> Finale:
>
> Anyone: please think about it before (if) you respond to this email.
Okay, sorry, I just had to laugh. Not your fault, I admit that. You are as innocent
as I used to be.
Here's the deal bro:
[RANT MODE ON]
Sometimes it seems that the DRI project is for a "special" group of people who are
(either,or,and,not,etc,etc):
1) special, either because they designed
greetings;
i am interested in writing the bits required to get dri working on the SiS
630E (which evidently contains an SiS300 and SiS 301, among other things)
on FreeBSD. It's my understanding that this chipset is supported under
Linux, but i havent poked around in the tree yet.
is there such a
21 matches
Mail list logo
