From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Strange transmit corruption in jsm driver on geode sc1200 system
Date: Fri, 25 Aug 2006 22:20:17 +0100 [thread overview]
Message-ID: <1156540817.3007.270.camel@localhost.localdomain> (raw)
In-Reply-To: <20060825203047.GH13641@csclub.uwaterloo.ca>
Ar Gwe, 2006-08-25 am 16:30 -0400, ysgrifennodd Lennart Sorensen:
> The driver is doing memcpy_toio to tranfer data to the transmit FIFO
> (which is a 64byte memory mapped block of memory on the PCI bus as far
> as I can tell). The data in the transmit queue is in the right order
That should be staying in order unless the device memory is mislabelled
and prefetchable etc.
> being passed to memcpy_toio, but somehow by the time it is in the uart
> and goes out the transmiter, every 4th byte is moved 3 bytes back.
What happens if you swap the memcpy_toio with while() writeb() ?
> I read something about the geodes doing memory write reordering, but
> that it is supposed to magically not screw up PCI writes. I have no
> idea if it is or not though.
They do a lot of stuff but it should not affect the PCI side and I'd
expect it to do other things than byte lane re-ordering.
> Does anyone have any suggestions for something to try?
Is the buffer 32bit aligned ?
next prev parent reply other threads:[~2006-08-25 20:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-25 20:30 Lennart Sorensen
2006-08-25 21:20 ` Alan Cox [this message]
2006-08-25 21:03 ` Lennart Sorensen
2006-08-25 21:24 ` Alexey Dobriyan
2006-08-25 21:57 ` Lennart Sorensen
2006-08-28 17:30 ` Lennart Sorensen
2006-08-28 18:11 ` Lennart Sorensen
2006-08-28 19:09 ` Alan Cox
2006-08-28 19:18 ` Lennart Sorensen
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=1156540817.3007.270.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
/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
all inboxes | Powered by JetHome®