public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Harald Welte <laforge@gnumonks.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6] fix pci_update_resource() / IORESOURCE_UNSET on PPC
Date: Wed, 24 Dec 2003 12:04:33 -0800	[thread overview]
Message-ID: <20031224200433.GC6577@kroah.com> (raw)
In-Reply-To: <20031224111054.GB941@obroa-skai.de.gnumonks.org>

On Wed, Dec 24, 2003 at 12:10:55PM +0100, Harald Welte wrote:
> Hi!
> 
> [disclaimer:  This was posted on the linuxppc list before, BenH asked me 
>  to re-post it to lkml]
> 
> The prism54 (http://prism54.org) driver for my cardbus adapter works
> with 2.4.x, but not 2.6.x on a Titanium G4 Powerbook IV.
> 
> On 2.6.x the error message was
> PCI:0001:02:00.0 Resource 0 [00000000-00001fff] is unassigned
> 
> After investigating differences in the PCI code of 2.4.x and 2.6.x, i
> noticed that 2.4.x/arc/ppc/kernel/pci.c:pcibios_update_resource()
> contained a couple of lines that unset the IORESOURCE_UNSET bitflag.
> 
> In 2.6.x, this is handled by the generic PCI core in
> drivers/pci/setup-res.c:pci_update_resource() code.  However, the code
> is missing the 'res->flags &= ~IORESOURCE_UNSET' part.
> 
> The below fix re-adds that section from 2.4.x. 
> 
> I'm not sure wether this belongs into the arch-independent PCI api.
> Anyway, on PPC it seems to be needed for certain cardbus devices.

Is there any way you can add this to the ppc arch specific code, as
that's the only platform that seems to want this, right?

thanks,

greg k-h

  reply	other threads:[~2003-12-24 20:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-24 11:10 [PATCH 2.6] fix pci_update_resource() / IORESOURCE_UNSET on PPC Harald Welte
2003-12-24 20:04 ` Greg KH [this message]
2003-12-24 20:33   ` Safe ISA port probing? Ben Srour
2003-12-24 21:12     ` Randy.Dunlap
2003-12-26  8:46   ` [PATCH 2.6] fix pci_update_resource() / IORESOURCE_UNSET on PPC Harald Welte

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=20031224200433.GC6577@kroah.com \
    --to=greg@kroah.com \
    --cc=laforge@gnumonks.org \
    --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