public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Joey Oravec <joravec@drewtech.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] CONFIG_MMC: mapping the device to physical memoryfor sharp ZAURUS
Date: Thu, 21 Jun 2007 09:00:58 -0400	[thread overview]
Message-ID: <f5dsqp$djj$1@sea.gmane.org> (raw)
In-Reply-To: 187928.85495.qm@web57312.mail.re1.yahoo.com

"my lists" <lists_my@yahoo.com> wrote in message 
news:187928.85495.qm at web57312.mail.re1.yahoo.com...
> CFG_MMC_BASE: is this the base address where MMC is mapped ?
>
> include/configs/pxa255_idp.h:#define CFG_MMC_BASE               0xF0000000
> is this usable gererically for pxa255 or only for that specific board ?
> if not how can I find out where it is mapped (if there is no tech 
> documentation
> avalible for sharp Zaurus) ?

Take a look at cpu/pxa/mmc.c. This adds a few functions like 
mmc_block_read(), mmc_block_write(), and mmc_init() which interact with the 
media card. Typically init will register the card as a FAT filesystem, and 
you'll let those functions interact with the card.

In my version of the code, CFG_MMC_BASE mainly affects the "cp" command in 
common/cmd_mem.c. Some functions like that will let you interact with the 
card as a raw device, as if it were mapped into unused memory. They'll call 
mmc2info() to decide if the address is within that assigned range. I don't 
find this feature very useful and always interact with the card as a 
filesystem.

-joey 

  reply	other threads:[~2007-06-21 13:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-20 20:32 [U-Boot-Users] CONFIG_MMC: mapping the device to physical memory for sharp ZAURUS my lists
2007-06-21 13:00 ` Joey Oravec [this message]
2007-06-21 16:18   ` [U-Boot-Users] CONFIG_MMC: mapping the device to physical memoryfor " my lists
2007-06-21 17:33     ` [U-Boot-Users] CONFIG_MMC: mapping the device to physicalmemoryfor " Joey Oravec
2007-06-25 21:57     ` [U-Boot-Users] pxa255: ZAURUS boards my lists

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='f5dsqp$djj$1@sea.gmane.org' \
    --to=joravec@drewtech.com \
    --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