public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH 4/6] cfi_flash: Introduce read and write accessors
Date: Tue, 11 Dec 2007 17:25:22 +0100	[thread overview]
Message-ID: <20071211162522.1574024657@gemini.denx.de> (raw)
In-Reply-To: Your message of "Tue, 11 Dec 2007 16:46:44 +0100." <20071211164644.6430849a@dhcp-252-066.norway.atmel.com>

In message <20071211164644.6430849a@dhcp-252-066.norway.atmel.com> you wrote:
> On Tue, 11 Dec 2007 09:35:21 -0600
> Kumar Gala <galak@kernel.crashing.org> wrote:
> 
> > should these not use in/out macros from asm/io.h?
> 
> That would probably be better. It's just that I'm having a hard time
> finding a set of macros that
>   a) is available on all architectures
>   b) don't do any byte swapping or other tricks
> 
> __raw_writeb() and friends would satisfy b) but not a)...

Then we eventually should implement these for the missing
architetures.

Kumar is right. We definitely must use the "real" accessor functions.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
365 Days of drinking Lo-Cal beer.                       = 1 Lite-year

  reply	other threads:[~2007-12-11 16:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-11 15:28 [U-Boot-Users] [PATCH 0/6] cfi_flash cleanups Haavard Skinnemoen
2007-12-11 15:28 ` [U-Boot-Users] [PATCH 1/6] cfi_flash: Break long lines Haavard Skinnemoen
2007-12-11 15:28   ` [U-Boot-Users] [PATCH 2/6] cfi_flash: Make some needlessly global functions static Haavard Skinnemoen
     [not found]     ` <1197386900-14570-4-git-send-email-hskinnemoen@atmel.com>
2007-12-11 15:28       ` [U-Boot-Users] [PATCH 4/6] cfi_flash: Introduce read and write accessors Haavard Skinnemoen
2007-12-11 15:28         ` [U-Boot-Users] [PATCH 5/6] Introduce map_physmem() and unmap_physmem() Haavard Skinnemoen
2007-12-11 15:28           ` [U-Boot-Users] [PATCH 6/6] cfi_flash: Use " Haavard Skinnemoen
2007-12-11 15:36             ` Kumar Gala
2007-12-11 15:43               ` Haavard Skinnemoen
2007-12-11 18:49                 ` Stefan Roese
2007-12-12  9:36                   ` Haavard Skinnemoen
2007-12-12 10:24                     ` Stefan Roese
2007-12-11 22:10             ` Wolfgang Denk
2007-12-11 22:55               ` Andrew Dyer
2007-12-12  6:09                 ` Stefan Roese
2007-12-12  9:23               ` Haavard Skinnemoen
2007-12-11 15:35         ` [U-Boot-Users] [PATCH 4/6] cfi_flash: Introduce read and write accessors Kumar Gala
2007-12-11 15:46           ` Haavard Skinnemoen
2007-12-11 16:25             ` Wolfgang Denk [this message]
2007-12-11 17:13               ` Haavard Skinnemoen
2007-12-11 18:59                 ` Stefan Roese
2007-12-11 22:05                 ` Wolfgang Denk
2007-12-12  9:31                   ` Haavard Skinnemoen
2007-12-13 11:04   ` [U-Boot-Users] [PATCH 1/6] cfi_flash: Break long lines Stefan Roese
2007-12-11 19:04 ` [U-Boot-Users] [PATCH 0/6] cfi_flash cleanups Stefan Roese
2007-12-12 10:01   ` Haavard Skinnemoen

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=20071211162522.1574024657@gemini.denx.de \
    --to=wd@denx.de \
    --cc=u-boot@lists.denx.de \
    /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