Date: Tue, 20 May 1997 10:40:58 +0200 (MET DST) From: Wolfgang Helbig <helbig@MX.BA-Stuttgart.De> To: FreeBSD-hackers@FreeBSD.ORG Subject: option "CMD640" in RELENG-2.2 (fwd) Message-ID: <199705200840.KAA06844@helbig.informatik.ba-stuttgart.de>
next in thread | raw e-mail | index | archive | help
Hi, For some reason, this message did not make it to the list, at least it did not show up here again, so I repost it. Maybe someone played with dtmail at FreeBSD.ORG :-) ----- Forwarded message from helbig ----- >From helbig Sat May 17 21:23:49 1997 Subject: option "CMD640" in RELENG-2.2 To: hackers@FreeBSD.ORG Date: Sat, 17 May 1997 21:23:49 +0200 (MET DST) Cc: se@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] Hi, How about putting the options "CMD640" line in GENERIC for RELENG-2.2? The CMD640 workaround was committed to RELENG-2.2 (and -current) right before the 2.2-RELEASE was cut. Thank you, STefan, for your reviews, suggestions and commissions! The CMD640 option was included in the current GENERIC file and I believe it was exposed to quite a number of tests since then, especially in the 3.0SNAPS, so it seems safe to enable it in 2.2 GENERIC as well. This option will take effect on the wd driver only if the PCI subsystem detects this bogus chip. Enabling it in the GENERIC kernel will help those unfortunate beaten with this chip to install and use FreeBSD w/o the need to build a customized kernel and a boot floppy or to reconfigure the IDE hardware each time they want to use fixit.flp. Since I am not a committer -- not even a contributor :-( -- I'd like to ask someone with more power to commit the one line change in GENERIC and update the documentation in the FAQ, relnotes.hlp and hardware.hlp to reflect the fact that the CMD640 workaround is is not disabled by default anymore. Thanks in advance Wolfgang ----- End of forwarded message from helbig -----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705200840.KAA06844>