From: Russell King <rmk@arm.linux.org.uk>
To: Stevie O <stevie@qrpff.net>
Cc: "David S. Miller" <davem@redhat.com>,
Mika.Liljeberg@welho.com, kuznet@ms2.inr.ac.ru,
Mika.Liljeberg@nokia.com, linux-kernel@vger.kernel.org,
sarolaht@cs.helsinki.fi
Subject: Re: TCP LAST-ACK state broken in 2.4.17-pre2 [NEW DATA]
Date: Thu, 20 Dec 2001 09:01:39 +0000 [thread overview]
Message-ID: <20011220090139.B29925@flint.arm.linux.org.uk> (raw)
In-Reply-To: <3C1FA558.E889A00D@welho.com> <200112181837.VAA10394@ms2.inr.ac.ru> <3C1FA558.E889A00D@welho.com> <20011218.122813.63057831.davem@redhat.com> <5.1.0.14.2.20011220022218.01dc2258@whisper.qrpff.net>
In-Reply-To: <5.1.0.14.2.20011220022218.01dc2258@whisper.qrpff.net>; from stevie@qrpff.net on Thu, Dec 20, 2001 at 02:31:44AM -0500
On Thu, Dec 20, 2001 at 02:31:44AM -0500, Stevie O wrote:
> I don't know what arch you're using, but I work with ARM7TDMI, which has a
> behavior I believe can be found documented in some obscure .pdf from arm.com:
Sorry, it's not an obscure PDF. It's documented in the Architecture
Reference Manual, which is the main reference for the behaviour of any
ARM processor. If you don't have that, then you're missing *vital*
information.
> At least, that's how ARM's docs seem to describe it. I work with this cpu
> embedded in a microcontroller (AT91M40800), and these values result:
>
> *(int*)0x00 == 0x33221100
> *(int*)0x01 == 0x33221100
> *(int*)0x02 == 0x33221100
> *(int*)0x03 == 0x33221100
> *(int*)0x04 == 0x77665544
Looks like some random manufacturer decided to do something different.
Nothing out of the ordinary there. 8(
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-12-20 9:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-18 9:33 TCP LAST-ACK state broken in 2.4.17-pre2 [NEW DATA] Mika.Liljeberg
2001-12-18 18:37 ` kuznet
2001-12-18 20:21 ` Mika Liljeberg
2001-12-18 20:28 ` David S. Miller
2001-12-18 20:29 ` ARM: " kuznet
2001-12-18 20:52 ` Mika Liljeberg
2001-12-18 21:08 ` David S. Miller
2001-12-18 21:03 ` Russell King
2001-12-18 21:11 ` David S. Miller
2001-12-18 21:14 ` Russell King
2001-12-18 21:15 ` David S. Miller
2001-12-18 21:27 ` Mika Liljeberg
2001-12-18 21:24 ` Rik van Riel
2001-12-18 21:28 ` Russell King
2001-12-18 21:33 ` David S. Miller
2001-12-20 7:31 ` Stevie O
2001-12-20 7:40 ` David S. Miller
2001-12-20 7:51 ` Stevie O
2001-12-20 8:58 ` Russell King
2001-12-20 9:01 ` Russell King [this message]
2001-12-20 10:22 ` David Weinehall
2002-01-02 19:52 ` Mike Touloumtzis
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=20011220090139.B29925@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=Mika.Liljeberg@nokia.com \
--cc=Mika.Liljeberg@welho.com \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=sarolaht@cs.helsinki.fi \
--cc=stevie@qrpff.net \
/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