From owner-freebsd-current  Sat Feb  3 14:39:45 2001
Delivered-To: freebsd-current@freebsd.org
Received: from ntlg.sibnet.ru (dns.sibnet.ru [217.70.96.34])
	by hub.freebsd.org (Postfix) with ESMTP
	id CA5C137B401; Sat,  3 Feb 2001 14:39:23 -0800 (PST)
Received: from tlg2-ppp5.sibnet.ru (tlg2-ppp5.sibnet.ru [217.70.97.116])
	by ntlg.sibnet.ru (8.9.3+Sun/8.9.3) with ESMTP id BAA00646;
	Sun, 4 Feb 2001 01:39:21 +0300 (MSK)
Date: Sun, 4 Feb 2001 04:44:30 +0600 (GMT+6)
From: "Semen A. Ustimenko" <semenu@FreeBSD.org>
X-Sender: semenu@default
To: freebsd-current@FreeBSD.org
Cc: freebsd-hackers@FreeBSD.org, Michael Smith <msmith@FreeBSD.org>
Subject: PCI bus code & SMC9432 behaviour
Message-ID: <Pine.BSF.4.21.0102040425480.706-100000@default>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi!

I got into a following problem with subj:

During boot process, the card can be in power down mode. This can be
cause MEMEN and PORTEN bits not set up correctly (set to 0) during boot.
This bits not set will cause no resources for this device, thus later a
bus_alloc_resource() call will fail. 

I succeed to with adding resources manualy by calling bus_set_resource(),
but it seems to me a wrong idea. I supposed the pci code analyze that
driver sets/clears PORTEN or MEMEN bit, and thus add/remove appropriate
resources... This wont be difficult.

If you say this is a good idea, i can provide a patch myself, though i
haven't thouched the pci code before.

Good luck!



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message