All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mmc: seperate block number into small parts for multi-write cmd
Date: Sun, 10 Oct 2010 08:48:22 +0200	[thread overview]
Message-ID: <20101010064822.ED08C14F310@gemini.denx.de> (raw)
In-Reply-To: <AANLkTi=qBk7N+SdW_6K1=ywKM1ZKo5F-518Q7qceNXws@mail.gmail.com>

Dear Lei Wen,

In message <AANLkTi=qBk7N+SdW_6K1=ywKM1ZKo5F-518Q7qceNXws@mail.gmail.com> you wrote:
> 
> Although the common code is named as mmc.c, I think a lot of people use it
> to work for sd too, since they are compatible in most case.

Right. And where SD drivers differ, such differeng code should be
provided by the SD drivers, and not pulled into the common code parts.

> the driver cannot do nothing unless a mess change.

Please explain why that shouldnot be possible. It's the driver that
accesses your hardware, so it has full control over everything going
on.


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
Dealing with failure is easy: work hard to improve. Success  is  also
easy  to  handle:  you've  solved  the  wrong  problem.  Work hard to
improve.

  reply	other threads:[~2010-10-10  6:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-06  7:19 [U-Boot] [PATCH] mmc: seperate block number into small parts for multi-write cmd Lei Wen
2010-09-06  8:28 ` Wolfgang Denk
2010-09-06  8:40   ` Lei Wen
2010-09-06  9:23 ` Reinhard Meyer
2010-09-06  9:31   ` Lei Wen
2010-09-06 10:16     ` Reinhard Meyer
2010-09-06 10:48       ` Lei Wen
2010-09-06 11:50         ` Reinhard Meyer
2010-10-10  4:20           ` Lei Wen
2010-10-10  6:48             ` Wolfgang Denk [this message]
2010-10-10  8:49               ` Lei Wen
2010-10-10  9:22                 ` Wolfgang Denk
2010-10-10  9:27                   ` Lei Wen
2010-10-10  9:39                     ` Reinhard Meyer
2010-10-10  9:44                       ` Lei Wen
2010-10-10  9:33                   ` Reinhard Meyer
2010-10-10  9:42                     ` Lei Wen
2010-10-11  3:42                     ` [U-Boot] [PATCH V2] " Lei Wen
2010-10-11  9:00                       ` Reinhard Meyer
2010-10-11  9:22                         ` Wolfgang Denk
2010-10-11  9:27                           ` Lei Wen
2010-10-11 10:44 ` [U-Boot] [PATCH] " Reinhard Meyer
2010-10-11 11:35   ` Wolfgang Denk
2010-10-11 15:39     ` [U-Boot] [PATCH V3] " Lei Wen
2010-10-13 19:57       ` Wolfgang Denk
2010-10-14  5:38         ` [U-Boot] [PATCH V4] " Lei Wen
2010-10-25 18:46           ` Steve Sakoman
2010-10-27 18:39           ` Wolfgang Denk
2010-10-27 19:59             ` Steve Sakoman
2010-10-27  6:04         ` [U-Boot] [PATCH V3] " Lei Wen

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=20101010064822.ED08C14F310@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.