mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: castet.matthieu@free.fr
To: "Brown, Len" <len.brown@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: RE: pnp and acpi_pnp
Date: Fri,  3 Sep 2004 10:52:03 +0200	[thread overview]
Message-ID: <1094201523.413830b39d44d@imp3-q.free.fr> (raw)
In-Reply-To: <29AC424F54821A4FB5D7CBE081922E40018E14F4@hdsmsx403.hd.intel.com>

Selon "Brown, Len" <len.brown@intel.com>:

> there are PNP id's which should tell exactly what
> the device is.  For the ACPI case, you can dump
> your BIOS with acpidmp and disassemble it with iasl
> to see the PNP-ids.
>
> But Linux doesn't use ACPI's PNP-ids for device
> enumeration -- yet.
>
Ok, thanks.

> >> PNPBIOS should be disabled when ACPI is enabled, and it is a bug that
> >> this is not automatic.
Yes it sould.
Also with 2.6.9 acpi pnp and pnp will conflic :
the new acpi driver drivers/acpi/motherboard.c reserve the motherboard
resources, but if you look at driver/pnp/system.c, there is also a pnp driver
that does the same jobs. So if PNP0c0[12] appear in pnp layer (with pnpbios),
both driver try to allocate the ressource.
Hopefully it cause only warnings.
But it show the problem and the need of unification instead of reimplant things.

> cheers,
> -Len
>
regards
Matthieu

> >-----Original Message-----
> >From: castet.matthieu@free.fr [mailto:castet.matthieu@free.fr]
> >Sent: Thursday, September 02, 2004 7:38 AM
> >To: Brown, Len
> >Cc: linux-kernel@vger.kernel.org
> >Subject: Re: pnp and acpi_pnp
> >
> >Selon Len Brown <len.brown@intel.com>:
> >
> >> Matthieu,
> >> PNPBIOS should be disabled when ACPI is enabled, and it is a bug that
> >> this is not automatic.
> >>
> >> yes, the "Linux PNP" layer is incomplete, and ACPI isn't yet plugged
> >> into that.
> >>
> >> cheers,
> >> -Len
> >>
> >>
> >>
> >
> >
> >Hi,
> >thanks for your reply.
> >
> >What about the fact that acpi pnp don't make the difference
> >between a normal
> >serial port and a ir port ?
> >
> >I hope acpi will be plugged soon in Linux PNP layer.
> >
> >regards,
> >Matthieu
> >
>



       reply	other threads:[~2004-09-03  9:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <29AC424F54821A4FB5D7CBE081922E40018E14F4@hdsmsx403.hd.intel.com>
2004-09-03  8:52 ` castet.matthieu [this message]
     [not found] <566B962EB122634D86E6EE29E83DD808182C46FD@hdsmsx403.hd.intel.com>
2004-09-01  3:39 ` Len Brown
2004-09-02 11:38   ` castet.matthieu
2004-08-29 10:06 castet.matthieu

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=1094201523.413830b39d44d@imp3-q.free.fr \
    --to=castet.matthieu@free.fr \
    --cc=len.brown@intel.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®