Neal Pollack writes: > I express the same concerns as Alan; We need to use common code as much > as possible, and ensure > that we do not create custom branches/forks that double our costs. > Can this, and will this use, the same X.org code for this chip being > used for x86 today? > If not, why?
Not just the same code, but binaries delivered by the same consolidation. It would _not_ be acceptable to have some other consolidation copy over that source code so that it can build and deliver its own private version. I'd like to hear back from the submitter to clarify the situation, but I'm leaning towards the derail lever. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
