Date: Tue, 2 Apr 1996 11:25:58 +0930 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: Brett_Glass@ccgate.infoworld.com (Brett Glass) Cc: Brett_Glass@ccgate.infoworld.com, jkh@time.cdrom.com, hardware@freebsd.org Subject: Re: Some solutions to disk problems.... I think. Message-ID: <199604020155.LAA08971@genesis.atrad.adelaide.edu.au> In-Reply-To: <9603018283.AA828371256@ccgate.infoworld.com> from "Brett Glass" at Mar 31, 96 08:10:32 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Brett Glass stands accused of saying: > > The code should probably be activated by flags (one per drive for each IDE > interface). What is the proper procedure for implementing and assigning a > device driver flag, and making sure that there are no conflicts? Are any > flag bits reserved in FreeBSD disk drivers? Don't do it this way, particularly since you are adding a command to activate a vendor-specific function. You should create a rogues table, and define your Seagate fix as a 'rogue feature', triggered by the drive id in wdattach(). If the feature were _standard_, then you might want to look at a simple wdcontrol utility and a set of ioctls. > --Brett -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604020155.LAA08971>