public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Allen Curtis" <acurtis@onz.com>
To: "David Woodhouse" <dwmw2@infradead.org>
Cc: <linux-mtd@lists.infradead.org>
Subject: RE: 64-bit support..what happened?
Date: Wed, 4 Sep 2002 07:41:13 -0700	[thread overview]
Message-ID: <NCBBIINEHIPFGJPLBEIFOEKHDLAA.acurtis@onz.com> (raw)
In-Reply-To: <31730.1031149412@redhat.com>

> > 2. drivers/mtd/maps/physmap.c - attempts to reference __raw_readll()
> > and __raw_writell() when in 64-bit mode. These functions/macros do not
> > exist. They would appear in include/asm/io.h. Nothing exists in the
> > MTD tree to patch this file or otherwise provide these functions.
>
> Correct. Again, this is platform-specific and you need to provide
> it. Some
> people have to play tricks with transferring all 64 bits into a
> FP register
> and storing form there, etc. It's probably best to take the stuff in
> physmap.c as merely an example, and provide your own map driver.

As you mentioned, although my architecture has a 64-bit bus, the only way to
perform a 64-bit bus access is through the floating point processor. Do you
see any reason why I couldn't just perform 2 32-bit operations?

I will take physmap.c as an example and make our own version. However good
sample code would include the proper headers if they reference conditional
defines. (slight jab...sorry) I believe that there are 3 files under map
that include the conditional compile and none of them include the proper
header file. Perhaps this just indicates that the conditional should be
moved to another file or change to use the autoconfig defines?

  reply	other threads:[~2002-09-04 14:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-04 14:14 64-bit support..what happened? Allen Curtis
2002-09-04 14:23 ` David Woodhouse
2002-09-04 14:41   ` Allen Curtis [this message]
2002-09-04 14:51     ` David Woodhouse
2002-09-04 15:06       ` Allen Curtis
2002-09-04 15:09         ` David Woodhouse

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=NCBBIINEHIPFGJPLBEIFOEKHDLAA.acurtis@onz.com \
    --to=acurtis@onz.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.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