From: Vojtech Pavlik <vojtech@suse.cz>
To: Mike Galbraith <mikeg@wen-online.de>
Cc: andre@linux-ide.org, linux-kernel@vger.kernel.org
Subject: Re: [preview] Latest AMD & VIA IDE drivers with UDMA100 support
Date: Sun, 21 Jan 2001 17:32:51 +0100 [thread overview]
Message-ID: <20010121173251.B1073@suse.cz> (raw)
In-Reply-To: <20010121104606.A398@suse.cz> <Pine.Linu.4.10.10101211237230.2017-100000@mikeg.weiden.de>
In-Reply-To: <Pine.Linu.4.10.10101211237230.2017-100000@mikeg.weiden.de>; from mikeg@wen-online.de on Sun, Jan 21, 2001 at 01:42:41PM +0100
On Sun, Jan 21, 2001 at 01:42:41PM +0100, Mike Galbraith wrote:
> On Sun, 21 Jan 2001, Vojtech Pavlik wrote:
>
> > On Sat, Jan 20, 2001 at 02:57:07PM -0800, Andre Hedrick wrote:
> >
> > > chipset ---\
> > > |
> > > \---------IDC-header
> > >
> > > chipset ---+
> > > |
> > > +----------IDC-header
> > >
> > > These are nearly the same but the corners cause bounce and iCRC's
>
> I don't see how anyone can influence risetime falltime or impedance
> matching [1] issues via software timing changes.
>
> (the top drawing is what you see on a poorly designed board.. long
> rise/fall times often cause worse problems than [slight] ringing)
>
> > Well, there are other ways the motherboard maker can screw up the
> > traces, and often this happens:
> >
> > chipset --------\
> > |
> > chipset ------\ |
> > | \------ header
> > \-------- header
> >
>
> Can you compensate for these things (to any degree?) in software?
Not really. Slowing the data rate down is in my opinion the only way to
compensate for this. Btw, the chipset only controls the write data rate
with UDMA. The read rate is controlled by the drive.
> 1. Only a software guy would call it 'bounce'.. sounds funny ;-)
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-21 16:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-20 17:14 [preview] Latest AMD & VIA IDE drivers with UDMA100 support Alan Chandler
[not found] ` <Pine.LNX.4.10.11101200938180.2302-100000@master.linux-ide.org>
2001-01-20 18:45 ` Alan Chandler
2001-01-20 20:56 ` Vojtech Pavlik
2001-01-20 22:57 ` Andre Hedrick
2001-01-20 23:55 ` Alan Chandler
[not found] ` <Pine.LNX.4.10.10101202015510.1776-100000@coffee.psychology.mcmaster.ca>
2001-01-21 10:51 ` Alan Chandler
2001-01-21 11:44 ` Vojtech Pavlik
2001-01-21 9:46 ` Vojtech Pavlik
2001-01-21 13:04 ` Jan Niehusmann
[not found] ` <Pine.Linu.4.10.10101211237230.2017-100000@mikeg.weiden.de>
2001-01-21 16:32 ` Vojtech Pavlik [this message]
2001-01-21 20:49 ` Andre Hedrick
2001-01-22 0:12 ` Dan Hopper
2001-01-22 6:06 ` Mike Galbraith
2001-01-25 21:54 ` David D.W. Downey
2001-01-25 21:56 ` Vojtech Pavlik
2001-01-25 22:00 ` Andre Hedrick
2001-01-26 0:26 ` David D.W. Downey
2001-01-24 18:04 ` Andre Hedrick
2001-01-24 19:25 ` Vojtech Pavlik
2001-01-24 21:58 ` Andre Hedrick
2001-01-25 12:20 ` Vojtech Pavlik
-- strict thread matches above, loose matches on Subject: below --
2001-01-19 15:56 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=20010121173251.B1073@suse.cz \
--to=vojtech@suse.cz \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikeg@wen-online.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox