From: Brad Douglas <brad@neruo.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: alan@lxorguk.ukuu.org.uk, dax@gurulabs.com, linux-kernel@vger.kernel.org
Subject: Re: APM oops with Dell 5000e laptop
Date: 18 Nov 2000 02:57:16 +0800 [thread overview]
Message-ID: <20001117192856Z129664-28370+57@vger.kernel.org> (raw)
In-Reply-To: <E13wj4s-0000U0-00@the-village.bc.nu>
> > 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?
>
> The ideal approach is to ident and version id the compal bios. The DMI tables
> can include more useful BIOS info but rarely do (you might want to dump all the
> DMI tables in your box and see if you have a BIOS vendor/version)
The BIOS revisions seem to match up, but there are already multiple versions of the BIOS for this machine already, so I initially discounted that method. It also means a bit of upkeep, too.
I was really hoping for a "set it and forget it" approach, but that doesn't seem possible.
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/
prev parent reply other threads:[~2000-11-17 19:29 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
2000-11-17 10:49 ` Alan Cox
2000-11-17 18:57 ` Brad Douglas [this message]
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=20001117192856Z129664-28370+57@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®