From owner-freebsd-current@FreeBSD.ORG Sun Jul 17 00:43:01 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 0535016A41C for ; Sun, 17 Jul 2005 00:43:01 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.village.org (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9C3443D49 for ; Sun, 17 Jul 2005 00:43:00 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1]) by harmony.village.org (8.13.3/8.13.3) with ESMTP id j6H0eb40023094; Sat, 16 Jul 2005 18:40:38 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 16 Jul 2005 18:41:20 -0600 (MDT) Message-Id: <20050716.184120.61267598.imp@bsdimp.com> To: thierry@herbelot.com From: "M. Warner Losh" In-Reply-To: <20050716.112411.52164710.imp@bsdimp.com> References: <20050716.105849.112624020.imp@bsdimp.com> <200507161914.23682.thierry@herbelot.com> <20050716.112411.52164710.imp@bsdimp.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: loss of PCMCIA ed(4) interface X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sun, 17 Jul 2005 00:43:01 -0000 In message: <20050716.112411.52164710.imp@bsdimp.com> "M. Warner Losh" writes: : In message: <200507161914.23682.thierry@herbelot.com> : Thierry Herbelot writes: : : > Also, do you have ed compiled into the kernel : : > or are you using a module? : : : : it's in the kernel : a straight, simple GENERIC. : : OK. I always use modules. I'll see if something is broken with : generic. OK. ed(4) is fine. Works great for me. However, there appears to be some issues with the Ricoh RF5C47x class of bridge chips. I have an old VAIO that exhibits similar problems to what you describe. I believe it is the difference between how the TI automatically powers up the card, and how the Ricoh requires an additional manual step that we're not doing right now. I'll try to find that step as soon as my system updates... Its a Pentium 300, so even an installworld takes a while (esp when you forget to enable soft updates...). Warner