Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 30 Sep 1999 01:46:41 +0200 (CEST)
From:      Oliver Fromme <olli@dorifer.heim3.tu-clausthal.de>
To:        freebsd-hackers@FreeBSD.ORG
Subject:   Re: 2.88Mb floppies
Message-ID:  <199909292346.BAA03499@dorifer.heim3.tu-clausthal.de>

next in thread | raw e-mail | index | archive | help
Wilko Bulte wrote in list.freebsd-hackers:
 > As Doug Rabson wrote ...
 > > On Mon, 27 Sep 1999, Wilko Bulte wrote:
 > > > static struct fd_type fd_types[NUMTYPES] =
 > > > {
 > > > { 21,2,0xFF,0x04,82,3444,1,FDC_500KBPS,2,0x0C,2 }, /* 1.72M in HD 3.5in */
 > > > { 18,2,0xFF,0x1B,82,2952,1,FDC_500KBPS,2,0x6C,1 }, /* 1.48M in HD 3.5in */
 > > > { 18,2,0xFF,0x1B,80,2880,1,FDC_500KBPS,2,0x6C,1 }, /* 1.44M in HD 3.5in */
 > > 
 > > I have no idea whether that driver can cope with 2.88mb floppies to be
 > > honest. There is only one way to find out...
 > 
 > Right. I'll give it a try asap. Somebody sent me a sample entry to
 > add to fd_type. But I want to do a bit of study on the fd source to see
 > if I can understand what all the fields mean.

I once programmed low-level FDC stuff under DOS, so I'm a bit
familiar with this...  The difference between 1.44 and 2.88 Mb
floppies is that the latter use 36 sectors per track and twice
the data rate (1 MBit/s).  So the entry should look like this:

{36, 2, 0xff, 0x1b, 80, 5760, 1, FDC_125KBPS, 2, 0x6c, 1}

Actually, there should be a  #define FDC_1MBPS FDC_125KBPS

Regards
   Oliver

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de)

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
                                         (Terry Pratchett)


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909292346.BAA03499>