mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andries.Brouwer@cwi.nl
To: jgarzik@pobox.com, mzyngier@freesurf.fr
Cc: Andries.Brouwer@cwi.nl, aebr@win.tue.nl,
	alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org,
	willy@debian.org
Subject: Re: [PATCH] sysfs stuff for eisa bus [1/3]
Date: Sat, 16 Nov 2002 23:30:45 +0100 (MET)	[thread overview]
Message-ID: <UTC200211162230.gAGMUji20171.aeb@smtp.cwi.nl> (raw)

    From: Jeff Garzik <jgarzik@pobox.com>

    > AB> Yes, lists are fine, but not in the kernel source.

    Unfortunately, I respectfully disagree with Andries.

:-)

    Until drivers/pci/pci.ids list is removed from the kernel source,
    I think we are best served by modelling EISA on PCI as much as
    is reasonable.

That I do not have a strong opinion about, not having much
experience with collecting PCI IDs. (I send them to Vojtech :-))
But really, Jeff, these EISA IDs are a pile of junk.
So many with the same ID describe different hardware.

I like a certain level of quality in the kernel source.
When the kernel prints something it should not be random junk.
"Never mind what the Linux kernel says - that is all just nonsense".

A user space utility with a long list is fine: 70% chance that
it is right, 30% that it is wrong. A user space utility can
print: "with that ID we have seen the following five hardware
descriptions".

Since the kernel does not use these values - they are for
informational purposes only - I would prefer to avoid the
misinformation.

Andries


[In the eisa list we see that ISAAB01 is a "HAYES Smartmodem 1200B".
My ISAAB01 however is a "Hayes Smartmodem 2400B". What do you print?]



             reply	other threads:[~2002-11-16 22:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-16 22:30 Andries.Brouwer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-17 18:08 Andries.Brouwer
2002-11-17 14:52 J.E.J. Bottomley
2002-11-16 13:43 Andries.Brouwer
2002-11-16 15:37 ` Marc Zyngier
2002-11-16 20:57   ` Jeff Garzik
2002-11-16 23:43     ` Alan Cox
2002-11-17 10:37     ` Marc Zyngier
2002-11-17 14:48       ` Alan Cox
2002-11-10 21:55 Marc Zyngier
2002-11-10 23:32 ` Andries Brouwer
2002-11-10 23:56   ` Jeff Garzik
2002-11-11  8:46   ` Marc Zyngier
2002-11-11 13:08     ` Alan Cox

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=UTC200211162230.gAGMUji20171.aeb@smtp.cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=aebr@win.tue.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mzyngier@freesurf.fr \
    --cc=willy@debian.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

all inboxes | Powered by JetHome®