From: Martin Dalecki <dalecki@evision-ventures.com>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Oleg Drokin <green@namesys.com>,
"Gryaznova E." <grev@namesys.botik.ru>,
martin@dalecki.de, Linux Kernel <linux-kernel@vger.kernel.org>,
Reiserfs developers mail-list <Reiserfs-Dev@namesys.com>
Subject: Re: [reiserfs-dev] Re: IDE problem: linux-2.5.17
Date: Fri, 24 May 2002 15:40:32 +0200 [thread overview]
Message-ID: <3CEE42D0.8090004@evision-ventures.com> (raw)
In-Reply-To: <3CECF59B.D471F505@namesys.botik.ru> <3CECFC5B.3030701@evision-ventures.com> <20020523193959.A2613@namesys.com> <3CED004A.6000109@evision-ventures.com> <20020524005057.F27005@ucw.cz> <3CEE1DFE.4080500@evision-ventures.com> <20020524151536.C636@ucw.cz> <3CEE2EE2.1040407@evision-ventures.com> <20020524152054.F636@ucw.cz>
Użytkownik Vojtech Pavlik napisał:
>>Hey what I'm talking about is the "physics" of the hardware.
>>But I would rather expect sane hardware to deal with it transparently
>>to the programmer of the setup registers.
>
>
> Well, when I hear "timer" I think "engineering", not "physics". And a
> timer would have to be visible somewhere. I really don't think the
> controller can tell how many drives it sees unless it measures the
> termination resistance or somesuch.
Jak się zwał tak się zwał, byle by się dobrze miał :-).
Anyway measuring the termination resistance is rather trivial
from the electrical point of view...
next prev parent reply other threads:[~2002-05-24 14:44 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-23 13:58 IDE problem: linux-2.5.17 Gryaznova E.
2002-05-23 14:17 ` Martin Dalecki
2002-05-23 17:48 ` Gryaznova E.
2002-05-23 18:03 ` Tomas Szepe
2002-05-23 18:44 ` Andre Hedrick
2002-05-23 17:49 ` Martin Dalecki
2002-05-23 19:11 ` Andre Hedrick
2002-05-23 19:13 ` Andre Hedrick
2002-05-24 15:05 ` Alan Cox
2002-05-23 22:40 ` Vojtech Pavlik
2002-05-23 18:07 ` Martin Dalecki
2002-05-23 22:42 ` Vojtech Pavlik
2002-05-23 22:37 ` Vojtech Pavlik
2002-05-23 14:27 ` Martin Dalecki
2002-05-23 15:39 ` [reiserfs-dev] " Oleg Drokin
2002-05-23 14:44 ` Martin Dalecki
2002-05-23 16:00 ` Oleg Drokin
2002-05-23 22:52 ` Vojtech Pavlik
2002-05-23 21:47 ` Lionel Bouton
2002-05-23 22:55 ` Vojtech Pavlik
2002-05-24 0:23 ` Lionel Bouton
2002-05-24 1:04 ` Andre Hedrick
2002-05-24 5:56 ` Vojtech Pavlik
2002-05-24 8:53 ` Lionel Bouton
2002-05-24 4:53 ` Oleg Drokin
2002-05-23 22:50 ` Vojtech Pavlik
2002-05-24 11:03 ` Martin Dalecki
2002-05-24 13:15 ` Vojtech Pavlik
2002-05-24 12:15 ` Martin Dalecki
2002-05-24 13:20 ` Vojtech Pavlik
2002-05-24 13:40 ` Martin Dalecki [this message]
2002-05-24 14:54 ` Vojtech Pavlik
2002-05-23 15:52 ` Tomas Szepe
2002-05-23 16:02 ` Oleg Drokin
2002-05-23 22:45 ` 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=3CEE42D0.8090004@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=Reiserfs-Dev@namesys.com \
--cc=green@namesys.com \
--cc=grev@namesys.botik.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@dalecki.de \
--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