linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: jgarzik@mandrakesoft.com (Jeff Garzik)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
	eric@brouhaha.com (Eric Smith),
	linux-kernel@vger.kernel.org,
	torvalds@transmeta.com (Linus Torvalds),
	arjanv@redhat.com, mj@ucw.cz
Subject: Re: 2.4.2 yenta_socket problems on ThinkPad 240
Date: Sat, 16 Jun 2001 19:02:40 +0100 (BST)	[thread overview]
Message-ID: <E15BKPA-0008O7-00@the-village.bc.nu> (raw)
In-Reply-To: <3B2B9DA3.3E310BF7@mandrakesoft.com> from "Jeff Garzik" at Jun 16, 2001 01:55:47 PM

> 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


  reply	other threads:[~2001-06-16 18:05 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 [this message]
2001-06-16 18:15         ` Linus Torvalds
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=E15BKPA-0008O7-00@the-village.bc.nu \
    --to=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 \
    --cc=torvalds@transmeta.com \
    /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).