All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Martin Dalecki <dalecki@evision-ventures.com>
Cc: Vojtech Pavlik <vojtech@suse.cz>, 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:15:36 +0200	[thread overview]
Message-ID: <20020524151536.C636@ucw.cz> (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>

On Fri, May 24, 2002 at 01:03:26PM +0200, Martin Dalecki wrote:
> Użytkownik Vojtech Pavlik napisał:
> 
> > 
> >>Hmm thinking again about it... It occurrs to me
> >>that actually there should be a mechanism which tells the
> >>host chip drivers whatever there are only just one or
> >>two drivers connected. I will have to look in to it.
> > 
> > 
> > There is no such mechanism (except for probing the drives). IDE has
> > quite nonsensical "split" termination - the termination resistors are
> > always present even on the middle device. This is to "simplify" things
> > ...
> > 
> 
> Yes there is the host chip timer setting is basically
> changing the termination properties on the hsot chips part
> of the connection. This is the reason I was thinking
> that making the driver for it know how many drivers
> are attached to it could make some sense.

Hmm, interesting. Is it on all chips or just some? I don't know about
anything like that on Intel, VIA, nVidia, AMD, SiS and Artop controllers ...

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2002-05-24 13:15 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 [this message]
2002-05-24 12:15             ` Martin Dalecki
2002-05-24 13:20               ` Vojtech Pavlik
2002-05-24 13:40                 ` Martin Dalecki
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=20020524151536.C636@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=Reiserfs-Dev@namesys.com \
    --cc=dalecki@evision-ventures.com \
    --cc=green@namesys.com \
    --cc=grev@namesys.botik.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@dalecki.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.