mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: brad@neruo.com (Brad Douglas)
Cc: dax@gurulabs.com (Dax Kelson),
	alan@lxorguk.ukuu.org.uk (Alan Cox),
	linux-kernel@vger.kernel.org
Subject: Re: APM oops with Dell 5000e laptop
Date: Thu, 16 Nov 2000 21:43:14 +0000 (GMT)	[thread overview]
Message-ID: <E13wWoN-0008PC-00@the-village.bc.nu> (raw)
In-Reply-To: <20001116203922Z129069-521+734@vger.kernel.org> from "Brad Douglas" at Nov 17, 2000 04:08:55 AM

> 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

I have user space code to walk these tables so I have a basis to attack this
in 2.2.19

-
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/

  reply	other threads:[~2000-11-16 22:14 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 [this message]
2000-11-16 23:40           ` Brad Douglas
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=E13wWoN-0008PC-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=brad@neruo.com \
    --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®