public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Adam Wozniak <adam.wozniak@comdev.cc>
To: acurtis@onz.com
Cc: "Jörn Engel" <joern@wohnheim.fh-wedel.de>, linux-mtd@lists.infradead.org
Subject: Re: patch for 64 bit wide flash
Date: Thu, 14 Feb 2002 08:16:20 -0800	[thread overview]
Message-ID: <3C6BE2D4.2B771561@comdev.cc> (raw)
In-Reply-To: NCBBIINEHIPFGJPLBEIFEEEFDEAA.acurtis@onz.com

in my physmap.c (I should probably check this in):

__u64 physmap_read64(struct map_info *map, unsigned long ofs)
{
#ifndef __raw_readll
#error Your architecture needs a __raw_readll in asm/io.h
#endif
        return __raw_readll(map->map_priv_1 + ofs);
}

void physmap_write64(struct map_info *map, __u64 d, unsigned long adr)
{
#ifndef __raw_writell
#error Your architecture needs a __raw_writell in asm/io.h
#endif
        __raw_writell(d, map->map_priv_1 + adr);
        mb();
}

from my include/asm/io.h (this will vary from architecture to
architecture)

#define __raw_readll(addr)      (*(volatile unsigned long long *)(addr)) 
#define __raw_writell(v, addr)  (*(volatile unsigned long long *)(addr)
= (v))

(right next to __raw_writel and all those guys)

Allen Curtis wrote:
> 
> I have another version of 64-bit bus support which does not change any of
> the variable types and only changes one function prototype. It probably is
> not as fast as this 64-bit version, assuming that it is really doing 64-bit
> bus accesses, but it is a very low impact solution.

Whether or not you really do 64 bit bus accesses is going to be compiler
dependant.  If it does, then everything is good.  If it doesn't, it most
likely won't be any worse than anything you come up with by hand.  IMHO
it would be a shame to break this for people who have tools which really
do 64 bit accesses on architectures that can benefit from it.

--Adam
-- 
Adam Wozniak (KG6GZR)   COM DEV Wireless - Digital and Software Systems
awozniak@comdev.cc      3450 Broad St. 107, San Luis Obispo, CA 93401
                        http://www.comdev.cc
                        Voice: (805) 544-1089       Fax: (805) 544-2055

  reply	other threads:[~2002-02-14 16:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-18 23:27 patch for 64 bit wide flash Adam Wozniak
2001-12-21  9:14 ` David Woodhouse
2001-12-21 16:30   ` Adam Wozniak
2001-12-27 23:31   ` Adam Wozniak
2002-02-14 12:32 ` Jörn Engel
2002-02-14 12:38   ` David Woodhouse
2002-02-14 12:58     ` Jörn Engel
2002-02-14 14:16   ` Allen Curtis
2002-02-14 16:16     ` Adam Wozniak [this message]
2002-02-14 16:48       ` Jörn Engel
  -- strict thread matches above, loose matches on Subject: below --
2001-12-29  0:47 Allen Curtis
2001-12-31 16:01 ` adam.wozniak

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=3C6BE2D4.2B771561@comdev.cc \
    --to=adam.wozniak@comdev.cc \
    --cc=acurtis@onz.com \
    --cc=joern@wohnheim.fh-wedel.de \
    --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