From: Sven Schnelle <svens@stackframe.org>
To: Helge Deller <deller@gmx.de>
Cc: John David Anglin <dave.anglin@bell.net>,
Carlo Pisani <carlojpisani@gmail.com>,
Grant Grundler <grantgrundler@gmail.com>,
linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: HPPA problems with the PCI
Date: Sat, 25 May 2019 22:37:30 +0200 [thread overview]
Message-ID: <20190525203729.GA21294@t470p.stackframe.org> (raw)
In-Reply-To: <1a4a708b-09a0-cb46-1491-554df106967a@gmx.de>
Hi Helge,
On Sat, May 25, 2019 at 09:09:04PM +0200, Helge Deller wrote:
> > It's also set on my C3750, but not on my J5000 (PDC FW 5.0):
> >
> > root@j5000:~# cat /proc/cpuinfo
> > cpu : PA8500 (PCX-W)
> > capabilities : os32 os64 nva_supported (0x03)
> > model : 9000/785/J5000
> > model name : Forte W 2-way
>
> Carlo & Sven, do you run 32- or 64-bit kernel?
> Maybe the 32-bit PDC does not return the NP (iopdir_fdc) while the 64-bit PDC does?
> Otherwise we maybe should only trust this bit, if it's a "PA8700 (PCX-W2)" or higher CPU ?
This was on 32 bit, but i tested it on 64 bit now and the iopdir_fdc flag is
also not present. Can't say whether your >PA-8700 idea is good or bad, don't
know enough about PA-RISC CPUs.
Sven
next prev parent reply other threads:[~2019-05-25 20:37 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+QBN9Cg6QAe5W3vS3dere=K53NAHDrMb9FN5StEfNkC=RTGqg@mail.gmail.com>
[not found] ` <CA+QBN9B7B39NARTNYan2wrhRLSEAhxukTy0B6yWRMUxgLJmuNA@mail.gmail.com>
2019-05-23 0:38 ` HPPA problems with the PCI Grant Grundler
2019-05-23 1:09 ` John David Anglin
2019-05-23 4:43 ` Grant Grundler
2019-05-23 16:10 ` John David Anglin
2019-05-23 21:48 ` Carlo Pisani
2019-05-23 23:18 ` Grant Grundler
[not found] ` <CAP6odjh2-HhbPYhFqc40cVCrVc6E689CM65WqbiTOnTRgeQojQ@mail.gmail.com>
2019-05-23 12:14 ` John David Anglin
2019-05-23 12:16 ` Carlo Pisani
2019-05-23 13:44 ` Carlo Pisani
2019-05-23 23:09 ` Grant Grundler
2019-05-24 6:39 ` Sven Schnelle
2019-05-24 18:12 ` Grant Grundler
2019-05-25 9:01 ` Carlo Pisani
2019-05-25 14:13 ` John David Anglin
2019-05-25 17:15 ` Helge Deller
2019-05-25 17:19 ` Carlo Pisani
2019-05-25 17:50 ` John David Anglin
2019-05-25 18:13 ` Sven Schnelle
2019-05-25 18:30 ` Carlo Pisani
2019-05-25 19:09 ` Helge Deller
2019-05-25 19:20 ` Carlo Pisani
2019-05-25 19:24 ` Helge Deller
2019-05-25 19:46 ` Rolf Eike Beer
2019-05-25 19:34 ` Carlo Pisani
2019-05-25 20:37 ` Sven Schnelle [this message]
2019-05-25 17:20 ` John David Anglin
2019-05-25 20:54 ` John David Anglin
2019-05-25 20:56 ` Sven Schnelle
2019-05-27 17:43 ` John David Anglin
2019-05-31 15:27 ` Grant Grundler
2019-05-24 7:06 ` Sven Schnelle
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=20190525203729.GA21294@t470p.stackframe.org \
--to=svens@stackframe.org \
--cc=carlojpisani@gmail.com \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=grantgrundler@gmail.com \
--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 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).