From owner-freebsd-mobile Mon Apr 2 23:33:35 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 9D3D237B71B; Mon, 2 Apr 2001 23:33:28 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f336XSm20119; Mon, 2 Apr 2001 23:33:28 -0700 (PDT) Date: Mon, 2 Apr 2001 23:33:28 -0700 From: Alfred Perlstein To: John Baldwin Cc: Warner Losh , Mike Smith , John Reynolds , mobile@FreeBSD.org, qa@FreeBSD.org Subject: Re: followup to problems with 4.3-RC1 for laptops Message-ID: <20010402233328.B813@fw.wintelcom.net> References: <20010402122034.V813@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Mon, Apr 02, 2001 at 03:16:50PM -0800 X-all-your-base: are belong to us. Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * John Baldwin [010402 15:17] wrote: > > On 02-Apr-01 Alfred Perlstein wrote: > > * John Baldwin [010402 11:34] wrote: > >> > >> On 02-Apr-01 Alfred Perlstein wrote: > >> > Shouldn't the device be able to specify an all-or-nothing request? > >> > > >> > Perhaps something that needs fast interrupts will cause much hair > >> > pulling if it doesn't get one becasue of latency issues messing up > >> > the hardware. If the bus didn't grant a fast interrupt it could then > >> > declien to attach, perhaps spitting out a meaningful error message > >> > at the same time. > >> > >> True, no need for an error message, but I suppose one could do something > >> like > >> this then: > > > > Of course there's no need for an error message, everyone installing > > FreeBSD should be able to look at the kernel sources for his driver > > and figure out what's wrong with it. > > If you get an error in attach(), you will return it back up the chain and > device_probe_and_attach() will output a message such as: > > foo0: attach failed - returned 6 > > or some such. How about we just output this: ___ |__ \ / / |_| (_) I'm sure the experienced user will usually know what's wrong. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message