From: Grant Likely <glikely@gmail.com>
To: Andrew Williams <awilliam@nortel.com>, linuxppc-embedded@ozlabs.org
Subject: Re: COP Status 0x21
Date: Thu, 25 Aug 2005 10:18:32 -0600 [thread overview]
Message-ID: <20050825161832.GB6154@siegfried.thelikelysolution.ca> (raw)
In-Reply-To: <713043CE8B8E1348AF3C546DBE02C1B4049162C5@zcarhxm2.corp.nortel.com>
On Thu, Aug 25, 2005 at 11:19:31AM -0400, Andrew Williams wrote:
> <insert favorite curses here>
>
> Spend 6 hours searching, draft an email to the list, and solve
> problem 20 minutes later. Compared my BDI to a co-workers and
> and discovered that although we had the same firmware, we didn't have
> the same "Logic" version in the device. Reflashed and I can
> now read the PVR correctly.
>
> Sorry to waste everyone's time on this.
Ah, but the next person to have this problem (should) find your post
when they search. :)
next prev parent reply other threads:[~2005-08-25 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 15:19 COP Status 0x21 Andrew Williams
2005-08-25 16:18 ` Grant Likely [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-25 14:38 Andrew Williams
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=20050825161832.GB6154@siegfried.thelikelysolution.ca \
--to=glikely@gmail.com \
--cc=awilliam@nortel.com \
--cc=linuxppc-embedded@ozlabs.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).