From: Jon Smirl <jonsmirl@gmail.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: "David S. Miller" <davem@davemloft.net>,
benh@kernel.crashing.org, linux-kernel@vger.kernel.org,
greg@kroah.com, helgehaf@aitel.hist.no
Subject: Re: Ignore disabled ROM resources at setup
Date: Tue, 30 Aug 2005 00:51:23 -0400 [thread overview]
Message-ID: <9e473391050829215148807c49@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0508292125571.3243@g5.osdl.org>
On 8/30/05, Linus Torvalds <torvalds@osdl.org> wrote:
>
>
> On Mon, 29 Aug 2005, David S. Miller wrote:
> >
> > So I think the kernel, by not enabling the ROM, is doing the
> > right thing here.
>
> Notice that on ppc even older versions didn't actually _enable_ the rom,
> but they would write the non-enabled address to the PCI_ROM_ADDRESS
> register, so that anybody who read that register would see _where_ the ROM
> would be enabled if it was enabled.
>
> That's the thing that changed in the commit Ben dislikes. Now, if the ROM
> is disabled, we won't even write the disabled address to the PCI register,
> because it led to trouble on some strange Matrox card. Probably a card
> that nobody has ever used on PPC, and certainly not on a Powerbook, so in
> that sense the apparent breakage on ppc is arguably "unnecessary" as far
> as Ben is concerned.
>
> But I notice the problem: pci_enable_rom() is indeed broken with the
> change.
>
> Ben, does this (totally untested) patch fix it for you?
>
> Linus
>
> ----
> diff --git a/drivers/pci/rom.c b/drivers/pci/rom.c
> --- a/drivers/pci/rom.c
> +++ b/drivers/pci/rom.c
> @@ -23,11 +23,14 @@
> */
> static void pci_enable_rom(struct pci_dev *pdev)
> {
> - u32 rom_addr;
> + struct resource *res = pdev->resource + PCI_ROM_RESOURCE;
> + struct pci_bus_region region;
>
> - pci_read_config_dword(pdev, pdev->rom_base_reg, &rom_addr);
> - rom_addr |= PCI_ROM_ADDRESS_ENABLE;
> - pci_write_config_dword(pdev, pdev->rom_base_reg, rom_addr);
> + if (!res->flags)
> + return;
> +
> + pcibios_resource_to_bus(pdev, ®ion, res);
> + pci_write_config_dword(pdev, pdev->rom_base_reg, region.start | PCI_ROM_ADDRESS_ENABLE);
> }
I was reading the status out of the PCI config space to account for
our friend X which enables ROMs without informing the OS. With X
around PCI config space can get out of sync with the kernel
structures.
>
> /**
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2005-08-30 4:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200508261859.j7QIxT0I016917@hera.kernel.org>
2005-08-30 2:38 ` Ignore disabled ROM resources at setup Benjamin Herrenschmidt
2005-08-30 3:15 ` Linus Torvalds
2005-08-30 4:47 ` Jon Smirl
2005-08-30 3:19 ` Benjamin Herrenschmidt
2005-08-30 3:52 ` Linus Torvalds
2005-08-30 4:09 ` Linus Torvalds
2005-08-30 4:20 ` David S. Miller
2005-08-30 4:37 ` Benjamin Herrenschmidt
2005-08-30 4:40 ` Linus Torvalds
2005-08-30 4:49 ` Benjamin Herrenschmidt
2005-08-30 5:29 ` Linus Torvalds
2005-08-30 6:46 ` Benjamin Herrenschmidt
2005-08-31 4:16 ` Benjamin Herrenschmidt
2005-08-30 4:51 ` Jon Smirl [this message]
2005-08-30 4:54 ` Benjamin Herrenschmidt
2005-08-30 5:15 ` Linus Torvalds
2005-08-30 14:39 ` Alan Cox
2005-08-30 15:29 ` Petr Vandrovec
2005-08-30 4:33 ` Benjamin Herrenschmidt
2005-08-30 5:03 ` Linus Torvalds
2005-08-30 6:40 ` Benjamin Herrenschmidt
2005-08-30 4:35 ` Jon Smirl
2005-08-30 5:32 ` David S. Miller
2005-08-30 6:43 ` Benjamin Herrenschmidt
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=9e473391050829215148807c49@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=greg@kroah.com \
--cc=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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