All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Greg Griffes" <ggg@ieee.org>
To: "None Atall" <linux_meis@yahoo.com>
Cc: "linuxppc-embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Raven Cop 8260 Utility
Date: Thu, 14 Feb 2002 20:40:17 -0500	[thread overview]
Message-ID: <006401c1b5c1$b9265fe0$6401a8c0@attbi.com> (raw)
In-Reply-To: 20020214143150.11108.qmail@web9701.mail.yahoo.com


Some flash parts have a WP* pin that "protects" the flash boot sectors only.  Often, designers will wire that input to a discrete
that can be controlled by software.

Greg Griffes
Smiths Aerospace

----- Original Message -----
From: "None Atall" <linux_meis@yahoo.com>
To: "Wolfgang Denk" <wd@denx.de>
Cc: "Bruno Coudoin" <bcoudoin@anfora.fr>; "linuxppc-embedded" <linuxppc-embedded@lists.linuxppc.org>
Sent: Thursday, February 14, 2002 9:31 AM
Subject: Re: Raven Cop 8260 Utility


>
>  We have tried it to. We have reached the conclution
> that perhaps the specific flash has a hardware
> problem.
> Not even the startup monitor that BlueCat distributes
> could be writen into flash. I couldn't ether make
> ppcboot write into flash. Really strange. But it
> doesn't realy matters, since I found at least one way
> to run ppcboot. :)
>
>                  Thanks
>                    D. Meidanis


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

       reply	other threads:[~2002-02-15  1:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020214143150.11108.qmail@web9701.mail.yahoo.com>
2002-02-15  1:40 ` Greg Griffes [this message]
2002-02-15  9:32   ` Raven Cop 8260 Utility None Atall
     [not found] <20020214134601.48635.qmail@web9706.mail.yahoo.com>
2002-02-14 14:02 ` Wolfgang Denk
2002-02-14 10:13 Bruno Coudoin
2002-02-14 11:01 ` Wolfgang Denk
2002-02-14 11:26   ` Bruno Coudoin

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='006401c1b5c1$b9265fe0$6401a8c0@attbi.com' \
    --to=ggg@ieee.org \
    --cc=linux_meis@yahoo.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 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.