From: ambx1@neo.rr.com (Adam Belay)
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: Matthieu Castet <castet.matthieu@free.fr>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.9+] PnPBIOS: Missing SMALL_TAG_ENDDEP tag
Date: Sun, 5 Dec 2004 21:42:19 -0500 [thread overview]
Message-ID: <20041206024218.GD3103@neo.rr.com> (raw)
In-Reply-To: <41B3A963.4090003@keyaccess.nl>
On Mon, Dec 06, 2004 at 01:35:47AM +0100, Rene Herman wrote:
> Hi Adam.
>
> Between 2.6.8 and 2.6.9, the following patch to rsparser.c was merged:
>
> http://linus.bkbits.net:8080/linux-2.5/cset@414703f7MEe33PTYY-aFQaM3CLKjZw?nav=index.html|src/|src/drivers|src/drivers/pnp|src/drivers/pnp/pnpbios|related/drivers/pnp/pnpbios/rsparser.c
>
> The added warning triggers on my machine:
>
> Linux Plug and Play Support v0.97 (c) Adam Belay
> PnPBIOS: Scanning system for PnP BIOS support...
> PnPBIOS: Found PnP BIOS installation structure at 0xc00f7740
> PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0x6634, dseg 0xf0000
> PnPBIOS: Missing SMALL_TAG_ENDDEP tag
> PnPBIOS: Missing SMALL_TAG_ENDDEP tag
> PnPBIOS: Missing SMALL_TAG_ENDDEP tag
> PnPBIOS: Missing SMALL_TAG_ENDDEP tag
> PnPBIOS: 13 nodes reported by PnP BIOS; 13 recorded by driver
>
> I don't believe those warnings should be printed, what with "broken" the
> expected state of anything coming from the BIOS. The attached patch
> removes them again. Works for me...
>
> Rene.
Hi Rene,
Could you please send me "pnp.tar" from something like this:
mkdir /tmp/pnp; cp /proc/bus/pnp/[0-f][0-f] /tmp/pnp; tar -cf pnp.tar /tmp/pnp; rm -fR /tmp/pnp
make sure the pnpbios /proc interface is compiled into the kernel.
I'd like to look at the node data to see what's going on.
Thanks,
Adam
next prev parent reply other threads:[~2004-12-06 2:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 0:35 [2.6.9+] PnPBIOS: Missing SMALL_TAG_ENDDEP tag Rene Herman
2004-12-06 0:46 ` matthieu castet
2004-12-06 1:04 ` Rene Herman
2004-12-06 2:42 ` Adam Belay [this message]
2004-12-06 3:06 ` Rene Herman
2004-12-06 16:59 ` Adam Belay
2004-12-06 21:04 ` Rene Herman
2004-12-07 0:03 ` Adam Belay
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=20041206024218.GD3103@neo.rr.com \
--to=ambx1@neo.rr.com \
--cc=castet.matthieu@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.herman@keyaccess.nl \
/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