I'd like to say this was a head scratcher for me. I like Keith's thouhts
on this.
--
Todd Fries .. [EMAIL PROTECTED]
Free Daemon Consulting, LLCLand: 405-748-4596
http://FreeDaemonConsulting.com Mobile: 405-203-6124
"..in support of free software solutions."
Ke
Around 23 o'clock on Jul 23, Matthieu Herrb wrote:
> Here's a patch to allow multiple '-nolisten' options on the command
> line. To disable both IPv4 and IPv6 transports, one needs to say:
>
> X -nolisten tcp -nolisten inet6
While supporting multiple -nolisten arguments is good, I suggest
Jon Leech <[EMAIL PROTECTED]> wrote:
> I'll back that up. Besides which, after a few years of being bitched
> at (and in one case involving a friend who's a senior software engineer at
> a commodity graphics vendor, physically threatened) because their company
> wasn't doing enough for Linux/O
On Sun, Jul 20, 2003 at 03:10:14AM -0400, Mike A. Harris wrote:
...
> Anyone in my position who has to deal with these types of support
> questions or customer/user feedback, will very likely know
> exactly where I am coming from, and will strongly back up my
> statement that it is often better to
> From: Matthias Scheler <[EMAIL PROTECTED]>
> On Wed, Jul 23, 2003 at 01:48:08PM +0200, Egbert Eich wrote:
> > > I wasn't suggesting to use it on Linux. My suggestion was to revert to
> > > using a single socket on all platforms and use the above code to enable
> > > accepting IPv4 connections
Maybe I'm missing something, but I always thought the XFree86 nolisten
code was overly complicated, and this just seems to make it worse. When
we added -nolisten to Xsun, we got multiple listeners for free with a
simpler implementation, contained entirely in utils.c:
else if ( strcmp( argv
Here's a patch to allow multiple '-nolisten' options on the command
line. To disable both IPv4 and IPv6 transports, one needs to say:
X -nolisten tcp -nolisten inet6
I'll add a documentation patch too later.
Index: xc/programs/Xserver/include/os.h
On Wed, 23 Jul 2003, Egbert Eich wrote:
> Marc Aurele La France writes:
> > I don't like the peppering of this code with more OS #ifdef's. I think
> > the approach espoused by Itojun, Todd, Matthieu and Andrew is better.
> So maybe you can tell what the big difference is?
So maybe not. I've
I've accidently sent the wrong file before. Sorry.
Egbert.
Index: Xtrans.c
===
RCS file: /home/x-cvs/xc/lib/xtrans/Xtrans.c,v
retrieving revision 3.31
diff -u -r3.31 Xtrans.c
--- Xtrans.c20 Jul 2003 16:12:15 - 3.31
+++
Marc Aurele La France writes:
>
> I don't like the peppering of this code with more OS #ifdef's. I think
> the approach espoused by Itojun, Todd, Matthieu and Andrew is better.
>
So maybe you can tell what the big difference is?
It tries to preserve more of the old behavoir with
respect to
On Tue, Jul 22, 2003 at 06:56:58PM -0700, Mark Vojkovich wrote:
| The interest, at least as far as the press is concerned, seems to
| be almost totally in the chipset performance. nForce2 is available
| without internal graphics. If I recall correctly, nForce3 (I believe
| there were some reviews
Oops, I haven't rebuilt the server.
Maybe this should be changed to int, 0 and 1.
Egbert.
Dr Andrew C Aitchison writes:
> On Wed, 23 Jul 2003, Egbert Eich wrote:
>
> > I've made the patch below which takes care of the problem for me.
>
> make[3]: Entering directory `/home/XFree86/4.2/std/
Fabio Massimo Di Nitto writes:
>
> I didn't check/produce any code but the easiest way to implement in linux
> is something like (if the user does not specify --nolisten):
>
> bind to ipv6
> if it works ok
> otherwise fail silently
> bind to ipv4
> if it works ok
> otherwise fail with e
On Wed, 23 Jul 2003, Egbert Eich wrote:
> I've made the patch below which takes care of the problem for me.
> I have tried several different versions, I didn't really like any
> of them.
> This code is one of the rare pieces of code that is rather well
> structured and relatively free of any ugly
On Wed, 23 Jul 2003 21:36:43 +0530, Nitin Mahajan wrote:
>
>1.Is this the double buffering???
Yes; while one offscreen buffer is being displayed, you draw into a second
offscreen buffer. When that buffer is finished, you flip them so that the
second becomes visible and the first is free for dr
> Hi! Loic,
> Thanx for the reply.
> I think I got the concept.
> 1.Is this the double buffering???
Yes indeed. Triple would be to have one more buffer:
1 displayed
1 waiting to be displayed
1 in which you render
> 2.I guess can be achieved by a frame buffer to framebuffer copy using the Bi
On Wed, 23 Jul 2003, Egbert Eich wrote:
> I've made the patch below which takes care of the problem for me.
make[3]: Entering directory `/home/XFree86/4.2/std/xc/lib/ICE'
rm -f transport.o
gcc -m32 -c -O2 -fno-strength-reduce -fno-strict-aliasing -ansi -pedantic
-Wall -Wpointer-arith -Wstrict-p
Hi! Loic,
Thanx for the reply.
I think I got the concept.
1.Is this the double buffering???
2.I guess can be achieved by a frame buffer to framebuffer copy using the BitBLT
engine???
Am I right??
3.Will this help me in achieving a frame rate of 30fps to play a software decoded
video.
Regard
From: "Nitin Mahajan" <[EMAIL PROTECTED]>
> Hello !
> As regards C&T 69030 ,can anyone please tell ,what instant full screen
> page FLIP means
It usually means that you render something to be displayed on the screen
in some offscreen part of the video memory, then you tell the chipset th
Title: Message
Hello
!
As regards C&T
69030 ,can anyone please tell ,what instant full screen page FLIP
means
What part of the
driver code in xfree86 is handling this???
regards
Nitin Mahajan
mail:[EMAIL PROTECTED]
Ph:51101667. Mobile :
9886099925
Ok guys, you are getting the logic wrong from everything I've seen. Here
is what you really want to do:
errv6 = attempt to bind to v6 socket
errv4 = attempt to bind to v4 socket
if ( errv6 && errv4 )
error!
else
success!
this will work on linux, bsd, and any system, with
I've made the patch below which takes care of the problem for me.
I have tried several different versions, I didn't really like any
of them.
This code is one of the rare pieces of code that is rather well
structured and relatively free of any ugly hacks. This fix makes
it a lot uglier, what I par
On Wed, 23 Jul 2003, Egbert Eich wrote:
> Fabio Massimo Di Nitto writes:
> > On Tue, 22 Jul 2003, Matthias Scheler wrote:
> >
> > > On Tue, Jul 22, 2003 at 08:03:35PM +0200, Egbert Eich wrote:
> > > > The current CVS code produces the error:
> > > >
> > > > _XSERVTransSocketINETCreateListene
--- Begin Message ---
(todd and matthieu, if this does not go through please forward it)
>I wasn't suggesting to use it on Linux. My suggestion was to revert to
>using a single socket on all platforms and use the above code to enable
>accepting IPv4 connections on *BSD.
there is s
Hello !
Can any one please tell me,how will I measure the frame rate in this
case.
How will I test my driver for the frame rate?
Regards
Nitin
-Original Message-
From: Nitin Mahajan
Sent: Wednesday, July 23, 2003 8:41 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Driver for 69030
Hello Everyo
On Wed, Jul 23, 2003 at 01:48:08PM +0200, Egbert Eich wrote:
> > I wasn't suggesting to use it on Linux. My suggestion was to revert to
> > using a single socket on all platforms and use the above code to enable
> > accepting IPv4 connections on *BSD.
> Yes, I understand. I was just looking for
Matthias Scheler writes:
>
> I wasn't suggesting to use it on Linux. My suggestion was to revert to
> using a single socket on all platforms and use the above code to enable
> accepting IPv4 connections on *BSD.
>
Yes, I understand. I was just looking for a decend way of making
things work
Fabio Massimo Di Nitto writes:
> On Tue, 22 Jul 2003, Matthias Scheler wrote:
>
> > On Tue, Jul 22, 2003 at 08:03:35PM +0200, Egbert Eich wrote:
> > > The current CVS code produces the error:
> > >
> > > _XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed
> > > _XSERVTrans
Matthias Scheler writes:
> On Tue, Jul 22, 2003 at 09:14:08PM +0200, Egbert Eich wrote:
> > As I tried to explain binding to an IPv6 socket implicitely binds to
> > an IPv4 socket.
>
> That's a bug.
>
According to what I've heared it is intended and
therefore considered a feature.
I'm not
On Wed, Jul 23, 2003 at 07:38:11AM +0100, Andrew C Aitchison wrote:
> So, what we do is as follows:
>
> (1) At this point we set up two addresses, one containing ":" to indicate
> an IPv6 wildcard address, ...
That should read "::".
> (2) Later, when we create the IPv6 socket, we set IPV6_V6O
> therefore, i suggest
> - on all platforms try to open 2 sockets, AF_INET6 then AF_INET
> - ignore error from socket(2) and bind(2) on both cases
> - raise error only if both attempt fails
actually for the 1st bullet, obeying the result from getaddrinfo(3)
Hello all,
I'll try to make this short and to the point, but I can't promise
anything. If someone on this list thinks this question shouldn't be on
this list, let me know, and I'll drop it. Thanks.
The problem concerns my tweaking of a window manager (evilwm). Now, I
don't want everyone to
32 matches
Mail list logo
