*BSD News Article 19376


Return to BSD News archive

Xref: sserve comp.os.os2.programmer:13286 comp.os.linux:52522 comp.os.mach:3154 comp.os.minix:22540 comp.periphs:4084 comp.unix.bsd:12386 comp.unix.pc-clone.32bit:4022 comp.os.386bsd.development:1026
Newsgroups: comp.os.os2.programmer,comp.os.linux,comp.os.mach,comp.os.minix,comp.periphs,comp.unix.bsd,comp.unix.pc-clone.32bit,comp.os.386bsd.development
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!darwin.sura.net!news-feed-2.peachnet.edu!news-feed-1.peachnet.edu!umn.edu!csus.edu!netcom.com!adler
From: adler@netcom.com (Bruce Adler)
Subject: Re: More on the DMA timing problem
Message-ID: <adlerCBKtnF.DGH@netcom.com>
Keywords: DMA FDC timing problem QIC-40/80 
Organization: Netcom Online Communications Services (408-241-9760 login: guest)
References: <jmonroyCBKrE9.76n@netcom.com>
Date: Wed, 11 Aug 1993 03:57:15 GMT
Lines: 12

Enough already! Just post the code somewhere and someone with some
real programming experience will figure out what's wrong with your
code. I find it very hard to believe that you've discovered some
sort of previously unknown hardware flaw that causes your driver
to fail on several different motherboard, controller and drive
combinations.  Your prior so-called newsletters have already
convinced me (and probably many others) that you probably lack the
experience, ability, and knowledge to design and implement even the
most simple Unix device driver.

If you insist on keeping your precious code to yourself then stop
cross-posting to so many groups.