Permalink
Browse files

Added chromium 1.9 source

  • Loading branch information...
0 parents commit 7d3a3e1eaf3765a07f00c9c17f2be74d5acd6b50 @excid3 committed Sep 18, 2010
Showing 1,191 changed files with 320,181 additions and 0 deletions.
@@ -0,0 +1,5 @@
+.cvsignore
+bin
+lib
+built
+
@@ -0,0 +1,61 @@
+This Chromium distribution contains information and code which is
+covered under the following notice:
+
+Copyright (c) 2002, The Regents of the University of California.
+Produced at the Lawrence Livermore National Laboratory
+For details, contact: Randall Frank (rjfrank@llnl.gov).
+UCRL-CODE-2002-058
+All rights reserved.
+
+This file is part of Chromium. For details, see accompanying
+documentation.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+Redistributions of source code must retain the above copyright notice, this
+list of conditions and the disclaimer below.
+
+Redistributions in binary form must reproduce the above copyright notice,
+this list of conditions and the disclaimer (as noted below) in the
+documentation and/or other materials provided with the distribution.
+
+Neither the name of the UC/LLNL nor the names of its contributors may be
+used to endorse or promote products derived from this software without
+specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OF THE UNIVERSITY OF
+CALIFORNIA, THE U.S. DEPARTMENT OF ENERGY OR CONTRIBUTORS BE LIABLE FOR ANY
+DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGE.
+
+Additional BSD Notice
+
+1. This notice is required to be provided under our contract with the U.S.
+ Department of Energy (DOE). This work was produced at the University of
+ California, Lawrence Livermore National Laboratory under Contract No.
+ W-7405-ENG-48 with the DOE.
+
+2. Neither the United States Government nor the University of California
+ nor any of their employees, makes any warranty, express or implied, or
+ assumes any liability or responsibility for the accuracy, completeness,
+ or usefulness of any information, apparatus, product, or process
+ disclosed, or represents that its use would not infringe privately-owned
+ rights.
+
+3. Also, reference herein to any specific commercial products, process, or
+ services by trade name, trademark, manufacturer or otherwise does not
+ necessarily constitute or imply its endorsement, recommendation, or
+ favoring by the United States Government or the University of
+ California. The views and opinions of authors expressed herein do not
+ necessarily state or reflect those of the United States Government or
+ the University of California, and shall not be used for advertising or
+ product endorsement purposes.
@@ -0,0 +1,29 @@
+This Chromium distribution contains information and code which is
+covered under the following notice:
+
+/*
+ * Copyright 2001,2002 Red Hat Inc., Durham, North Carolina.
+ *
+ * All Rights Reserved.
+ *
+ * Permission is hereby granted, free of charge, to any person obtaining
+ * a copy of this software and associated documentation files (the
+ * "Software"), to deal in the Software without restriction, including
+ * without limitation on the rights to use, copy, modify, merge,
+ * publish, distribute, sublicense, and/or sell copies of the Software,
+ * and to permit persons to whom the Software is furnished to do so,
+ * subject to the following conditions:
+ *
+ * The above copyright notice and this permission notice (including the
+ * next paragraph) shall be included in all copies or substantial
+ * portions of the Software.
+ *
+ * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+ * EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+ * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+ * NON-INFRINGEMENT. IN NO EVENT SHALL RED HAT AND/OR THEIR SUPPLIERS
+ * BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
+ * ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+ * CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+ * SOFTWARE.
+ */
32 LICENSE
@@ -0,0 +1,32 @@
+Copyright (c) 2002, Stanford University
+All rights reserved.
+
+Some portions of Chromium are copyrighted by individiual organizations.
+Please see the files COPYRIGHT.LLNL and COPYRIGHT.REDHAT for more
+information.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+* Redistributions of source code must retain the above copyright notice,
+ this list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+* Neither the name of Stanford University nor the names of its contributors
+ may be used to endorse or promote products derived from this software
+ without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
+LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
+INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
+CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGE.
@@ -0,0 +1,23 @@
+# Copyright (c) 2001, Stanford University
+# All rights reserved.
+#
+# See the file LICENSE.txt for information on redistributing this software.
+
+TOP = .
+
+include $(TOP)/arch.mk
+
+ifeq ($(USE_DMX), 1)
+DMX_DIR = dmx
+endif
+
+ifeq ($(DOXYGEN), 1)
+DOXYGEN_DIR = doxygen
+endif
+
+SUBDIRS = util mothership spu_loader packer state_tracker $(DMX_DIR) \
+ unpacker dlm spu app_faker opengl_stub crserverlib crserver \
+ crutapi crutclientapi crutproxy crutserver progs $(DOXYGEN_DIR)
+
+include ${TOP}/cr.mk
+
69 TO-DO
@@ -0,0 +1,69 @@
+Finish up tilesort glReadPixels pixelstore parameters.
+
+Grep the code for 'XXX' for miscellaneous loose ends.
+
+In state_polygon_gen.c in crStatePolygonSwitch() we need a better test
+for updating the polygon stipple. As-is we're calling diff.PolygonStipple
+all the time.
+
+Separate auto-start controls for server and app nodes.
+
+Don't require a program argument in sort-last template.
+
+Sort-last template seems to require all command line args, instead of none.
+
+Wes Bethel:
+ While driving the GUI config tool, I started out with a tilesort
+ template. On the app node, I added an array SPU before the tilesort
+ spu, then save the config file. The config file doesn't contain the
+ array spu I asked for. There may be related problems for other
+ app-side SPU additions - I've not checked.
+
+Remove #include <math.h> ; create a cr_math.h file instead.
+ Wrapper for absf() in server_tiles.c
+
+Rewrite the opengl_stub/defs.py file so that we don't need to manually
+update the stack_sizes array. The sizes should be obtained by calling
+apiutil.PacketLength() or something similar.
+
+Check unpacker/unpack.c for unfinished special case functions.
+
+Implement GL_EXT_draw_range_elements extension
+
+In DLM's BindTexture function, record the texture ID with the display
+list info so that we know which textures are bound in a list. Then, in
+tilesort, before glCallList, flush (state-diff) all those textures to
+be sure the servers' texture are up to date. We currently flush all
+textures prior to glCallList (but that code's disabled).
+
+
+
+
+CRServer context management issue
+---------------------------------
+
+In the CRServer the Cr state tracker is used for "soft" context switching
+between multiple clients. This is generally faster/cheaper than calling
+glXMakeCurrent() to do context switches.
+
+So, the CRServer asks the first SPU to create one rendering context which is
+thereafter used by all clients and all their contexts.
+
+The problem is, this single rendering context may not be compatible with
+all the different windows we might create on the server side.
+
+We might create several windows, each with different visuals/pixelformats
+(i.e. with/without stencil, accum, alpha, etc). When we try to bind the
+rendering context to a window, the underlying GLXContext and X Window
+might not be compatible.
+
+Currently, there's a hack in crServerDispatchCreateContext() to try to
+work around this, but it's far from ideal.
+
+The right solution is for the CRServer to create a different rendering
+context for each different visual that's requested. Then, when we have
+to do a context switch (either from one client to another, or between two
+contexts belonging to one client), do a "soft" context switch if the
+contexts have the same visual. Otherwise, do a "hard/GLX" context switch
+if the contexts have different visuals.
+
Oops, something went wrong.

0 comments on commit 7d3a3e1

Please sign in to comment.