1.\" $NetBSD: fdc.4,v 1.1 2007/05/08 19:23:18 jnemeth Exp $ 2.\" 3.\" Copyright (c) 1996 The NetBSD Foundation, Inc. 4.\" All rights reserved. 5.\" 6.\" This code is derived from software contributed to The NetBSD Foundation 7.\" by Paul Kranenburg. 8.\" 9.\" Redistribution and use in source and binary forms, with or without 10.\" modification, are permitted provided that the following conditions 11.\" are met: 12.\" 1. Redistributions of source code must retain the above copyright 13.\" notice, this list of conditions and the following disclaimer. 14.\" 2. Redistributions in binary form must reproduce the above copyright 15.\" notice, this list of conditions and the following disclaimer in the 16.\" documentation and/or other materials provided with the distribution. 17.\" 3. All advertising materials mentioning features or use of this software 18.\" must display the following acknowledgement: 19.\" This product includes software developed by the NetBSD 20.\" Foundation, Inc. and its contributors. 21.\" 4. Neither the name of The NetBSD Foundation nor the names of its 22.\" contributors may be used to endorse or promote products derived 23.\" from this software without specific prior written permission. 24.\" 25.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS 26.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED 27.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 28.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS 29.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 30.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 31.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 32.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 33.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 34.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 35.\" POSSIBILITY OF SUCH DAMAGE. 36.\" 37.Dd May 8, 2007 38.Dt FD 4 sparc64 39.Os 40.Sh NAME 41.Nm fdc 42.Nd Sun SPARCstation i82072 or i82077 floppy disk controller driver 43.Sh SYNOPSIS 44.Cd "fdc0 at sbus0" Pq SBus based machines 45.Cd "fdc0 at ebus0" Pq PCI based machines 46.Cd "fd* at fdc0" 47.Sh DESCRIPTION 48This is the driver for the built-in floppy disk drive run by the 49.Tn Intel 50i82072 or i82077 controller chip found on the SPARCstation desktop 51systems, and other 52.Tn SPARC 53systems. 54.Pp 55Bits 56.Bq 0-3 57of the minor device number of the special files referring to this 58device encode the floppy density as follows: 59.Bl -tag -width indent -offset indent 60.It 0 613.5'' 1.44MB floppy diskettes. 62.It 1 633.5'' 720KB floppy diskettes. 64.It 2 653.5'' 360KB floppy diskettes. 66.It 3 673.5'' 1.2MB/NEC Japanese format floppy diskettes. 68.El 69.Sh FORMATTING 70The driver supports floppy disk formatting using the interfaces in 71.Aq Pa sys/fdio.h : 72.Pp 73.Bl -tag -width FDIOCFORMAT_TRACK -compact 74.It Dv FDIOCGETFORMAT Fa struct fdformat_parms 75Fetch current formatting parameters. 76This gets the default parameters 77for the open device if no parameters have been set during the session. 78.Pp 79.It Dv FDIOCSETFORMAT Fa struct fdformat_parms 80Set formatting parameters. 81The driver saves this state and it persists while the device is open. 82.Pp 83.It Dv FDIOCFORMAT_TRACK Fa struct fdformat_cmd 84Format a track on the medium. 85If this call returns 86.Er EINVAL , 87the track formatting parameters were out of range for the medium. 88If it returns 89.Er EIO , 90there was a medium error while formatting the track. 91.Pp 92.It Dv FDIOCSETOPTS Fa int 93Set driver options which persist until the device is closed. 94The 95options should be the logical OR of the desired values below: 96.Pp 97.Bl -tag -width FDOPT_NORETRY -compact 98.It Dv FDOPT_NORETRY 99Do not retry operations on failure 100.It Dv FDOPT_SILENT 101Do not print error messages to the console 102.El 103.Pp 104.It Dv FDIOCGETOPTS Fa int 105Fetch drive options. 106.El 107.Pp 108A typical use of the formatting facilities would be to open the device, 109call 110.Dv FDIOCGETFORMAT 111to fetch the current format parameters, perhaps 112change a parameter or two, display the formatting details to the user, 113and then call 114.Dv FDIOCSETFORMAT 115followed by a series of calls to 116.Dv FDIOCFORMAT_TRACK . 117.Sh SEE ALSO 118.Xr eject 1 , 119.Xr fdformat 1 120.Sh HISTORY 121The 122.Nm 123driver first appeared in 124.Nx 4.0 . 125.Sh BUGS 126The ebus attachment does not yet work. 127