Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 21 Apr 2000 09:32:53 +0100
From:      David Pick <D.M.Pick@qmw.ac.uk>
To:        freebsd-bugs@FreeBSD.org, imp@FreeBSD.org, nate@yogotech.com
Cc:        "Sean O'Connell" <sean@stat.Duke.EDU>, robert bowen <robert@braingarage.com>
Subject:   Re: kern/18118 and kern/9030 on silly PCIC controllers
Message-ID:  <E12iYru-000C9M-00@dialup-janus.css.qmw.ac.uk>

next in thread | raw e-mail | index | archive | help

Nate (no longer really responsible although his EMail address is still in
the code!) advised me to send a query to the "mobile" list (which I did
while the PR kern/18118 was already submitted) and both:
	"Sean O'Connell" <sean@stat.Duke.EDU>
and	robert bowen <robert@braingarage.com>
advised me in EMails I downloaded this morning how to do it by using
	device pcic0 at isa?
in the configuration file instead of the default version. Sean also advised
appending:
	machdep.pccard.pcic_irq="0"
to "/boot/loader.conf". Having done these, and rebuilt the kernel, things
now work and PCCards are recognised and started successfully without
having to patch the code at all. Thanks a lot, all of you. I can now
proceed with putting FreeBSD 4.0 on my various personal and work laptops,
all of which get used at various times for network monitoring, &c, so I'm
grateful I can get on with this upgrade over the extended weekend.

Just one question with this fix - does it stop cards being accessed as
PCCard cards in 32-bit mode because they are seen as being on the
16-bit ISA bus or does it only affect the PCIC(s) themselves? (One of
my 100Mbit Ethernet cards is a CardBus card.)

I don't want to sound ungrateful, but this hassle for all of us could have
been avoided by a little more documentation of the configuration line in
the LINT configuration file, which I always read because it tends to
document all sorts of flags, &c, for the configuration options. I had
(of course) already consulted the other documentation (man pages, &c) that
I could find and found nothing useful (for this problem!). It would also be
nice if the "fix" could be documented in the PR database along with the
closures of both PRs.

Thanks again for all your help. Generally I find FreeBSD very reliable
and stable (which is why I use it!) and we often find that problems
other people have at work with Linux are solved by references to the
FreeBSD documentation! However, this time, and with a rather involved
bit of code to read, the source wasn't quite enough for a rapid fix.

-- 
	David Pick
	D.M.Pick@qmw.ac.uk
a.k.a.	Hostmaster@qmw.ac.uk




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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E12iYru-000C9M-00>