public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Adam Wozniak <adam.wozniak@comdev.cc>
Cc: linux-mtd@lists.infradead.org
Subject: Re: patch for 64 bit wide flash
Date: Fri, 21 Dec 2001 09:14:13 +0000	[thread overview]
Message-ID: <3698.1008926053@redhat.com> (raw)
In-Reply-To: <3C1FD0DD.9A4F2CC8@comdev.cc>

adam.wozniak@comdev.cc said:
> I've got a 64 bit wide flash consisting of eight 8bit wide chips.
> Here's a patch against the 2.4.16 kernel 

I'm a little concerned about the following bit - gcc is fairly crap at 
dealing with 64-bit datatypes. I'd prefer to do that only if it's 
necessary. Can we define a cfi_busword type which is only as big as we need 
- so it's only a __u64 if CONFIG_MTD_CFI_B8 is set?

@@ -337,9 +393,9 @@
  */
 static inline __u32 cfi_send_gen_cmd(u_char cmd, __u32 cmd_addr, __u32 base,
 				struct map_info *map, struct cfi_private *cfi,
-				int type, __u32 *prev_val)
+				int type, __u64 *prev_val)
 {
-	__u32 val;
+	__u64 val;
 	__u32 addr = base + cfi_build_cmd_addr(cmd_addr, CFIDEV_INTERLEAVE, type);
 
 	val = cfi_build_cmd(cmd, map, cfi);

--
dwmw2

  reply	other threads:[~2001-12-21  9:03 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 [this message]
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
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=3698.1008926053@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=adam.wozniak@comdev.cc \
    --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