From owner-freebsd-sparc64@FreeBSD.ORG Mon Oct 27 08:00:38 2003 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DEA8316A4B3 for ; Mon, 27 Oct 2003 08:00:38 -0800 (PST) Received: from decstation.larkowski.net (d47-69-13-15.col.wideopenwest.com [69.47.15.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CBFB43FDF for ; Mon, 27 Oct 2003 08:00:37 -0800 (PST) (envelope-from peter@larkowski.net) Received: from localhost (peter@localhost)h9RG0Z801624 for ; Mon, 27 Oct 2003 11:00:35 -0500 (EST) Date: Mon, 27 Oct 2003 11:00:32 -0500 (EST) From: peter@larkowski.net To: sparc64@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Parallel Port? X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2003 16:00:39 -0000 Are there plans to support parallel ports in the near future? I have an Ultra Axe board and I'd like to use it as a print server (among other things), but when I uncomment device ppc, the kernel build fails immediately as that device isn't defined, and loading modules for lpt, ppbus, or ppi all fail with either link_elf: symbol ppbus_io_desc undefined or link_elf: symbol ppb_request_bus undefined, meaning I need device ppc I assume. If there aren't plans for parallel port support soon, what all would need to be done (ie, just device ppc porting or is it more complex than that?)