From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
"David S. Miller" <davem@davemloft.net>,
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 14:54:12 +1000 [thread overview]
Message-ID: <1125377653.11963.57.camel@gaston> (raw)
In-Reply-To: <9e473391050829215148807c49@mail.gmail.com>
>
> 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.
Well, X isn't supposed to keep the ROM enabled is it ? besides, most of
the time, the kernel code will be run at boot. I think we shouldn't care
here. If X does the wrong thing, it will eventually break but it
shouldn't break in the "normal" case and it will ultimately be fixed
(finger crossed) by R7.1
Ben.
next prev parent reply other threads:[~2005-08-30 4:59 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
2005-08-30 4:54 ` Benjamin Herrenschmidt [this message]
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=1125377653.11963.57.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=greg@kroah.com \
--cc=helgehaf@aitel.hist.no \
--cc=jonsmirl@gmail.com \
--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 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.