Date: Thu, 18 Dec 1997 16:35:00 -0700 From: Nate Williams <nate@mt.sri.com> To: Ted Faber <faber@ISI.EDU> Cc: ambrisko@whistle.com, nate@mt.sri.com, freebsd-mobile@FreeBSD.ORG Message-ID: <199712182335.QAA18248@mt.sri.com> In-Reply-To: <199712182328.PAA23547@tnt.isi.edu> References: <199712182328.PAA23547@tnt.isi.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> Nate, here's a patch to -current that addresses the issue Doug raised > of CL-PD6832's that are initialized to odd ports and also allows users > to specify a port for their pcic other than the bios default port. Ugh. I really dislike adding 'yet another' config option. > Right now, this added flexibility isn't worth much, because > /sys/pccard/pcic.c has its ports essentially hardwired at 0x3e0, but > it seems cleaner to me anyway. It should provide a way for users with > chips initialized to standard CArdBus operation to switch to 16-bit > legacy mode. So, wouldn't it be 'easier' to just hard-code the port to 0x3e0, since that's where the code expects to find it? > Doug and I (mostly Doug, since I don't see the same problems in my > setup) are still poking around with his interrupts so there may be > some more fixes to come, but this seems solid (and works fine on my > box with PCIC_PCI_PORT defined or not (defining it to other than 0x3e0 > boots, but the pcic driver doesn't find the chip). Then why allow the user to set it? Why not just hard-code it to 0x3e0 *always*? What would that break? Nate [ patch deleted ]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199712182335.QAA18248>