From owner-freebsd-ia64@FreeBSD.ORG Wed Nov 26 21:25:08 2003 Return-Path: Delivered-To: freebsd-ia64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61C3116A4CE; Wed, 26 Nov 2003 21:25:08 -0800 (PST) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2524443FEC; Wed, 26 Nov 2003 21:25:06 -0800 (PST) (envelope-from marcel@xcllnt.net) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by ns1.xcllnt.net (8.12.9/8.12.9) with ESMTP id hAR5P5EG047214; Wed, 26 Nov 2003 21:25:05 -0800 (PST) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp01.pn.xcllnt.net (localhost [127.0.0.1]) hAR5P5Wx012662; Wed, 26 Nov 2003 21:25:05 -0800 (PST) (envelope-from marcel@dhcp01.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.12.10/8.12.10/Submit) id hAR5P5RY012661; Wed, 26 Nov 2003 21:25:05 -0800 (PST) (envelope-from marcel) Date: Wed, 26 Nov 2003 21:25:05 -0800 From: Marcel Moolenaar To: Kris Kennaway Message-ID: <20031127052505.GA12627@dhcp01.pn.xcllnt.net> References: <20031127042759.GA60140@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031127042759.GA60140@xor.obsecurity.org> User-Agent: Mutt/1.5.4i cc: anholt@FreeBSD.org cc: re-ia64@FreeBSD.org cc: ia64@FreeBSD.org Subject: Re: XFree86-4-Server marked NOT_FOR_ARCHS=ia64? X-BeenThere: freebsd-ia64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the IA-64 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Nov 2003 05:25:08 -0000 On Wed, Nov 26, 2003 at 08:28:00PM -0800, Kris Kennaway wrote: > For some reason XFree86-4-Server is marked NOT_FOR_ARCHS=ia64, which > means it cannot be built for the disc 1 packages. What is supposed to > be going on here? Should XFree86 be depending on a different server > port for ia64, or is this port just broken on ia64 and in need of a > fix? I have the necessary patches to make it build. However, there are kernel issues that are non-trivial to fix. Those are mainly caused by the X server accessing the hardware directly. Our VM is not capable to provide memory mappings with specific attributes to allow processes to access memory mapped hardware. This is needed on ia64. Secondly, the X server needs syscons which is too i386 centric to be used on ia64 without porting it. The end result will invariably be something that's kludgy and awkward. Just like on alpha and sparc64. I'm looking at something else. FYI, -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net