public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	"David S. Miller" <davem@redhat.com>,
	willy@debian.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 2.5] pci_{save,restore}_extended_state
Date: Sat, 25 Jan 2003 08:52:48 +0000	[thread overview]
Message-ID: <20030125085248.A4882@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20030124212403.A25285@jurassic.park.msu.ru>; from ink@jurassic.park.msu.ru on Fri, Jan 24, 2003 at 09:24:03PM +0300

On Fri, Jan 24, 2003 at 09:24:03PM +0300, Ivan Kokshaysky wrote:
> pci.h: added missing SIZEOFs for each capability as per PCI specs.
> I'm not 100% sure about PCI_CHSWP_SIZEOF and PCI_X_SIZEOF - somebody
> with respective specs in hands (Matthew?) ought to verify this...

PCI-X is 8 bytes -- ID, Next capability, 2-byte `Command', 4-byte `Status'

Except PCI-X bridges, which are 16-bytes long.  And I didn't write down the
definition for those.

Hotswap uses only 3 bytes, but the 4th byte is `reserved' so better save
4 bytes rather than 3.

>  #define  PCI_CHSWP_PI		0x30	/* Programming Interface */
>  #define  PCI_CHSWP_EXT		0x40	/* ENUM# status - extraction */
>  #define  PCI_CHSWP_INS		0x80	/* ENUM# status - insertion */
> +#define PCI_CHSWP_SIZEOF	4
>  
>  /* PCI-X registers */
>  
> @@ -309,6 +314,7 @@
>  #define  PCI_X_STATUS_MAX_SPLIT	0x0380	/* Design Max Outstanding Split Trans */
>  #define  PCI_X_STATUS_MAX_CUM	0x1c00	/* Designed Max Cumulative Read Size */
>  #define  PCI_X_STATUS_SPL_ERR	0x2000	/* Rcvd Split Completion Error Msg */
> +#define PCI_X_SIZEOF		9
>  
>  /* Include the ID list */
>  

-- 
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk

  parent reply	other threads:[~2003-01-25  8:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-24 18:24 [patch 2.5] pci_{save,restore}_extended_state Ivan Kokshaysky
2003-01-24 23:07 ` Jeff Garzik
2003-01-25  8:52 ` Matthew Wilcox [this message]
2003-01-25 17:25   ` [patch 2.5] pci_{save,restore}_extended_state, corrected Ivan Kokshaysky

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=20030125085248.A4882@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=davem@redhat.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@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