Re: Linear Allocator (Was Re: Alan H's new linear allocator and Neomagic Xv)
Alan Hourihane writes: Well, if someone else has a chip, or wants to update and test other drivers (but be careful with DRI enabled drivers as it needs more work in the driver). Here's a patch to the neomagic that should work, and could be used as a template for the other drivers. That's all. Most Xv (if not all) use linear allocation already and will take advantage of it straight away without any furthur modifications. Index: neo_driver.c === RCS file: /X11R6/x-cvs/xc/programs/Xserver/hw/xfree86/drivers/neomagic/neo_driver.c,v retrieving revision 1.71 diff -u -r1.71 neo_driver.c --- neo_driver.c 24 Sep 2003 03:16:55 - 1.71 +++ neo_driver.c 30 Oct 2003 10:05:04 - @@ -1685,11 +1685,20 @@ AvailFBArea.y1 = 0; I'm not sure if this will solve the problems we see on neomagic. I will take a look at it but I won't be able to do this in time for 4.4. Egbert. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Linear Allocator
Alan Hourihane [EMAIL PROTECTED] wrote: Well, if someone else has a chip, or wants to update and test other drivers (but be careful with DRI enabled drivers as it needs more work in the driver). Here's a patch to the neomagic that should work, and could be used as a template for the other drivers. That's all. Most Xv (if not all) use linear allocation already and will take advantage of it straight away without any furthur modifications. I was not aware of this new Linear Allocator. Are there any docs on how to interface this into the drivers at all? I would like to take a look at it and see how it works. We would like to be able to hook the linear allocator functions such that we can do surface management in offscreen memory ourselves in our driver. Is that possible with the linear allocator (ie: hook out the functions that create the surfaces somehow)? Also is using the linear allocator a requirement for Xv? Regards, --- Kendall Bennett Chief Executive Officer SciTech Software, Inc. Phone: (530) 894 8400 http://www.scitechsoft.com ~ SciTech SNAP - The future of device driver technology! ~ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Setting up a runtime-only package?
Hello everyone, I am trying to get together the packaging requires for XFree86 so that I can provide it to our users. Ideally, I would like to split the packaging into at least two pieaces, possibly three. At the very least I would like to provide a runtime component that has all of the required shared libraries, data files and header files, so that customers can run other precompiled stuff, or develop X applications. The shared libs and include stuff is easy, I know what to include there, but what else is needed for a pure runtime environment (no server, no standard clients) such that, for example, I can compile Mozilla against the XFree86 libs and have it run. Does anyone have an idea of what else is required? I am guessing the fonts will be required, but how many other bits and pieces in usr/X11R6/lib are required? The second piece would be all the clients, the server itself and anything not in the runtime package, as well as all of the man pages. A possible third piece would be to have all of the fonts in their own package, or perhaps all of the doc in its own package too. If anyone can point me at any docs, or help shed some light on this, I would be extremely grateful. Regards, Kean. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Capturing events from the root window
On Fri, 31 Oct 2003 10:52:44 +1100, Carsten Haitzler (The Rasterman) [EMAIL PROTECTED] wrote: no. the wm - or any app can go raising windows above yours... you cant clock windows in place to be on top as such. (ok we can argue of some nasty hacks and methods if you are the wm... but thats a world on its own.) If I raise my window, how can I make sure that it is on top of all? ok. for a normal window yes its possible to get events to know if you got obscured. they are called visibilitynotify events. BUT i am actually not sure if they will be received by inputonly windows. but thats the path you want to go. Whats input only windows? How can I make sure my window is not an InputOnly window but, whatever, else? you could find if a window has been raised/lowered etc. by monitoring creatnotifies on root, then on every windows created monitor structurenotifies then look for configurenotify events and check the stacking sections (above, window, event). again - i dont know how well gdk(gtk) supports this part of x so you may have to dump into xlib. I don'tneccessarily need to do that. If it is possible to make sure that my window is raised on top off all, then I can simply monitor for this visibillitynotify, and raise it anyway. If it is not possible to create other window then this inputwindow then I can monitor this createnotify. How is this working? Does root then send me an event everytime a window is created? hmm how is it meant to work? mouse goes to left or right side of window, launcher buttons pop up and u click one to run something? Yes. The nice thing of this tool is, that it always works. You don't need to have a window or a bar or anything on the screen which you need to access. It's really usefull to have around, thats why I decided to port it to linux. -- Gerhard Gruber Für jedes menschliche Problem gibt es immer eine einfache Lösung: Klar, einleuchtend und falsch. (Henry Louis Mencken) ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Capturing events from the root window
You could fudge it if you have to. Monitor your window for configure notify events, and poll the root window. Whenever there is information indicating that your window is no longer at the top, restack it so that it becomes on top if you have to. This will work, but you'll need to keep your latency down. It will take about a split second for it to jump. This ought to work no matter what window manager you use. This is a sure fire kludge, but there might be a better way. Does X11 provide a always on top flag? From: Gerhard W. Gruber [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Capturing events from the root window Date: Thu, 30 Oct 2003 23:07:37 +0100 On Fri, 31 Oct 2003 08:51:07 +1100, Carsten Haitzler (The Rasterman) [EMAIL PROTECTED] wrote: you willonly then get events when the mouse passes over your thin window. That's no problem as long as my window stays on top. not as a widget - no. you'll have to jump down to gdk. i'm not sure if gdk supports this though. you'll want an inputonly window thats a toplevel window (immediate child of root) thats override-redirect. you'll need to also monitor I managed to create an invisible window which is only one pixel in widht and has the same height as the screen (hardcoded for now, how can I query the current resolution?). The only problem, I still have is, to make the window stay on top of all others in order to always receive input events when the user moves the mouse to the right border (or where he configured it). Is it possible to create a window that always stays on top? Not only of it's own application, but of all application windows. If not, is it possible to get an event when my window is obscured or lowered because another window has been raised over it? Actually getting the inof when it is obscored would be enough because it only needs to stay accessible all the time and for this it doesn't have to be the top window. And can I raise a window above all others? I browsed the web for this, but it seems that is also not possible. Everytime I think of a new way how to achieve what I need it seems to be blocked by X. :( all client windows, where they move, go etc. and follow i'm still not even 100% sure what it is you want to actually do (in overall aim) You can take a look in the readme at http://sourceforge.net/projects/launchmenu, there I explain it. Its just a simple app that has been proven quite usefull to me over the years and I wrote this for myself because the original source is not portable and the author doesn't give away all the source anyway. If you don't want to download the package, it is of course in the CVS as well. there's a whole extension devoted to recording events - the xrecord extension - but i know very little about it. :) No prob. It wouldn't do what I need anyway. -- Gerhard Gruber Für jedes menschliche Problem gibt es immer eine einfache Lösung: Klar, einleuchtend und falsch. (Henry Louis Mencken) ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel _ Enjoy MSN 8 patented spam control and more with MSN 8 Dial-up Internet Service. Try it FREE for one month! http://join.msn.com/?page=dept/dialup ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Capturing events from the root window (ID20311056 ignore this number)
Unless you own the root window, you probably can't intercept events. The X server knows which connection each window belongs to, and only THAT connection gets events relayed to it. Short of hacking X, there's no way to steal messages. You COULD monitor the stacking order, and listen for interesting events on YOUR window, and periodically (once every 1/10th of a second or so) POLL the status and stacking order of your window. All windows are visible (i.e. the X server will tell you that they exist, where they are, etc), but you can only receive events related to windows that YOU own. From: Gerhard W. Gruber [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Capturing events from the root window Date: Thu, 30 Oct 2003 23:07:37 +0100 On Fri, 31 Oct 2003 08:51:07 +1100, Carsten Haitzler (The Rasterman) [EMAIL PROTECTED] wrote: you willonly then get events when the mouse passes over your thin window. That's no problem as long as my window stays on top. not as a widget - no. you'll have to jump down to gdk. i'm not sure if gdk supports this though. you'll want an inputonly window thats a toplevel window (immediate child of root) thats override-redirect. you'll need to also monitor I managed to create an invisible window which is only one pixel in widht and has the same height as the screen (hardcoded for now, how can I query the current resolution?). The only problem, I still have is, to make the window stay on top of all others in order to always receive input events when the user moves the mouse to the right border (or where he configured it). Is it possible to create a window that always stays on top? Not only of it's own application, but of all application windows. If not, is it possible to get an event when my window is obscured or lowered because another window has been raised over it? Actually getting the inof when it is obscored would be enough because it only needs to stay accessible all the time and for this it doesn't have to be the top window. And can I raise a window above all others? I browsed the web for this, but it seems that is also not possible. Everytime I think of a new way how to achieve what I need it seems to be blocked by X. :( all client windows, where they move, go etc. and follow i'm still not even 100% sure what it is you want to actually do (in overall aim) You can take a look in the readme at http://sourceforge.net/projects/launchmenu, there I explain it. Its just a simple app that has been proven quite usefull to me over the years and I wrote this for myself because the original source is not portable and the author doesn't give away all the source anyway. If you don't want to download the package, it is of course in the CVS as well. there's a whole extension devoted to recording events - the xrecord extension - but i know very little about it. :) No prob. It wouldn't do what I need anyway. -- Gerhard Gruber Für jedes menschliche Problem gibt es immer eine einfache Lösung: Klar, einleuchtend und falsch. (Henry Louis Mencken) ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel _ See when your friends are online with MSN Messenger 6.0. Download it now FREE! http://msnmessenger-download.com ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Boost Your Car's Gas Mileage 27%+.....diza
FUEL SAVER PRO This revolutionary device Boosts Gas Mileage 27%+ by helping fuel burn better using three patented processes from General Motors. Take a test drive Today - http://www.llat.org?axel=49 PROVEN TECHNOLOGY A certified U.S. Environmental Protection Agency (EPA) laboratory recently completed tests on the new Fuel Saver. The results were astounding! Master Service, a subsidiary of Ford Motor Company, also conducted extensive emissions testing and obtained similar, unheard of results. The achievements of the Fuel Saver is so noteworthy to the environmental community, that Commercial News has featured it as their cover story in their June, 2000 edition. Take a test drive Today - http://www.llat.org?axel=49 No more advertisements, thanks - http://www.aqmp.net/out5s/rem2e.asp qfugzcwnr uutujwc vuopporwuq yoiiqqmjc rhhkz
Re: Capturing events from the root window
On Fri, 31 Oct 2003 22:04:22 +0100 "Gerhard W. Gruber" [EMAIL PROTECTED] (Bbabbled: (B (B On Fri, 31 Oct 2003 10:52:44 +1100, Carsten Haitzler (The Rasterman) (B [EMAIL PROTECTED] wrote: (B (B no. the wm - or any app can go raising windows above yours... you cant clock (B windows in place to be on top as such. (ok we can argue of some nasty hacks (B and methods if you are the wm... but thats a world on its own.) (B (B If I raise my window, how can I make sure that it is on top of all? (B (Bthe raise will raise ontop of everything - BUt something may raise itself above (Byour window immediately afterwards too... (B (B ok. for a normal window yes its possible to get events to know if you got (B obscured. they are called visibilitynotify events. BUT i am actually not sure (B if they will be received by inputonly windows. but thats the path you want to (B go. (B (B Whats input only windows? How can I make sure my window is not an InputOnly (B window but, whatever, else? (B (Binputonly windows are invisible windows. you can map,unmap, move, resize, get (Bevents (mouswe moves, button presses, key events etc.) on them, but they do not (Bvisually do anything on the screen. (B (B you could find if a window has been raised/lowered etc. by monitoring (B creatnotifies on root, then on every windows created monitor (B structurenotifies then look for configurenotify events and check the stacking (B sections (above, window, event). again - i dont know how well gdk(gtk) (B supports this part of x so you may have to dump into xlib. (B (B I don'tneccessarily need to do that. If it is possible to make sure that my (B window is raised on top off all, then I can simply monitor for this (B visibillitynotify, and raise it anyway. If it is not possible to create other (B window then this inputwindow then I can monitor this createnotify. How is this (B working? Does root then send me an event everytime a window is created? (B (Byes. every time a window is created (or destroyed etc. etc.) if you select for (Bthe right event mask (structure substructurenotify) x will tell u when the (Broot window and children of it change (created, destoryed, reparent, move, (Bresize, restack etc.) with events. this is close to what a window manager does (B(close, but not quite). i'd definitely suggets the inputonly window. u will (Bnever be ab;e to sensibly pass events on, but in the area of the screen the (Binputonly window lives, you can "eat" all the events yourself :) (B (B hmm how is it meant to work? mouse goes to left or right side of window, (B launcher buttons pop up and u click one to run something? (B (B Yes. The nice thing of this tool is, that it always works. You don't need to (B have a window or a bar or anything on the screen which you need to access. (B (Bhmm - in which case here is what i'd recommend. you use an inputonly window - (Bstick in a corner, edge etc. where u want the "activate" area of the screen (B(that activates the toolbar), then pop up the toolbar (so its raised on TOP of (Byour input only window - have this as an exception in general to maintaining the (Bon-top stacking of your inputonly window) then if the mouse exits that toolbor, (Bhide it again. monitor stacking as mentioned above with structure (Bsubstructurenotify mask set on root and handle the events. the problemn here is (Breally gdk/gtk. i dont know how well it will deal with this. if u did it in xlib (Bu'd be fine, but i am not sure if gdk/gtk will be 100% happy. others might know (Bif ti will or will not. (B (B It's really usefull to have around, thats why I decided to port it to linux. (B (B -- (B Gerhard Gruber (B (B F_r jedes menschliche Problem gibt es immer eine einfache L_sung: (B Klar, einleuchtend und falsch. (Henry Louis Mencken) (B (B ___ (B Devel mailing list (B [EMAIL PROTECTED] (B http://XFree86.Org/mailman/listinfo/devel (B (B (B-- (B--- Codito, ergo sum - "I code, therefore I am" (BThe Rasterman (Carsten Haitzler)[EMAIL PROTECTED] $B7'<*(B - $Bhttp://XFree86.Org/mailman/listinfo/devel
Re: Server regeneration no longer works
On Thu, Oct 30, 2003 at 08:51:48AM +0100, Frank Gießler wrote: David Dawes wrote: snip cvs rdiff -D 15 October 2003 -D 16 October 2003 Xserver/os gives: snip Thanks, it is indeed the same bug. I've marked the one in Bugzilla as fixed. Is there an easy way to figure out the dates for the diffs? I chose them based on the date of the message of mine you quoted that mentioned the fix :-) Also, cvsweb.xfree86.org allows easy viewing of changes. That's how I found out. But one has to know which files to investigate, and if more than one file is involved it can be a real PITA. Or am I missing something? The cvs-commit list (and its archive) are useful for this. The commit messages will show you exactly what the revisions are for each changed file. I'd recommend that anyone following XFree86 development subscribe to cvs-commit (see http://www.xfree86.org/lists.html). David -- David Dawes X-Oz Technologies www.XFree86.org/~dawes www.x-oz.com ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
