From: Grant Grundler <grundler@cup.hp.com>
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Okay, I give up.
Date: Fri, 05 Nov 1999 23:27:11 -0800 [thread overview]
Message-ID: <199911060727.XAA15167@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Thu, 04 Nov 1999 23:07:28 PST." <Pine.LNX.4.10.9911042254060.16932-100000@vodka.thepuffingroup.com>
Alex deVries wrote:
> How do I extract an sversion and hversion out of ioscan -F output?
>
> For instance:
>
> pa:wsio:F:F:F:0:0:0:ext_bus:c720:8/12:1 49 0 132 0 0 137 128 7 0 0 0 91 62 0
> 2 :0:root.ccio.c720:c720:CLAIMED:INTERFACE:GSC add-on Fast/Wide SCSI Interf
> ace:0
1) Use ":" as a field seperator (that's probably obvious)
2) field 1 indicates the structure/contents of field 12.
"pa" says field 12 is IODC data (16 bytes).
"pci" says field 12 is PCI vendor/product (4 bytes).
3) IODC data format should be documented in IOACD or somewhere.
PCI isn't. It's the PCI vendor/product ID from config space.
Short (but cryptic) answer is first three "nibbles" (4-bit quantities)
are HV model. Next nibble is HV rev. SV rev is the high order nibble
of the 5th byte (iodc[4]). SV model the following 5 nibbles.
So printing the values in hex should make them easier to eye-ball
and correlate to either hardware.c entries or PCI output.
> There doesn't seem to be a consistant way to parse it.
The "pa" vs. "pci" probably makes it look inconsistent.
cheers,
grant
>
> - Alex
> --
> Alex deVries <adevries@thepuffingroup.com>
> Vice President Engineering
> The Puffin Group
>
> ---------------------------------------------------------------------------
> To unsubscribe: send e-mail to parisc-linux-request@thepuffingroup.com with
> `unsubscribe' as the subject.
>
Grant Grundler
Unix Developement Lab
+1.408.447.7253
next prev parent reply other threads:[~1999-11-06 7:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-05 4:07 [parisc-linux] Okay, I give up Alex deVries
1999-11-06 7:27 ` Grant Grundler [this message]
1999-11-06 19:04 ` Frank Rowand
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=199911060727.XAA15167@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=parisc-linux@thepuffingroup.com \
/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