From owner-freebsd-mobile@FreeBSD.ORG Fri Feb 22 15:04:14 2008 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56CE716A400 for ; Fri, 22 Feb 2008 15:04:14 +0000 (UTC) (envelope-from gdt@ir.bbn.com) Received: from fnord.ir.bbn.com (fnord.ir.bbn.com [192.1.100.210]) by mx1.freebsd.org (Postfix) with ESMTP id 3494413C4EC for ; Fri, 22 Feb 2008 15:04:13 +0000 (UTC) (envelope-from gdt@ir.bbn.com) Received: by fnord.ir.bbn.com (Postfix, from userid 10853) id DD15A52EA; Fri, 22 Feb 2008 10:04:12 -0500 (EST) X-Hashcash: 1:20:080222:freebsd-mobile@freebsd.org::/cZszzTGBGi5V1E/:000000000000000000000000000000000001KvG From: Greg Troxel To: Andreas Wetzel References: <47BE9CBC.6010500@gmx.net> <47BED4A6.7040501@gmx.net> X-Hashcash: 1:20:080222:mickey242@gmx.net::2gVoaRwVutjmb09I:000000000000000000000000000000000000000000000LO4 Date: Fri, 22 Feb 2008 10:04:12 -0500 In-Reply-To: <47BED4A6.7040501@gmx.net> (Andreas Wetzel's message of "Fri, 22 Feb 2008 14:56:54 +0100") Message-ID: User-Agent: Gnus/5.110007 (No Gnus v0.7) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-mobile@freebsd.org Subject: Re: ThinkPad 600 - CardBus inoperative X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Feb 2008 15:04:14 -0000 hw.pci.link.LNKA.irq=11 hw.pci.link.LNKB.irq=10 hw.pci.link.LNKC.irq=7 hw.pci-link.LNKD.irq=7 That looks more or less like the equivalent of NetBSD's PCI_INTR_FIXUP. My ThinkPad 600 is a model 2645-450 with a total of 288 MB RAM installed (2 * 128MB + 32 MB internal memory). I know the 600 has several IRQ related I've never see a -450, but probably it has the same motherboard as a 41U. I would suggest enabling the highest level of verbosity possible for irq/pcibios stuff. You might try booting netbsd 4 or current to see if that works, and if so enabled high verbosity and figure out what it's doing and then spiff up freebsd to have the same workaround. I'm sure there are many things in netbsd that have been fixed via the reverse path - I'm not claiming 'x is better', but more that each probably has hardware workarounds the other doesn't and cross-porting them is a good thing.