[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

LEO support and accelerated creator support



Ben Collins <bcollins@debian.org> writes:

> On Sat, Apr 24, 1999 at 02:54:48PM -0400, Steve Dunham wrote:
> > > > I'll try the libc packages too.  You were also working on an a sparc64
> > > > compiler, right?  What's the status on that.  If egcs 1.1.2 can
> > > > correctly compile the sparc64 kernel I'd rather use it than the
> > > > current egcs64 package (which gets internal errors on the 3com
> > > > driver).

> > I just tried the latest glibc packages.  Works on the Ultra5 and SS20
> > with 2.2.5cvs kernel.  Doesn't work with the slink 2.2.1 kernel on the
> > SS20 (init wedges).

> > I wonder if the sparc32 vfork patch is in the 2.2.6 kernel.

> Damnit...we will have to depend on a certain kernel-image package for
> glibc 2.1.1 then. We need to get source and debs of the latest cvs
> kernel (probably just diff the 2.2.5 in unstable with the 2.2.5+cvs you
> used, then upload a patch) in the dist before we can put glibc 2.1.1 in
> there.

I don't have the 2.2.5cvs source anymore (toasted the partition so I
could build X on it).  However, I do have:

cvs 2.2.7 kernel (for sparc32, the sparc64 one is building now) at:

  deb http://www.cse.msu.edu/debian slink kernel

XFree86_3.3.3.1-0pre1v3 with accelerated LEO support and accelerated
FFB (Creator) support added.  It needs a kernel with LEO support compiled
in, and it was compiled against your libc-2.1.1, so sparc32 users will
have to use the 2.2.7 kernel or build their own.

The Creator support is said to require "recent" kernels.  I don't know
if 2.2.1 is recent enough, the 2.2.7 kernel should work fine when I
get done compiling it.

Preliminary packages at:

  deb http://www.cse.msu.edu/debian slink x3331

(You will also have to "ln -s /dev/fb0 /dev/fb".)


Branden has released XFree86_3.3.3.1-1 now, so I'll make proper diffs
against that package, and rebuild against glibc_2.0.105 sometime in
the next week or so.


Steve
dunham@cse.msu.edu


Reply to: