From: Brad Douglas <brad@neruo.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: dax@gurulabs.com, alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: APM oops with Dell 5000e laptop
Date: 17 Nov 2000 07:40:49 +0800 [thread overview]
Message-ID: <20001117001119Z131557-521+765@vger.kernel.org> (raw)
In-Reply-To: <E13wWoN-0008PC-00@the-village.bc.nu>
> > I do not believe so. I tend to think that detecting these broken models is a waste of kernel code (especially, if there's an effort to correct the problem).
>
> One idea the Dell folks suggested is walking the SMBIOS data table. That happens
> to be something I want to do as its the only good way I know to get
>
> o Cache sizes on older machines
> o The type of monitoring device (lm78 etc) attached
> o slot information
You cannot base this on the Type 1: System Information as a method of identifying the system.
I have in front of me a Dell 5000e and a Compal N30W2, which are the exact same machines. A SMBIOS dump shows different identification information for both machines. In the System Information struct, one says Compal Electronics and the other says Dell Computer Corporation for the manufacturer. The Product Names are also (obviously) different as well.
So far, I have been unable to find anything in the dump that identifies the two machines as the same.
I don't believe doing this just to make a Dell detect properly is the right way to go (regardless of my bias). I think the best we can do build a list of the systems that are the same, but it's certainly not a preferred way.
Any suggestions?
Brad Douglas
brad@neruo.com
brad@tuxtops.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-17 0:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-13 22:34 toshoboe.c typo in linux-2.4.0-test11-pre4 Adam J. Richter
2000-11-13 22:54 ` APM oops with Dell 5000e laptop Dax Kelson
2000-11-13 23:04 ` Brad Douglas
2000-11-16 16:06 ` Alan Cox
2000-11-16 17:59 ` Dax Kelson
2000-11-16 18:17 ` Alan Cox
2000-11-16 21:04 ` John D. Kim
2000-11-16 21:21 ` Barry K. Nathan
2000-11-18 21:02 ` Pavel Machek
2000-11-16 20:08 ` Brad Douglas
2000-11-16 21:43 ` Alan Cox
2000-11-16 23:40 ` Brad Douglas [this message]
2000-11-17 10:49 ` Alan Cox
2000-11-17 18:57 ` Brad Douglas
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=20001117001119Z131557-521+765@vger.kernel.org \
--to=brad@neruo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dax@gurulabs.com \
--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
all inboxes | Powered by JetHome®