From: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
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 17:03:05 -0400 [thread overview]
Message-ID: <20060825210305.GL13639@csclub.uwaterloo.ca> (raw)
In-Reply-To: <1156540817.3007.270.camel@localhost.localdomain>
On Fri, Aug 25, 2006 at 10:20:17PM +0100, Alan Cox wrote:
> That should be staying in order unless the device memory is mislabelled
> and prefetchable etc.
Hmm, no according to lspci the memory is labeled non-prefetachble, and
the pci bridge agrees with that setting too.
> What happens if you swap the memcpy_toio with while() writeb() ?
I tried changing it to a for loop that calles memcpy_toio with one byte
at a time, and it works fine that way (although probably less
efficient). I expect the writeb one at a time will work too.
> 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.
Yeah no kidding.
> Is the buffer 32bit aligned ?
I honestly don't know. I am just trying to figure out why the jsm
driver isn't working on this system while it works on other types of
hardware, and so far it seems to come down to the __memcpy assembly not
being happy on the SC1200 doing more than one byte at a time. it is
very consistently making the same mistake all the time.
--
Len Sorensen
next prev parent reply other threads:[~2006-08-25 21:03 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
2006-08-25 21:03 ` Lennart Sorensen [this message]
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=20060825210305.GL13639@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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®