public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: "Dr. David Alan Gilbert" <gilbertd@treblig.org>
Cc: erik@hensema.xs4all.nl, linux-kernel@vger.kernel.org
Subject: Re: /proc/pci deprecation?
Date: Sat, 7 Dec 2002 15:46:58 -0200	[thread overview]
Message-ID: <20021207174658.GD10322@conectiva.com.br> (raw)
In-Reply-To: <20021207131559.GA737@gallifrey>

Em Sat, Dec 07, 2002 at 01:15:59PM +0000, Dr. David Alan Gilbert escreveu:
> * Erik Hensema (usenet@hensema.xs4all.nl) wrote:
> > 
> > Every half-decent installer autodetects all PCI devices. AND had lspci
> > installed in the install image.
> 
> Yes, but wait till you find yourself stuck on a weird embedded board
> with a small flash and a serial console and you are trying to debug the
> PCI device you've built.

In this weird embedded board with small flash it'd be lovely to save one
more page (or perhaps more) in the kernel image, no? :-)
 
> Sure in most cases you have lspci (and its friends); but why do people
> want to deprecate a perfectly good tool that occasionally comes in
> useful? (Make it a compile time option sure, remove it - no).

See above. And as you said lspci mostly is available. Remove it or make
it a compile time option, please.

- Arnaldo

  reply	other threads:[~2002-12-07 17:39 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06 23:18 /proc/pci deprecation? Petr Vandrovec
2002-12-07  7:44 ` Willy Tarreau
2002-12-07 13:20   ` Tomas Szepe
2002-12-07 19:03   ` Linus Torvalds
2002-12-08  2:56     ` Patrick Mochel
2002-12-08  4:21       ` Linus Torvalds
2002-12-08 20:56         ` Richard Henderson
2002-12-09  1:54           ` Linus Torvalds
2002-12-09  3:59             ` Patrick Mochel
2002-12-13 12:36               ` kernel isapnp (2.4.20) h-peter recktenwald
2002-12-09 13:35             ` /proc/pci deprecation? Ivan Kokshaysky
2002-12-09 14:11             ` Alan Cox
2002-12-09 17:00               ` Linus Torvalds
2002-12-09 18:29                 ` Alan Cox
2002-12-09 18:11                   ` Linus Torvalds
2002-12-09 18:16                     ` Jeff Garzik
2002-12-10  0:43                     ` Alan Cox
2002-12-10  0:30                       ` Linus Torvalds
2002-12-10  5:57                   ` Eric W. Biederman
2002-12-09 23:27                 ` Vojtech Pavlik
2002-12-09 14:14             ` Alan Cox
2002-12-10 16:42         ` Martin Mares
2002-12-07 12:35 ` Erik Hensema
2002-12-07 13:15   ` Dr. David Alan Gilbert
2002-12-07 17:46     ` Arnaldo Carvalho de Melo [this message]
2002-12-09 19:03       ` Rogier Wolff
2002-12-09 19:08         ` Arnaldo Carvalho de Melo
2002-12-07 13:14 ` Tomas Szepe
2002-12-07 18:52   ` Petr Vandrovec
2002-12-08 12:30     ` Erik Hensema
2002-12-09 10:14       ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2002-12-09 11:00 Nicolas Mailhot
2002-12-09  9:15 Adam J. Richter
2002-12-06 21:13 Patrick Mochel
2002-12-06 22:17 ` Jeff Garzik
2002-12-06 22:13   ` Patrick Mochel
2002-12-07 16:23     ` Krzysztof Halasa
2002-12-07 21:18     ` Kai Henningsen
2002-12-08 20:01       ` Krzysztof Halasa

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=20021207174658.GD10322@conectiva.com.br \
    --to=acme@conectiva.com.br \
    --cc=erik@hensema.xs4all.nl \
    --cc=gilbertd@treblig.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