From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: John David Anglin <dave.anglin@bell.net>
Cc: Sven Schnelle <svens@stackframe.org>,
Helge Deller <deller@gmx.de>,
Carlo Pisani <carlojpisani@gmail.com>,
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: Tue, 28 May 2019 19:24:29 +0200 [thread overview]
Message-ID: <1943613.tnj53yOHQY@daneel.sf-tec.de> (raw)
In-Reply-To: <674f8b61-e897-f657-68a2-648babca00be@bell.net>
[-- Attachment #1: Type: text/plain, Size: 790 bytes --]
Am Dienstag, 28. Mai 2019, 19:06:48 CEST schrieb John David Anglin:
> On 2019-05-28 11:38 a.m., Sven Schnelle wrote:
> > Interesting. Now that you mention it i see that my C3750 reports the same.
> > Google returned the following page
> > https://support.hpe.com/hpsc/swd/public/detail?swItemId=PF_CCJ70020
> >
> > Which is 2.0, and only mentions "C3650/C3700/C3750/J6700/J6750 firmware"
> > So maybe these machines have NP set, and machines "below" (like C3600)
> > don't have it set.
> >
> > I wonder what happens if you try to flash a 5.0 firmware to such a box.
>
> From what I see, the "C3650/C3700/C3750/J6700/J6750" and "HP 9000 Model
> B1000/C3000/J5000/J7000" use different firmware.
Which makes sense as the former have use a 8600 CPU, while the latter have
8700 ones.
Eike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2019-05-28 17:24 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
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 [this message]
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=1943613.tnj53yOHQY@daneel.sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=James.Bottomley@hansenpartnership.com \
--cc=carlojpisani@gmail.com \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=linux-parisc@vger.kernel.org \
--cc=svens@stackframe.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.