From: Abraham vd Merwe <abraham@2d3d.co.za>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
Nick Evgeniev <nick@octet.spb.ru>,
linux-kernel@vger.kernel.org
Subject: Re: linux 2.4.19-preX IDE bugs
Date: Fri, 14 Jun 2002 10:59:19 +0200 [thread overview]
Message-ID: <20020614105919.A18127@crystal.2d3d.co.za> (raw)
In-Reply-To: <20020614103746.A324@ucw.cz> <Pine.LNX.4.10.10206140140040.21513-100000@master.linux-ide.org>
[-- Attachment #1: Type: text/plain, Size: 1515 bytes --]
Hi Andre!
> > > http://www.tecchannel.de/hardware/817/index.html
> > >
> > > Read about the JUNK hardware base you are working with.
> > > This is one of the reasons people avoid VIA.
> >
> > Hmm, I don't want to interfere in this nicely-growing flamethrowing, but
> > Andre, you might have noticed, that Nick is saying that it actually
> > *works* on the VIA controller and doesn't on the Promise one. Plus older
> > kernels do work on the Promise controller. That's clearly a software
> > problem.
>
> Well if you have not read, I offered to export the changes to the kernel
> he states works as a way to isolate the driver from other changes.
> We have Promise adding their two cents, also.
>
> How about you rewriting the driver an take my name out of it too.
> Then you can have all the credit be yours.
Maybe I shouldn't stick my nose into this, but Andre, you've really got to
work on that attitude man. Sarcastic responses are only amusing for so
long...
--
Regards
Abraham
The reason they're called wisdom teeth is that the experience makes you wise.
__________________________________________________________
Abraham vd Merwe - 2d3D, Inc.
Device Driver Development, Outsourcing, Embedded Systems
Cell: +27 82 565 4451 Snailmail:
Tel: +27 21 761 7549 Block C, Aintree Park
Fax: +27 21 761 7648 Doncaster Road
Email: abraham@2d3d.co.za Kenilworth, 7700
Http: http://www.2d3d.com South Africa
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-06-14 8:57 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 15:28 Nick Evgeniev
2002-06-04 16:41 ` Alan Cox
2002-06-08 19:52 ` Andre Hedrick
2002-06-11 15:31 ` Nick Evgeniev
2002-06-11 16:52 ` Andre Hedrick
2002-06-13 11:15 ` Nick Evgeniev
2002-06-14 7:01 ` Andre Hedrick
2002-06-14 7:44 ` Nick Evgeniev
2002-06-14 8:20 ` Andre Hedrick
2002-06-14 8:37 ` Vojtech Pavlik
2002-06-14 8:45 ` Andre Hedrick
2002-06-14 8:55 ` Vojtech Pavlik
2002-06-14 8:59 ` Andre Hedrick
2002-06-14 9:15 ` Bartlomiej Zolnierkiewicz
2002-06-14 9:19 ` Bartlomiej Zolnierkiewicz
2002-06-14 8:59 ` Abraham vd Merwe [this message]
2002-06-14 9:08 ` Andre Hedrick
2002-06-14 9:24 ` Abraham vd Merwe
2002-06-14 9:06 ` Nick Evgeniev
2002-06-11 18:53 ` Jason C. Pion
2002-06-11 19:34 ` Tomas Szepe
2002-06-11 19:47 ` Jason C. Pion
2002-06-14 12:34 ` Bill Davidsen
2002-06-14 14:22 ` Jason C. Pion
2002-06-11 22:49 ` Bill Davidsen
2002-06-12 0:19 ` Andre Hedrick
2002-06-12 7:31 ` Alan Cox
2002-06-12 13:57 ` Bill Davidsen
2002-06-12 18:32 ` Andre Hedrick
2002-06-12 20:30 ` Bill Davidsen
2002-06-12 7:36 ` Alan Cox
2002-06-11 18:26 Mikael Pettersson
2002-06-13 20:39 Mikael Pettersson
2002-06-15 17:12 Anssi Saari
2002-06-15 18:51 ` Vojtech Pavlik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020614105919.A18127@crystal.2d3d.co.za \
--to=abraham@2d3d.co.za \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@octet.spb.ru \
--cc=vojtech@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®