From owner-freebsd-current@FreeBSD.ORG Tue Jun 17 15:10:50 2003 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 0AE6637B404 for ; Tue, 17 Jun 2003 15:10:50 -0700 (PDT) Received: from ion.gank.org (ion.gank.org [198.78.66.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6757F43F75 for ; Tue, 17 Jun 2003 15:10:49 -0700 (PDT) (envelope-from craig@xfoil.gank.org) Received: from localhost (ion.gank.org [198.78.66.164]) by ion.gank.org (GankMail) with ESMTP id CB9542BC5A; Tue, 17 Jun 2003 17:10:48 -0500 (CDT) Received: from ion.gank.org ([198.78.66.164]) by localhost (ion.gank.org [198.78.66.164]) (amavisd-new, port 10024) with LMTP id 23515-01; Tue, 17 Jun 2003 17:10:48 -0500 (CDT) Received: from [172.22.8.188] (pix.corelab.com [12.45.169.2]) by ion.gank.org (GankMail) with ESMTP id 2ACAB2BBB7; Tue, 17 Jun 2003 17:10:48 -0500 (CDT) From: Craig Boston To: "M. Warner Losh" In-Reply-To: <20030617.072124.84361707.imp@bsdimp.com> References: <20030615211800.1a8c1ece.craig@xfoil.gank.org> <20030617.072124.84361707.imp@bsdimp.com> Content-Type: text/plain Message-Id: <1055887859.52524.60.camel@owen1492.uf.corelab.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 17 Jun 2003 17:11:11 -0500 Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: Multiple cardbus devices? (RFI) 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, 17 Jun 2003 22:10:50 -0000 On Tue, 2003-06-17 at 08:21, M. Warner Losh wrote: > Does the following, untested, patch help any better than your gross > kludges? Hrm, actually it seems to have made it worse... Now they don't attach at all. xl0: <3Com 3c575B Fast Etherlink XL> port 0x1000-0x107f mem 0x88000000-0x8800007f,0x88000080-0x880000ff irq 11 at device 0.0 on cardbus0 xl0: reset didn't complete xl0: command never completed! xl0: command never completed! xl0: eeprom failed to come ready xl0: failed to read station address device_probe_and_attach: xl0 attach returned 6 Please excuse any typos -- had to copy by hand as my NIC isn't working at the moment :) It used to map the second memory range starting at 88000100 > One might be able to share the 4k range between devices if > one had, say, two xl cards (I'd have to look hard at the code to be > sure), but very few machines are so memory constrained as to make that > a big win for the hair it would add to the code. I'm not sure that will work, at least not without special handling on the xl (or whatever device) driver's part. I have two xl cards and when they are mapped into the same 4k range the second one doesn't attach and the first stops working. They're not identical though -- one is a 575BT and the other is a 575CT. Craig