From owner-freebsd-current Fri Nov 26 0:17:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id B278B14CC1; Fri, 26 Nov 1999 00:17:36 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA02778; Fri, 26 Nov 1999 09:16:14 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Matthew N. Dodd" Cc: Assar Westerlund , obrien@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: 3c509b getting `eeprom failed to come ready' in current In-reply-to: Your message of "Fri, 26 Nov 1999 00:07:54 EST." Date: Fri, 26 Nov 1999 09:16:14 +0100 Message-ID: <2776.943604174@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , "Matthew N. Dodd" writes: >Yes, and when I converted if_ep to newbus I mentioned that hardwire was no >longer supported. Couldn't we simply ignore such hardwiring (with a warning) if present ? >I'm a little annoyed that if_ep has issues working with if_ex/if_ie and >I'll add that to my list of things to look at when I get a chance to fix a >few outstanding issues with if_ep. Can we somehow mark the if_ep as "fickle hardware" so it gets probed before the if_ex/it_ie ? We used to have such a facility. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message