From owner-freebsd-hackers Sat Oct 14 20:44:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from spock.org (cm-24-169-6-210.nycap.rr.com [24.169.6.210]) by hub.freebsd.org (Postfix) with ESMTP id C9F7137B66D for ; Sat, 14 Oct 2000 20:44:47 -0700 (PDT) Received: (from jon@localhost) by spock.org serial EF600Q3T-B7F8823e9F3ifb77289F7T for hackers@freebsd.org; Sat, 14 Oct 2000 23:44:41 -0400 (EDT) (envelope-from jon) Date: Sat, 14 Oct 2000 23:44:41 -0400 From: Jonathan Chen To: hackers@freebsd.org Subject: PCI secondary bus Message-ID: <20001014234441.F78298@spock.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: telnet/1.1x Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While writing the new cardbus code, I ran into a problem where certain BIOSes (Dells in particular) does not initialize the pci configuration space of the pci to cardbus bridge. On a "normal" laptop, the BIOS will fill in a memory address, irq lines, and the secondary and subordinate bus numbers. On a dell laptop, those would be left as 0. I could work around the memory/irq issues, but I have no clue what to fill in for the secondary and subordinate bus numbers. Is there a magical function (in kernel, pcibios or otherwise) that would generate these values for me? And if not, how do I get the numbers? Would it be alright if I assign an arbitrary number as long as there is no conflict? Any help would be appreciated. Thanks. -- (o_ 1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2 _o) \\\_\ Jonathan Chen jon@spock.org /_/// <____) No electrons were harmed during production of this message (____> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message