From: Russell King <rmk@arm.linux.org.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Michael Frank <mflt1@micrologica.com.hk>,
linux-kernel <linux-kernel@vger.kernel.org>,
Pavel Machek <pavel@suse.cz>, John Belmonte <jvb@prairienet.org>
Subject: Re: 2.5.75-mm1 yenta-socket lsPCI IRQ reads incorrect
Date: Mon, 14 Jul 2003 16:21:38 +0100 [thread overview]
Message-ID: <20030714162138.B31395@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030714150435.GB5118@gtf.org>; from jgarzik@pobox.com on Mon, Jul 14, 2003 at 11:04:35AM -0400
On Mon, Jul 14, 2003 at 11:04:35AM -0400, Jeff Garzik wrote:
> On Mon, Jul 14, 2003 at 03:50:51PM +0100, Russell King wrote:
> > yenta_allocate_resources(socket);
> > +
> > + pci_save_state(dev, socket->saved_state);
> >
> > socket->cb_irq = dev->irq;
> >
>
> This reminds me, PCI Express makes the PCI config area larger, going
> from 256 bytes to either 4K or 64K IIRC.
>
> I wonder if we want new pci_{save,restore}_xstate functions?
> Or change the pci_{save,restore}_state API now to work with larger
> config areas?
Maybe we really want an API where you can pass in the size of your
buffer (which also determines how much gets saved) ?
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-07-14 15:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 5:41 Yenta_socket lsPCI IRQ reads incorrect Michael Frank
2003-07-14 9:07 ` Pavel Machek
2003-07-14 9:28 ` 2.5.75-mm1 yenta-socket " Michael Frank
2003-07-14 11:01 ` Russell King
2003-07-14 11:37 ` Michael Frank
2003-07-14 14:50 ` Russell King
2003-07-14 15:04 ` Jeff Garzik
2003-07-14 15:21 ` Russell King [this message]
2003-07-14 15:18 ` Michael Frank
2003-07-14 15:34 ` Russell King
2003-07-14 15:27 ` Michael Frank
2003-07-15 5:31 ` Michael Frank
2003-07-15 6:08 ` Michael Frank
2003-07-15 7:56 ` Russell King
2003-07-15 9:34 ` Michael Frank
2003-07-15 10:42 ` Michael Frank
2003-07-15 14:39 ` Russell King
2003-07-15 16:09 ` Michael Frank
2003-07-16 3:16 ` Michael Frank
2003-07-16 5:04 ` Michael Frank
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=20030714162138.B31395@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=jgarzik@pobox.com \
--cc=jvb@prairienet.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mflt1@micrologica.com.hk \
--cc=pavel@suse.cz \
/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).