Return to BSD News archive
Xref: sserve comp.os.os2.programmer:13298 comp.os.linux:52726 comp.os.mach:3159 comp.os.minix:22545 comp.periphs:4093 comp.unix.bsd:12396 comp.unix.pc-clone.32bit:4034 comp.os.386bsd.development:1037
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!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!vixen.cso.uiuc.edu!uwm.edu!cs.utexas.edu!uunet!decwrl!decwrl!csus.edu!netcom.com!jmonroy
From: jmonroy@netcom.com (Jesus Monroy Jr)
Subject: Re: More on the DMA timing problem
Message-ID: <jmonroyCBMzF6.3AG@netcom.com>
Followup-To: 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
Organization: NETCOM On-line Communication Services (408 241-9760 guest)
X-Newsreader: TIN [version 1.1 PL8]
References: <jmonroyCBKrE9.76n@netcom.com>
Date: Thu, 12 Aug 1993 07:57:06 GMT
Lines: 67
mail adler@netcom.com
Subject: Re: More on the DMA timing problem
As polite as I can remain, These are my words to you
mister alder.
>> 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
>> Organization: Netcom Online Communications Services (408-241-9760 login: guest)
>> Date: Wed, 11 Aug 1993 03:57:15 GMT
>>
>> Enough already! Just post the code somewhere and someone with some
>> real programming experience will figure out what's wrong with your
>> code.
POINT #1. You don't have my coe.
>> 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.
>>
POINT #2. I don't beleive you have any knowledge that is
useful to me. Namely, if there does exist a
problem with the DMA the mfgr of any devices
associated would most assuredly want to keep this
private. You might consider this if you own your
own business, like me.
>> 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.
>>
My newletter and knowledge only reflex your own ignorance.
This is evidenced by your own comments.
I don't care how long you think you been in this business,
(computers, etc.) this does not entitle you to any special
moronic additudes.
>> If you insist on keeping your precious code to yourself then stop
>> cross-posting to so many groups.
>>
My code is available to the beta groups that are testing
it; Which it is testing now.
The relevant importance of you -and any of the so-called
group you contend to be working in- is most assuredly
the best evidence of pathetic reasoning that abound.
If you think that I have, in the past, made any statements
that do _or_ are not well founded you and your cohorts
are welcome to do me up. Else tonight is the night
in which the most metors will be visible in more than a decade
my suggestion to you is to go outside and see which
land closest to you. My preference for a landing spot,
centered concentricly, is about 20 ft. from you.
Have a nice day.
Write again.
___________________________________________________________________________
Jesus Monroy Jr jmonroy@netcom.com
/386BSD/device-drivers /fd /qic /clock /documentation
___________________________________________________________________________