All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Frank <mflt1@micrologica.com.hk>
To: Russell King <rmk@arm.linux.org.uk>, Jeff Garzik <jgarzik@pobox.com>
Cc: 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 23:18:07 +0800	[thread overview]
Message-ID: <200307142318.07232.mflt1@micrologica.com.hk> (raw)
In-Reply-To: <20030714162138.B31395@flint.arm.linux.org.uk>

On Monday 14 July 2003 23:21, Russell King wrote:
> 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:

I'll give that patch a go tomorrow.

> > >  	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) ?

Right, using the dword write function for 16 words or so is OK, but
rather clumsy for much more than that.

Regards
Michael
-- 
Powered by linux-2.5.75-mm1. Compiled with gcc-2.95-3 - mature and rock solid

My current linux related activities:
- 2.5 yenta_socket testing
- Test development and testing of swsusp for 2.4/2.5 and ACPI S3 of 2.5 kernel 
- Everyday usage of 2.5 kernel

More info on 2.5 kernel: http://www.codemonkey.org.uk/post-halloween-2.5.txt
More info on swsusp: http://sourceforge.net/projects/swsusp/


  reply	other threads:[~2003-07-14 15:16 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
2003-07-14 15:18             ` Michael Frank [this message]
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=200307142318.07232.mflt1@micrologica.com.hk \
    --to=mflt1@micrologica.com.hk \
    --cc=jgarzik@pobox.com \
    --cc=jvb@prairienet.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=rmk@arm.linux.org.uk \
    /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.