public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Phillips <phillim2@home.com>
To: Kent E Yoder <yoder1@us.ibm.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Jeff Garzik <jgarzik@mandrakesoft.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IBM Lanstreamer bugfixes
Date: Wed, 30 Jan 2002 15:04:28 -0500	[thread overview]
Message-ID: <20020130200428.GA7318@home.com> (raw)
In-Reply-To: <OF0323731B.AAE52C6B-ON85256B51.005748CD@raleigh.ibm.com>
In-Reply-To: <OF0323731B.AAE52C6B-ON85256B51.005748CD@raleigh.ibm.com>

On Wed, Jan 30, 2002 at 01:27:29PM -0600 or sometime in the same epoch, Kent E Yoder scribbled:
>   I think the delays in the driver *were* just working around PCI posting 
> effects.  I tested by removing all the delays and instead putting 
> something like:
>         writew(val, addr);
>         (void) read(addr);

Yep, I has a similar problem when developing olympic, I would write
twice to the same location in very quick succession. This was using
one of the built in locations that the chipset would binary OR to the
current value. So theoretically the second write should have been
OR'ed with the first write, but the second write was being done before
the first write was committed across the pci bus, resulting in only
the second value being stored. 

In the end, I rewrote it to combine into a single write. 

-- 
Mike Phillips
Linux Token Ring Project
http://www.linuxtr.net
mailto: mikep@linuxtr.net


  parent reply	other threads:[~2002-01-30 21:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-30 19:27 [PATCH] IBM Lanstreamer bugfixes Kent E Yoder
2002-01-30 19:48 ` Jeff Garzik
2002-01-30 19:58 ` David Weinehall
2002-01-30 20:43   ` Alan Cox
2002-01-30 20:04 ` Mike Phillips [this message]
2002-01-30 20:47 ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2002-02-01 20:53 Kent E Yoder
2002-02-01 23:38 ` Alan Cox
2002-02-01 23:40 ` Alan Cox
2002-01-21 16:44 Kent E Yoder
2002-01-21 17:46 ` Mike Phillips
2002-01-18 23:02 Kent E Yoder
2002-01-18 23:19 ` Alan Cox
2002-01-18 23:52   ` Gérard Roudier
2002-01-19 17:14 ` Mike Phillips
2002-01-18 22:39 Kent E Yoder
2002-01-18 22:32 Kent E Yoder
2002-01-18 22:47 ` Alan Cox
2002-01-18 20:52 Kent E Yoder
2002-01-18 21:35 ` Alan Cox
2002-01-17 15:29 Kent E Yoder
2002-01-16 19:42 Kent E Yoder
2002-01-17 10:57 ` Jeff Garzik

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=20020130200428.GA7318@home.com \
    --to=phillim2@home.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yoder1@us.ibm.com \
    /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