From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: for which OMAP platform is MCI_OMAP_HSMMC appropriate?
Date: Tue, 7 Feb 2012 17:20:12 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.02.1202071718260.4214@oneiric> (raw)
In-Reply-To: <20120207221213.GG3852@pengutronix.de>
On Tue, 7 Feb 2012, Sascha Hauer wrote:
> On Tue, Feb 07, 2012 at 03:42:14PM -0500, Robert P. J. Day wrote:
> >
> > from drivers/mci/Kconfig:
> >
> > config MCI_OMAP_HSMMC
> > bool "OMAP HSMMC"
> > depends on ARCH_OMAP4 || ARCH_OMAP3
> > help
> > Enable this entry to add support to read and write SD cards on a
> > OMAP4 based system.
> >
> > i assume you can see the confusion. :-)
>
> I added this driver for the OMAP4 and forgot to adjust this when I
> realized that it works on OMAP3 aswell. U-boot uses this driver for
> omap5 also, so we better just drop the '4' in OMAP4.
ok, i can submit an adjusted patch but what would this depend on
then? OMAP 3,4 and 5, or OMAP in general? maybe you better handle
that, then, i'm not sure what the proper set of dependencies is.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-02-07 22:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 20:42 Robert P. J. Day
2012-02-07 22:12 ` Sascha Hauer
2012-02-07 22:20 ` Robert P. J. Day [this message]
2012-02-07 22:30 ` Sascha Hauer
2012-02-07 22:31 ` Robert P. J. Day
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=alpine.DEB.2.02.1202071718260.4214@oneiric \
--to=rpjday@crashcourse.ca \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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