Re: kern/7606 (isa pcic + isapnp pcic = bogus device attachments in 1.4)

[Quentin Garnier <cube%cubidou.net@localhost>]

The following reply was made to PR kern/7606; it has been noted by GNATS.

From: Quentin Garnier <cube%cubidou.net@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: dh%netbsd.org@localhost
Subject: Re: kern/7606 (isa pcic + isapnp pcic = bogus device attachments
        in 1.4)
Date: Tue, 13 Jan 2009 16:29:42 +0100

 --eEXhUPuSAf+QFVIn
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Mon, Dec 29, 2008 at 10:04:47AM +0000, dholland%NetBSD.org@localhost wrote:
 > Synopsis: isa pcic + isapnp pcic =3D bogus device attachments in 1.4
 >=20
 > State-Changed-From-To: feedback->open
 > State-Changed-By: dholland%NetBSD.org@localhost
 > State-Changed-When: Mon, 29 Dec 2008 10:04:47 +0000
 > State-Changed-Why:
 > Submitter can't test.
 > I'm inclined to rule that we also don't care, and therefore this PR should
 > just be closed. Anyone reading this have an opinion one way or another?
 
 I don't see any description of a problem in the PR.  The PCMCIA
 controler seems to respond fine in both address ranges, the one
 discovered by ISA PnP and the one specified in the config file on the
 ISA bus.
 
 That kind of stuff can always happen with ISA devices, and that's why
 you build a custom kernel in such situations.  Now, if the PR was that
 the device doesn't work (it does say it's "losing", but it doesn't
 mention any symptom other than the fact the device is discovered twice),
 then there'd be something to talk about, but all I see here is assumably
 a single device responding at two different address ranges.  There isn't
 much one can do about it.
 
 I'd just close that PR.
 
 --=20
 Quentin Garnier - cube%cubidou.net@localhost - cube%NetBSD.org@localhost
 "See the look on my face from staying too long in one place
 [...] every time the morning breaks I know I'm closer to falling"
 KT Tunstall, Saving My Face, Drastic Fantastic, 2007.
 
 --eEXhUPuSAf+QFVIn
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.4.9 (NetBSD)
 
 iQEcBAEBAgAGBQJJbLNmAAoJENgoQloHrPno0YcH/1YTQRE4RZBDA34RYiXUeVuQ
 rhVtut+hWYidlfMP11FDBRZHVNI3XA7bgWT17HxhiWbBTDjzn0SS+k1NEW6CkdnU
 aeEI5Dgf9rR85hk1daq4XXIhT6Q44bFbaujZeYV3+K0EIzFpgDzptHg/lTC9hxxU
 xMKs25ff25biRTWxo6mqx6BMauDKUdxucZXXjkVlDr4u6M+uYgTcTFKYVkVQIuQ3
 2LEE8XTYEk4eiM4eBC8xZpNf1rH2vOMNmhgllF2tVVym1jmOFAYGx9h+agE1aZtB
 oFgixyCoAuQse7gDo+gm6MQ7mXyUDxvIq667vzOcXBQglnE74bUXoMMfclKCayw=
 =Uanj
 -----END PGP SIGNATURE-----
 
 --eEXhUPuSAf+QFVIn--