public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] powerpc/esdhc: force the bus width to 4bit
Date: Fri, 2 Nov 2012 04:40:55 +0100	[thread overview]
Message-ID: <201211020440.55574.marex@denx.de> (raw)
In-Reply-To: <110EED8CC96DFC488B7E717A2027A27C210B1B@039-SN1MPN1-004.039d.mgd.msft.net>

Dear Huang Changming-R66093,

> Thanks, Jaehoon, I saw it.
> 
> Best Regards
> Jerry Huang

I wonder if you're just making fun of all of us or what you're actually trying 
to acomplish here with the constant top-posting ... I'm really stunned :-(

> > -----Original Message-----
> > From: Jaehoon Chung [mailto:jh80.chung at samsung.com]
> > Sent: Friday, November 02, 2012 10:03 AM
> > To: Huang Changming-R66093
> > Cc: Andy Fleming; Lukasz Majewski; Jaehoon Chung; Marek Vasut; u-
> > boot at lists.denx.de; Wen; Lei at theia.denx.de
> > Subject: Re: [U-Boot] [PATCH] powerpc/esdhc: force the bus width to 4bit
> > 
> > Hi,
> > 
> > Andy has sent the patch related with this problem.
> > Check the patch "[RFC] mmc: Properly determine maximum supported bus
> > width"
> > 
> > Best Regards,
> > Jaehoon Chung
> > 
> > >> decide the best workaround was to cripple our controller by
> > >> eliminating support for 8-bit?
> > > 
> > > I see 12bit width when using mmcinfo, then found out the mmc.c has
> > > been changed, and I assume this change is right, So I have to force our
> > 
> > controller to just support 4bit width, otherwise, the 12bit bus width is
> > not correct.
> > 
> > > _______________________________________________
> > > U-Boot mailing list
> > > U-Boot at lists.denx.de
> > > http://lists.denx.de/mailman/listinfo/u-boot

Best regards,
Marek Vasut

  reply	other threads:[~2012-11-02  3:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23  6:26 [U-Boot] [PATCH] powerpc/esdhc: force the bus width to 4bit Chang-Ming.Huang at freescale.com
2012-10-23  7:24 ` Marek Vasut
2012-10-23  9:23   ` Huang Changming-R66093
2012-10-23  9:50     ` Marek Vasut
2012-10-24  3:11       ` Huang Changming-R66093
2012-10-30  8:43       ` Jaehoon Chung
2012-10-30 17:35         ` Lukasz Majewski
2012-10-31  4:51           ` Jaehoon Chung
2012-10-31  8:20             ` Lukasz Majewski
2012-10-31 10:43               ` Jaehoon Chung
2012-11-01  4:09           ` Andy Fleming
2012-11-02  1:54             ` Huang Changming-R66093
2012-11-02  2:03               ` Jaehoon Chung
2012-11-02  2:15                 ` Huang Changming-R66093
2012-11-02  3:40                   ` Marek Vasut [this message]
2012-11-02  7:38             ` Lukasz Majewski
     [not found] <1351586621-1990-1-git-send-email-Chang-Ming.Huang@freescale.com>
     [not found] ` <110EED8CC96DFC488B7E717A2027A27C203263@039-SN1MPN1-003.039d.mgd.msft.net>
     [not found]   ` <110EED8CC96DFC488B7E717A2027A27C2058C8@039-SN1MPN1-003.039d.mgd.msft.net>
2012-11-01  2:29     ` Marek Vasut
     [not found] ` <201211010326.29763.marex@denx.de>
     [not found]   ` <110EED8CC96DFC488B7E717A2027A27C20B95C@039-SN1MPN1-004.039d.mgd.msft.net>
2012-11-01  3:05     ` Marek Vasut
2012-11-01  3:20       ` Huang Changming-R66093

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=201211020440.55574.marex@denx.de \
    --to=marex@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