public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Timur Tabi <timur@freescale.com>
Cc: Anton Altaparmakov <aia21@cam.ac.uk>,
	Jan Engelhardt <jengelh@computergmbh.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: __LITTLE_ENDIAN vs. __LITTLE_ENDIAN_BITFIELD
Date: Fri, 05 Oct 2007 23:29:04 +0200	[thread overview]
Message-ID: <jer6k9mesf.fsf@sykes.suse.de> (raw)
In-Reply-To: <4706A842.9030507@freescale.com> (Timur Tabi's message of "Fri\, 05 Oct 2007 16\:10\:26 -0500")

Timur Tabi <timur@freescale.com> writes:

> The CPU shift operation, yes.  I'm talking about shift operations on
> external memory-mapped devices.

That is a property of how the device is wired to the bus.  The cpu will
always put a value of 128 on the bus such that D7 = 1 and D0-D6 = 0.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2007-10-05 21:29 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-05 18:27 __LITTLE_ENDIAN vs. __LITTLE_ENDIAN_BITFIELD Timur Tabi
2007-10-05 18:35 ` Jan Engelhardt
2007-10-05 19:35   ` Timur Tabi
2007-10-05 19:43     ` Jan Engelhardt
2007-10-05 19:47       ` Timur Tabi
2007-10-05 20:04         ` Andreas Schwab
2007-10-05 20:07           ` Timur Tabi
2007-10-05 20:34             ` linux-os (Dick Johnson)
2007-10-05 20:37               ` Timur Tabi
2007-10-05 23:27                 ` Benjamin Herrenschmidt
2007-10-05 21:17             ` Andreas Schwab
2007-10-05 21:06     ` Anton Altaparmakov
2007-10-05 21:10       ` Timur Tabi
2007-10-05 21:29         ` Andreas Schwab [this message]
2007-10-05 21:32           ` Timur Tabi
2007-10-05 23:17             ` Andreas Schwab
2007-10-09 17:46         ` Lennart Sorensen
2007-10-09 17:56           ` Timur Tabi
2007-10-09 18:34             ` Lennart Sorensen
2007-10-09 18:50             ` Krzysztof Halasa
2007-10-09 18:57               ` Timur Tabi
2007-10-09 19:37                 ` Krzysztof Halasa
2007-10-09 19:44                   ` Timur Tabi
2007-10-09 22:11                     ` Krzysztof Halasa
2007-10-09 19:11               ` Jeremy Fitzhardinge
2007-10-09 19:39                 ` Krzysztof Halasa
2007-10-09 21:40                   ` Jeremy Fitzhardinge
2007-10-09 22:34                     ` Krzysztof Halasa
2007-10-10 12:05                       ` linux-os (Dick Johnson)

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=jer6k9mesf.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=aia21@cam.ac.uk \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=timur@freescale.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