From: Reinhard Meyer <u-boot@emk-elektronik.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] MMC initialisation
Date: Thu, 06 Jan 2011 05:06:59 +0100 [thread overview]
Message-ID: <4D253FE3.8060708@emk-elektronik.de> (raw)
In-Reply-To: <4D253B1E.4070707@emk-elektronik.de>
Arghhh....
Didn't see the original message was not sent to the list...
So my reply was neither...
On 06.01.2011 04:46, Reinhard Meyer wrote:
> Dear ????,
Please, dear Henry, ALL u-boot related questions MUST go to the mailing list, too.
>> I will porting U-Boot mmc part to my own board, still use U-Boot as bootloader.
>> First, I should research the source code of mmc part in U-Boot.
>> I found top9000eval_xe board support mmc, and SoC same with mine, (arm926ejs)
>> Mr. Reinhard Meyer is enthusiastic working here, Thanks a lot!
>> Let me describe mmc driver init process: (version: u-boot.2010.12)
>> 1. arch/arm/lib/board.c -> board_init_r() -> mmc_initialize(bd);
>> 2. drivers/mmc/mmc.c -> int mmc_initialize(bd_t *bis)
>> 3. board/emk/top9000/top9000.c -> int board_mmc_init(bd_t *bd)
>> -> return atmel_mci_init((void *)AT91_BASE_MCI);
>> 4. drivers/mmc/gen_atmel_mci.c -> int atmel_mci_init(void *regs)
> ...
>> mmc->init = mci_init;
>> // mmc->init(mmc); // How it Implementation
>> /* need to be able to pass these in on a board by board basis */
> ...
>
> I am not sure what your question/problem is here.
>
> If you wonder how and when mmc->init() is called, it is only called when the
> command "mmcinfo" is given.
>
> This is sure not perfect, and discussions have been around about this.
> "common/cmd_mmc.c" would need some rework there...
>
> However discussions are left open on how exactly changes should be done.
>
> Best Regards,
> Reinhard
parent reply other threads:[~2011-01-06 4:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4D253B1E.4070707@emk-elektronik.de>]
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=4D253FE3.8060708@emk-elektronik.de \
--to=u-boot@emk-elektronik.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