From: Russell King <rmk@arm.linux.org.uk>
To: Andre Hedrick <andre@linux-ide.org>
Cc: "Adam J. Richter" <adam@yggdrasil.com>,
jgarzik@mandrakesoft.com, ebiederm@xmission.com,
linux-kernel@vger.kernel.org
Subject: Re: IDE-flash device and hard disk on same controller
Date: Fri, 23 Aug 2002 12:10:59 +0100 [thread overview]
Message-ID: <20020823121059.D20963@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.10.10208230022060.14761-100000@master.linux-ide.org>; from andre@linux-ide.org on Fri, Aug 23, 2002 at 12:45:03AM -0700
On Fri, Aug 23, 2002 at 12:45:03AM -0700, Andre Hedrick wrote:
> This is where JG's hard work and my time with him explaining it will help
> most. Also case where RMK's ARM toys do fun things and the assumption by
> the driver that POST is valid is DEAD WRONG. I will repeat the assumption
> of my code about POST is DEAD WRONG! POST like events happen at different
> times for various archs.
Yet more FUD. Andre - go away and come back once you've calmed down.
Maybe its because you don't actually understand my IDE hardware. I
dunno. But you are "DEAD WRONG" about the crap you've written above.
Completely.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-08-23 11:06 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 6:54 IDE-flash device and hard disk on same controller Adam J. Richter
2002-08-23 7:45 ` Andre Hedrick
2002-08-23 11:10 ` Russell King [this message]
2002-08-23 17:08 ` Andre Hedrick
2002-08-23 17:42 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2002-08-23 10:48 Adam J. Richter
2002-08-23 10:14 Adam J. Richter
2002-08-23 8:31 Adam J. Richter
2002-08-23 8:59 ` Andre Hedrick
2002-08-23 9:54 ` Andries Brouwer
2002-08-21 13:22 Warner, Bill (IndSys, GEFanuc, VMIC)
2002-08-20 19:52 Heater, Daniel (IndSys, GEFanuc, VMIC)
2002-08-20 21:57 ` Andre Hedrick
2002-08-20 22:00 ` Jeff Garzik
2002-08-20 22:28 ` Jeff Garzik
2002-08-21 6:36 ` Geert Uytterhoeven
2002-08-21 6:55 ` Andre Hedrick
2002-08-21 7:16 ` Geert Uytterhoeven
2002-08-22 5:34 ` Eric W. Biederman
2002-08-22 23:12 ` Jeff Garzik
2002-08-23 0:50 ` Eric W. Biederman
2002-08-23 1:26 ` Jeff Garzik
2002-08-23 11:03 ` Russell King
2002-08-23 11:41 ` Benjamin Herrenschmidt
2002-08-23 10:12 ` Alan Cox
2002-08-23 13:09 ` Eric W. Biederman
2002-08-23 3:14 ` Andre Hedrick
2002-08-23 11:44 ` Benjamin Herrenschmidt
2002-08-24 2:02 ` Jeff Garzik
2002-08-24 0:19 ` Benjamin Herrenschmidt
2002-08-24 8:41 ` Russell King
2002-08-24 20:28 ` Andre Hedrick
2002-08-23 3:19 ` Andre Hedrick
2002-08-23 7:14 ` Helge Hafting
2002-08-23 7:49 ` Andre Hedrick
2002-08-23 10:50 ` Geert Uytterhoeven
2002-08-23 11:08 ` Russell King
2002-08-23 11:07 ` Russell King
2002-08-23 11:36 ` Benjamin Herrenschmidt
2002-08-22 13:41 ` bill davidsen
2002-08-19 18:31 Heater, Daniel (IndSys, GEFanuc, VMIC)
2002-08-19 19:21 ` Alan Cox
2002-08-20 8:44 ` Padraig Brady
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=20020823121059.D20963@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=adam@yggdrasil.com \
--cc=andre@linux-ide.org \
--cc=ebiederm@xmission.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
/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