From: "Remi Lefevre" <rlefevre@gmail.com>
To: "Scott Wood" <scottwood@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: FS_ENET ERROR(s) 0x12 at second NFS RPC port lookup (100005/1)
Date: Thu, 9 Oct 2008 21:46:42 +0200 [thread overview]
Message-ID: <4e0b9cb00810091246i2f200dbn9f8dc9877800e629@mail.gmail.com> (raw)
In-Reply-To: <48E393E6.7000505@freescale.com>
Ok, I'm sorry, I have incorrectly set the 60x pipeline depth to 0
instead of 1 in BCR register.
It works fine now. The side effect is interesting to know...
regards,
r=E9mi
prev parent reply other threads:[~2008-10-09 19:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 16:44 FS_ENET ERROR(s) 0x12 at second NFS RPC port lookup (100005/1) Remi Lefevre
2008-09-30 17:33 ` Scott Wood
2008-10-01 13:36 ` Remi Lefevre
2008-10-01 15:14 ` Scott Wood
2008-10-09 19:46 ` Remi Lefevre [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=4e0b9cb00810091246i2f200dbn9f8dc9877800e629@mail.gmail.com \
--to=rlefevre@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=scottwood@freescale.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;
as well as URLs for NNTP newsgroup(s).