From: Archit Taneja <a0393947@ti.com>
To: "S, Venkatraman" <svenkatr@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: NFS mount issue with OMAP4 on linux-next
Date: Tue, 24 Jul 2012 12:37:45 +0530 [thread overview]
Message-ID: <500E49C1.3000703@ti.com> (raw)
In-Reply-To: <CANfBPZ_EJJk_HRCpUpZHauJCjJ8HgQO=YC104roEcKsAAw=iMA@mail.gmail.com>
On Tuesday 24 July 2012 12:23 PM, S, Venkatraman wrote:
> On Tue, Jul 24, 2012 at 11:48 AM, Archit Taneja <a0393947@ti.com> wrote:
>> Hi,
>>
>> Comparing with working logs, I see this difference:
>>
>> [ 1.502166] spi spi1.0: no RX DMA engine channel for McSPI
>> [ 1.507904] omap2_mcspi omap2_mcspi.1: can't setup spi1.0, status -11
>> [ 1.514862] omap2_mcspi omap2_mcspi.1: can't create new device for ks8851
>>
>> I guess that's why it isn't working?
>>
> Most likely yes. SPI is needed for ethernet on OMAP4.
> Please include this patch in your build and check..
> http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap.git;a=commit;h=55936cdfaaf11ac352b56bc58e42d6661e65ee13
It works fine with this.
Thanks,
Archit
>
>
prev parent reply other threads:[~2012-07-24 7:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 6:07 NFS mount issue with OMAP4 on linux-next Archit Taneja
2012-07-24 6:18 ` Archit Taneja
2012-07-24 6:53 ` S, Venkatraman
2012-07-24 7:07 ` Archit Taneja [this message]
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=500E49C1.3000703@ti.com \
--to=a0393947@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=svenkatr@ti.com \
/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