Date: Tue, 16 Jan 1996 15:17:17 +0200 (EET) From: "Andrew V. Stesin" <stesin@elvisti.kiev.ua> To: stable@FreeBSD.org Subject: 2.1 config and IObase constants strangeness Message-ID: <199601161317.PAA14528@office.elvisti.kiev.ua>
next in thread | raw e-mail | index | archive | help
Hello, while I'm busy with equipping a new box, I discovered an unexpected config (8) behavior. As the hardware configuration is comparatively complex, IObase space is filled in an unusual manner, I'm afraid of overlaps and I never bothered remembering all "magic" default IObase values for different devices (like IO_FD1 == 0x3f0 for fdc0), I changed the "magic" constants in the definitions of fdc0 and sio[01] to their hex values, (i.e. "IO_FD1" to 0x3f0 for fdc0 line) for fdc0, sio0, sio1 devices. Surprizingly, config (8) didn't tell me about any errors, but resulting ioconf.c has become broken: config (8) inserted extra (erroneous) declarations for siointr (two times) and fdintr. The system is 2.1-very-late-beta (951026-SNAP). Is this a correct behaviour? (Or maybe fixed in -current, as always? :) Aren't magic IObase constants considered harmful? -- With best regards -- Andrew Stesin. +380 (44) 2760188 +380 (44) 2713457 +380 (44) 2713560 An undocumented feature is a coding error.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601161317.PAA14528>