From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 03:42:17 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 486E616A4CE; Tue, 20 Jul 2004 03:42:17 +0000 (GMT) Received: from sakura.ninth-nine.com (sakura.ninth-nine.com [219.127.74.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD20C43D4C; Tue, 20 Jul 2004 03:42:16 +0000 (GMT) (envelope-from nork@FreeBSD.org) Received: from melfina.ninth-nine.com ([IPv6:2002:d312:f91e::1]) (authenticated bits=0) by sakura.ninth-nine.com (8.12.11/8.12.11/NinthNine) with ESMTP id i6K3g7tx052880; Tue, 20 Jul 2004 12:42:07 +0900 (JST) (envelope-from nork@FreeBSD.org) Date: Tue, 20 Jul 2004 12:42:00 +0900 From: Norikatsu Shigemura To: freebsd-current@FreeBSD.org Message-Id: <20040720124200.03ce0672.nork@FreeBSD.org> In-Reply-To: <87hds3pfgv.wl@tora.nunu.org> References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> <200407182039.10773.dfr@nlsystems.com> <16634.54674.966908.540880@grasshopper.cs.duke.edu> <200407182104.53221.dfr@nlsystems.com> <87hds3pfgv.wl@tora.nunu.org> X-Mailer: Sylpheed version 0.9.12-gtk2-20040622 (GTK+ 2.4.4; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.5.3 (sakura.ninth-nine.com [IPv6:2002:db7f:4a79::1]); Tue, 20 Jul 2004 12:42:07 +0900 (JST) cc: simokawa@FreeBSD.org cc: gallatin@cs.duke.edu Subject: Re: Excellent job on the firewire support! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jul 2004 03:42:17 -0000 On Tue, 20 Jul 2004 11:41:52 +0900 Hidetoshi Shimokawa wrote: > > to the author and he might find the time for it :-) > It is not enough :-< I lack the knowledge of BIOS/PCI(and ACPI?). > Once we can access the OHCI register via PCI in the loader, > the remaining part is relatively easy as you described. > I need some help for this part. I suppose that implementing dcons > in the loader is architecture dependent. I want it! :-) Anyone, do you try to support dcons on BOOT? If someone do it, we will be able to change serial console - sio to fwohci.