From: Marcin Dalecki <dalecki@evision.ag>
To: unlisted-recipients:; (no To-header on input)
Cc: Petr Vandrovec <VANDROVE@vc.cvut.cz>,
Nick Orlov <nick.orlov@mail.ru>,
B.Zolnierkiewicz@elka.pw.edu.pl,
Marcelo Tosatti <marcelo@conectiva.com.br>,
linux-kernel@vger.kernel.org, davidsen@tmr.com
Subject: Re: [PATCH] pdc20265 problem.
Date: Fri, 09 Aug 2002 08:47:11 +0200 [thread overview]
Message-ID: <3D53656F.9000004@evision.ag> (raw)
In-Reply-To: Pine.LNX.4.10.10208081128430.25573-100000@master.linux-ide.org
Uz.ytkownik Andre Hedrick napisa?:
> Clearly the difference between what is silkscreened and the usage intent
> is beyond the obvious :-/ Since I have had or still have first hand
> experience in the observed behaior under Linux and MicroSoft, you are
> going by what is read. Book knowledges gets you books not reality.
> try a few w/ all of them bootable and see what happens. So until Linux
> gets a clue about EDDS 2.0 and or 3.0 it has not a chance of getting the
> correct hd0/hd1 from the INT13/19 services. Obviously experience and
> first hand knowledge of reality is worthless in Linux. I am out of this
> thread.
BTW. EDDS is up to level 3.3
next prev parent reply other threads:[~2002-08-09 6:49 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 18:22 [PATCH] pdc20265 problem Petr Vandrovec
2002-08-08 18:35 ` Andre Hedrick
2002-08-09 6:47 ` Marcin Dalecki [this message]
2002-08-12 1:24 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2002-08-08 16:48 Petr Vandrovec
2002-08-08 17:30 ` Andre Hedrick
2002-08-08 12:45 Petr Vandrovec
2002-08-08 13:02 ` Andre Hedrick
2002-08-07 18:39 Adam J. Richter
2002-08-07 19:33 ` Thunder from the hill
2002-08-07 21:11 ` Alan Cox
2002-08-07 20:02 ` Thunder from the hill
2002-08-07 23:40 ` Alan Cox
2002-08-07 10:20 Petr Vandrovec
2002-08-07 23:04 ` Bill Davidsen
2002-08-07 7:54 Adam J. Richter
2002-08-07 11:41 ` Alan Cox
2002-08-07 23:08 ` Bill Davidsen
2002-08-08 10:49 ` Zwane Mwaikambo
2002-08-07 16:32 ` Thunder from the hill
2002-08-06 10:28 Petr Vandrovec
2002-08-02 19:05 Bartlomiej Zolnierkiewicz
2002-08-02 23:05 ` Marcelo Tosatti
2002-08-03 0:55 ` Bartlomiej Zolnierkiewicz
2002-08-03 0:08 ` Marcelo Tosatti
2002-08-03 1:22 ` Nick Orlov
2002-08-03 13:41 ` Alan Cox
2002-08-06 3:48 ` Bill Davidsen
2002-08-06 4:33 ` Nick Orlov
2002-08-07 3:09 ` Bill Davidsen
2002-08-07 3:56 ` Nick Orlov
2002-08-07 18:30 ` Andre Hedrick
2002-08-07 20:27 ` Tomas Szepe
2002-08-07 22:46 ` Bill Davidsen
2002-08-08 10:50 ` Andre Hedrick
2002-08-08 17:42 ` Nick Orlov
2002-08-08 18:02 ` Andre Hedrick
2002-08-09 6:44 ` Marcin Dalecki
2002-08-12 1:37 ` Andre Hedrick
2002-08-09 17:16 ` Bill Davidsen
2002-08-01 6:38 Linux v2.4.19-rc5 Marcelo Tosatti
2002-08-02 1:47 ` [PATCH] pdc20265 problem Nick Orlov
2002-08-02 2:29 ` Nick Orlov
2002-08-02 12:27 ` Alan Cox
2002-08-02 12:52 ` Nick Orlov
2002-08-02 14:00 ` Bartlomiej Zolnierkiewicz
2002-08-02 14:45 ` Nick Orlov
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=3D53656F.9000004@evision.ag \
--to=dalecki@evision.ag \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=VANDROVE@vc.cvut.cz \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=martin@dalecki.de \
--cc=nick.orlov@mail.ru \
/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