mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Meelis Roos <mroos@linux.ee>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: PnPBIOS: Unknown tag '0x82'
Date: Mon, 22 Mar 2004 19:47:21 +0200 (EET)	[thread overview]
Message-ID: <Pine.GSO.4.44.0403221937330.18189-100000@math.ut.ee> (raw)

Since the beginning of its existence, the pnpbios driver talks about
unknown tag '0x82' on one of my computers. The computer has Intel
D815EEA2 mainboard, BIOS has been updated quite recently. I added the
tag dump to printout and here it is:

PnPBIOS: Unknown tag '0x82', length '18': 82 12 00 49 6e 74 65 6c 20 46 69 72 6d 77 61 72 65 20

This 0x82 0x12 0x00 and then 'Intel Firmware'.

Anything to worry about? Are the next tags still correctly parsed? The
full dmesg is now

PnPBIOS: Scanning system for PnP BIOS support...
PnPBIOS: Found PnP BIOS installation structure at 0xc00f2480
PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0x1d2a, dseg 0xf0000
pnp: 00:09: ioport range 0x4d0-0x4d1 has been reserved
pnp: 00:09: ioport range 0xcf8-0xcff could not be reserved
PnPBIOS: Unknown tag '0x82', length '18': 82 12 00 49 6e 74 65 6c 20 46 69 72 6d 77 61 72 65 20 .
pnp: 00:0b: ioport range 0x800-0x87f has been reserved
PnPBIOS: 20 nodes reported by PnP BIOS; 20 recorded by driver

-- 
Meelis Roos (mroos@linux.ee)



             reply	other threads:[~2004-03-22 17:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-22 17:47 Meelis Roos [this message]
2004-03-22 16:02 ` Adam Belay
2004-03-23  9:50   ` Meelis Roos
2004-03-24 16:29     ` Adam Belay
     [not found]       ` <Pine.GSO.4.44.0403251316210.6391-100000@math.ut.ee>
2004-03-26 23:54         ` Adam Belay
  -- strict thread matches above, loose matches on Subject: below --
2003-08-15 14:49 Meelis Roos

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=Pine.GSO.4.44.0403221937330.18189-100000@math.ut.ee \
    --to=mroos@linux.ee \
    --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®