From: Sven Schnelle <svens@stackframe.org>
To: John David Anglin <dave.anglin@bell.net>
Cc: Carlo Pisani <carlojpisani@gmail.com>,
Helge Deller <deller@gmx.de>,
linux-parisc@vger.kernel.org,
James Bottomley <James.Bottomley@hansenpartnership.com>
Subject: Re: [PATCH v3] parisc: Fix crash due alternative coding for NP iopdir_fdc bit
Date: Mon, 27 May 2019 22:22:07 +0200 [thread overview]
Message-ID: <20190527202207.GE29337@t470p.stackframe.org> (raw)
In-Reply-To: <7bb12d08-6a2a-11e0-774c-2498c7f8b607@bell.net>
Hi Dave,
On Mon, May 27, 2019 at 04:13:02PM -0400, John David Anglin wrote:
> On 2019-05-27 3:35 p.m., Carlo Pisani wrote:
> > isn't possible to burn the flash in the C3600 machine with the
> > firmware of C3750?
> > these two look similar.
> >
> Highly doubtful. Don't know where you would find firmware for either.
openpa.net has some, and i also extracted a few versions from HP-UX ISOs.
> Firmware needs to put on bootable device (tape drive!!!):
> https://www.manualslib.com/manual/436656/Hp-Visualize-B1000-Workstation.html?page=187#manual
I upgraded my C240 during the weekend with the latest PDC firmware via LAN. I think
this also worked on 712 (it's been ~15 years when i did that, so not 100% sure).
The firmware files are LIF images, so it's likely that updating via 'boot lan'
works on all machines.
On my C240 i had to set the minimum good memory size, if it is at zero the Firmware
update complains about not enough memory.
Regards
Sven
next prev parent reply other threads:[~2019-05-27 20:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 19:20 [PATCH v3] parisc: Fix crash due alternative coding for NP iopdir_fdc bit Helge Deller
2019-05-27 19:35 ` Carlo Pisani
2019-05-27 20:13 ` John David Anglin
2019-05-27 20:22 ` Sven Schnelle [this message]
2019-05-27 20:49 ` John David Anglin
2019-05-27 20:15 ` Sven Schnelle
2019-05-28 11:06 ` Sven Schnelle
2019-05-28 11:28 ` Rolf Eike Beer
2019-05-28 15:41 ` Sven Schnelle
2019-05-28 15:52 ` Helge Deller
[not found] ` <e81b7ae4-3126-5fda-58e4-4a83bd4fcfcf@bell.net>
2019-05-28 15:11 ` Helge Deller
2019-05-28 15:38 ` Sven Schnelle
2019-05-28 17:06 ` John David Anglin
2019-05-28 17:24 ` Rolf Eike Beer
2019-05-28 17:39 ` Sven Schnelle
2019-05-28 18:40 ` John David Anglin
2019-05-29 14:15 ` Helge Deller
2019-05-29 17:01 ` John David Anglin
2019-05-30 19:55 ` Sven Schnelle
2019-05-30 20:59 ` Sven Schnelle
2019-05-31 12:23 ` John David Anglin
2019-06-02 10:29 ` Carlo Pisani
2019-06-02 14:45 ` John David Anglin
2019-06-02 14:38 ` John David Anglin
2019-06-02 16:12 ` John David Anglin
2019-05-27 19:41 ` John David Anglin
2019-05-27 20:11 ` Helge Deller
2019-05-27 20:16 ` Carlo Pisani
2019-05-27 20:45 ` John David Anglin
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=20190527202207.GE29337@t470p.stackframe.org \
--to=svens@stackframe.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=carlojpisani@gmail.com \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=linux-parisc@vger.kernel.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.