Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 10 Feb 2013 14:33:00 +0100
From:      "C. P. Ghost" <cpghost@cordula.ws>
To:        Poul-Henning Kamp <phk@phk.freebsd.dk>
Cc:        current@freebsd.org
Subject:   Re: Time to kill fdc ?
Message-ID:  <CADGWnjXv6YZQ83PjHuwP-rGyj6-j7=s6xiiMd8MMFP6vLo_buw@mail.gmail.com>
In-Reply-To: <80406.1360502924@critter.freebsd.dk>
References:  <79955.1360494404@critter.freebsd.dk> <CADGWnjUn66K_Ngwn0Y_wyqX=RTT13h2FC23NeBH3WqNBBwd%2BXw@mail.gmail.com> <80406.1360502924@critter.freebsd.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Feb 10, 2013 at 2:28 PM, Poul-Henning Kamp <phk@phk.freebsd.dk> wrote:
>>> Unless somebody fixes the fdc driver to work in -current, I intend
>>> to dust of my axe and cut it from the tree later this spring.
>>
>>Any chance to get a user-mode fdc(4) replacement then? Maybe
>>in ports?
>
> Uhm, just how would that work ?
>
> If you just want virtual floppies, md(4) is your driver...

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.

> --
> 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.

-cpghost.

-- 
Cordula's Web. http://www.cordula.ws/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADGWnjXv6YZQ83PjHuwP-rGyj6-j7=s6xiiMd8MMFP6vLo_buw>