Date: Sun, 10 Feb 2013 14:53:48 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: "C. P. Ghost" <cpghost@cordula.ws> Cc: current@freebsd.org Subject: Re: Time to kill fdc ? Message-ID: <80600.1360508028@critter.freebsd.dk> In-Reply-To: <CADGWnjXv6YZQ83PjHuwP-rGyj6-j7=s6xiiMd8MMFP6vLo_buw@mail.gmail.com> References: <79955.1360494404@critter.freebsd.dk> <CADGWnjUn66K_Ngwn0Y_wyqX=RTT13h2FC23NeBH3WqNBBwd%2BXw@mail.gmail.com> <80406.1360502924@critter.freebsd.dk> <CADGWnjXv6YZQ83PjHuwP-rGyj6-j7=s6xiiMd8MMFP6vLo_buw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Content-Type: text/plain; charset=ISO-8859-1 -------- In message <CADGWnjXv6YZQ83PjHuwP-rGyj6-j7=s6xiiMd8MMFP6vLo_buw@mail.gmail.com> , "C. P. Ghost" writes: >On Sun, Feb 10, 2013 at 2:28 PM, Poul-Henning Kamp <phk@phk.freebsd.dk> wrote: >I was thinking of physical fdc(4). Is there a published interface >to access the hardware, i.e. to tunnel the commands and return >values to and from the device? Something like pass(4) but for >floppies? That way, fdc could be moved to user space and more >easily debugged. Look at /dev/io. But seriously: All our old releases are available on the net, 4.11 and 6.2 were both great releases and they have wonderful floppy support. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?80600.1360508028>