From owner-freebsd-stable Sun Oct 29 23:32:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E5BAB37B479; Sun, 29 Oct 2000 23:32:06 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e9U7W5n16965; Mon, 30 Oct 2000 00:32:05 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA68447; Mon, 30 Oct 2000 00:32:05 -0700 (MST) Message-Id: <200010300732.AAA68447@harmony.village.org> To: Soren Schmidt Subject: Re: pccard ATA support broken in -STABLE Cc: jim@FreeBSD.org, sos@FreeBSD.org, stable@FreeBSD.org, developers@FreeBSD.org In-reply-to: Your message of "Mon, 30 Oct 2000 08:24:44 +0100." <200010300724.IAA22083@freebsd.dk> References: <200010300724.IAA22083@freebsd.dk> Date: Mon, 30 Oct 2000 00:32:05 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200010300724.IAA22083@freebsd.dk> Soren Schmidt writes: : Are you _sure_ that is the problem, as it has been like that for a : long time in -current, and I'm pretty sure it still worked after : that. Yes. I'm sure it is the problem. jmb and I spent a long time looking at it at bsdcon. : > I don't know how to fix this sort of backing out a lot of stuff, and : > I'm loathe to do that. We must have a fix for it because ata support : > is too important to shipwith broken. : > : > And we knew about this in -current and were poo-poo'd :-( : : I dont have any PCCARD ATA HW here at all, so I can't do much about : it without somebody else finding the cause, then I can fix it... : or somebody get me a PCCARD ATA thingy on my desk... Send me your address. I'll ship you one when I return on wednesday with a 10MB ata card. I have several extra. : Phk told me yesterday that it worked on the std secondary address and : irq 15, but failed on some abitrary address irq something, that : suggests to me that the irq routing is broken somewhere... I've seen it broken on my laptop which has known good irq routing. :-) Doesn't matter what irq/address is used. It of course fails for ata controllers in conflict with built in hardware :-) It used to work flawlessly. -stable worked before you mfc. I've been traveling so I don't know the exact status in stable, but it is exactly the same failure mode as -current has. I'll know more later in the week. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message