From: David Woodhouse <dwmw2@infradead.org>
To: acurtis@onz.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: 64-bit support..what happened?
Date: Wed, 04 Sep 2002 15:23:32 +0100 [thread overview]
Message-ID: <31730.1031149412@redhat.com> (raw)
In-Reply-To: <NCBBIINEHIPFGJPLBEIFEEKGDLAA.acurtis@onz.com>
acurtis@onz.com said:
> 1. The conditional CONFIG_CFI_64 is defined within cfi.h. However not
> all the source modules that use this conditional include the proper
> header file. (all the source modules under drivers/mtd/maps)
You presumably only need to include it for the map drivers on those
platforms which can actually support 64-bit operation. So that's not
necessarily a problem.
> 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.
--
dwmw2
next prev parent reply other threads:[~2002-09-04 14:23 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 [this message]
2002-09-04 14:41 ` Allen Curtis
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=31730.1031149412@redhat.com \
--to=dwmw2@infradead.org \
--cc=acurtis@onz.com \
--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