From: Linus Torvalds <torvalds@transmeta.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
Eric Smith <eric@brouhaha.com>,
linux-kernel@vger.kernel.org, arjanv@redhat.com, mj@ucw.cz
Subject: Re: 2.4.2 yenta_socket problems on ThinkPad 240
Date: Sat, 16 Jun 2001 11:15:04 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0106161111041.9713-100000@penguin.transmeta.com> (raw)
In-Reply-To: <E15BKPA-0008O7-00@the-village.bc.nu>
On Sat, 16 Jun 2001, Alan Cox wrote:
>
> > core should be more than just the kissing cousins they are now. OTOH I
> > still don't like how much we trust firmware PCI bus setup on x86..
>
> The BIOS may make assumptions we dont know about such as the bus layout. What
> minimises the problem is effectively to validate the firmware provided PCI
> setup and if its crap, then do the job ourselves. That minimizes the problems
>
> Hence I think it should not be a define but an __init validator for the bus
> setup
Yes.
Regardless, it would certainly make sense to have a manual override, with
a kernel command line. If for no other reason than to allow for mistakes
and let the user force the old/new behaviour.
So the #define should be a variable with a kernel command line override,
along with a heuristic for the kernel to do a good guess on its own (and
the heuristic should probably not be as global as the current
"pcibios_assign_all_busses()" test - the heuristic will be able to tell on
a bridge basis on whether that bridge may need assignment. This might
imply giving the "pcibios_assign_all_busses()" thing the "dev" as an
argument).
Linus
next prev parent reply other threads:[~2001-06-16 18:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-15 23:14 2.4.2 yenta_socket problems on ThinkPad 240 Eric Smith
2001-06-15 23:25 ` Jeff Garzik
2001-06-16 13:25 ` Alan Cox
2001-06-16 17:55 ` Jeff Garzik
2001-06-16 18:02 ` Alan Cox
2001-06-16 18:15 ` Linus Torvalds [this message]
2001-06-22 23:14 ` Eric Smith
2001-06-22 23:27 ` Jeff Garzik
2001-06-16 18:16 ` Linus Torvalds
2001-06-17 4:03 ` Albert D. Cahalan
2001-06-16 18:10 ` Linus Torvalds
2001-06-16 18:23 ` Alan Cox
2001-06-16 19:22 ` Linus Torvalds
2001-06-16 21:11 ` [PATCH] " Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2001-06-07 0:09 Eric Smith
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=Pine.LNX.4.21.0106161111041.9713-100000@penguin.transmeta.com \
--to=torvalds@transmeta.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjanv@redhat.com \
--cc=eric@brouhaha.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mj@ucw.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).