All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "\"임근식\"" <invain@naver.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Re: Help me. Oops: 805 [#1]err using kernel.2.6.10.omap1patch with NFS(RFS)
Date: Thu, 19 Jan 2006 17:10:00 -0800	[thread overview]
Message-ID: <20060120011000.GV4425@atomide.com> (raw)
In-Reply-To: <43D03607.000001.29461@naver892>

* "임근식" <invain@naver.com> [060119 17:07]:
> 
> Thank you for offering you patch file. But, I tried thus patch work already for solve this problem.
> In the long run , Although I adjusted patch to smc91x.c file, booting still is failed with nfs RFS.
> I am poor knowledge about device dirver. If possible, I need technique of veteran engineer.
> 
> P.S: When i send packet using nmap tool from host(192.168.0.2) to target(192.168.0.10) ,
> Below message appeared on minicom console.
> -------------------------------------------------------
> eth0: bad memory timings: rxlen 0 status 507f
> eth0: bad memory timings: rxlen 0 status 407f
> -------------------------------------------------------

See what board-osk.c does for EMIFS:

static void __init osk_init_smc91x(void)
{
        if ((omap_request_gpio(0)) < 0) {
                printk("Error requesting gpio 0 for smc91x irq\n");
                return;
        }

        /* Check EMIFS wait states to fix errors with SMC_GET_PKT_HDR */
        EMIFS_CCS(1) |= 0x3;
}

Regards,

Tony

  reply	other threads:[~2006-01-20  1:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-20  0:59 Re: Help me. Oops: 805 [#1]err using kernel.2.6.10.omap1patch with NFS(RFS) "임근식"
2006-01-20  1:10 ` Tony Lindgren [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-20  1:02 "임근식"
2006-01-19 11:50 "임근식"

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=20060120011000.GV4425@atomide.com \
    --to=tony@atomide.com \
    --cc=invain@naver.com \
    --cc=linux-omap-open-source@linux.omap.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 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.