From: hvaibhav@ti.com (Vaibhav Hiremath)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP baseline test results for v3.7-rc3
Date: Tue, 30 Oct 2012 20:18:26 +0530 [thread overview]
Message-ID: <508FE8BA.1080404@ti.com> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A83EB51E84@DBDE01.ent.ti.com>
On 10/30/2012 6:09 PM, Hiremath, Vaibhav wrote:
> On Tue, Oct 30, 2012 at 17:17:00, Paul Walmsley wrote:
>> cc Vaibhav Hiremath
>>
>> On Tue, 30 Oct 2012, Mark Jackson wrote:
>>
>>> At what point is booting from MMC on the BeagleBone going to start working ?
>>>
>>> I only ask, since, by default, a new BeagleBone is setup to boot from
>>> MMC, so anyone testing a new kernel will probably expect the same setup
>>> to work.
>>
>> BeagleBone boots initramfs from MMC now, which is what mine was shipped to
>> do. Are you asking about rootfs on MMC? If so, Vaibhav would have a
>> better sense of this than I.
>>
>
> Mark,
>
> MMC is dependent on EDMA-DMA conversion patches from Matt, which he has
> already submitted to the list recently. So MMC support will come along with
> EDMA support. DMA-EDMA patches are targeted for v3.8, lets see how it goes.
>
>
> If you refer to the Matt's repo, you should get all the patches required to
> boot MMC support -
>
> https://github.com/ohporter/linux/tree/edma-dmaengine-am33xx-v3
>
>
I just tested this branch (+ one fix which Matt provided [1]) on
BeagleBone, and MMC is working without any issues. I have tested with
rootFS on MMC card.
[1] - http://www.spinics.net/lists/linux-omap/msg79911.html
Thanks,
Vaibhav
>
> Thanks,
> Vaibhav
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
next prev parent reply other threads:[~2012-10-30 14:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 2:36 OMAP baseline test results for v3.7-rc3 Paul Walmsley
2012-10-30 4:39 ` Vaibhav Hiremath
2012-10-30 13:03 ` Paul Walmsley
2012-11-05 2:41 ` Paul Walmsley
2012-11-06 6:09 ` Hiremath, Vaibhav
2012-11-06 10:24 ` Hiremath, Vaibhav
2012-10-30 10:55 ` Mark Jackson
2012-10-30 11:47 ` Paul Walmsley
2012-10-30 12:39 ` Hiremath, Vaibhav
2012-10-30 14:48 ` Vaibhav Hiremath [this message]
2012-10-30 16:27 ` Tony Lindgren
2012-10-30 17:27 ` Felipe Balbi
2012-10-30 17:58 ` Tony Lindgren
2012-10-30 18:51 ` Felipe Balbi
2012-11-06 6:17 ` Hiremath, Vaibhav
2012-11-06 7:58 ` Felipe Balbi
2012-11-06 8:07 ` Hiremath, Vaibhav
2012-11-06 8:05 ` Felipe Balbi
2012-10-31 13:41 ` Mark Jackson
2012-10-31 13:57 ` Hiremath, Vaibhav
2012-10-31 14:24 ` Mark Jackson
2012-11-01 15:52 ` Mark Jackson
2012-11-05 16:54 ` Mark Jackson
2012-11-06 6:16 ` Hiremath, Vaibhav
2012-11-06 9:47 ` Mark Jackson
2012-11-13 15:26 ` Mark Jackson
2012-11-13 15:35 ` Paul Walmsley
2012-11-13 15:57 ` Mark Jackson
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=508FE8BA.1080404@ti.com \
--to=hvaibhav@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).