From: matthieu castet <castet.matthieu@free.fr>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PNP parallel&serial ports: module reload fails (2.6.11)?
Date: Fri, 03 Jun 2005 07:58:20 +0200 [thread overview]
Message-ID: <429FF17C.9080902@free.fr> (raw)
In-Reply-To: <429FA1F3.9000001@tls.msk.ru>
[-- Attachment #1: Type: text/plain, Size: 1998 bytes --]
Hi Michael,
Michael Tokarev wrote:
> castet.matthieu@free.fr wrote:
>
>> Hi,
>>
>> try pnpacpi=off in your kernel options and it should work.
>> An other solution is to comment pnpacpi_disable_resources in
>> drivers/pnp/pnpacpi/core.c in order to avoid that the resource are
>> disable.
>
>
> Both ways solves this problem for me. Now I can insmod/rmmod
> parport_pc as many times as I want:
>
> parport: PnPBIOS parport detected.
> parport0: PC-style at 0x378, irq 7 [PCSPP]
> pnp: Device 00:0b disabled.
> pnp: Device 00:0b activated.
> parport: PnPBIOS parport detected.
> parport0: PC-style at 0x378, irq 7 [PCSPP]
> pnp: Device 00:0b disabled.
> pnp: Device 00:0b activated.
> parport: PnPBIOS parport detected.
> parport0: PC-style at 0x378, irq 7 [PCSPP]
> ....
>
> BTW, how "stable" pnpacpi=off is? I mean, is it supposed to
> work on more hardware than current default acpi-aware method?
>
pnpacpi=off use the old PNP bios if it is enabled. It seem to work most
of hardware that support it
(some recent acpi-only computer don't).
There could also have conflict if you use acpi and PNPBios together.
>> There was a problem in pnp layer implementation : the resource weren't
>> given in the right order, Adam Belay send me a patch, but I don't know
>> if it got in main-line ?
>
>
> Which patch was that? I can try it here, but can't seem to be able
> to find it...
>
http://bugme.osdl.org/attachment.cgi?id=4504&action=view plus the
attached ones.
>> May be there also a bug in pnpacpi_encode_resources (with the pnp patch
>> apply I didn't still work on some hardware...)
>>
>> You can try to send your dsdt, but I am quit busy for the moment.
>> May be some Intel guy could look at the problem...
>
>
> The DSDTs are at http://www.corpit.ru/mjt/hpml150.dsdt
> and http://www.corpit.ru/mjt/hpml310.dsdt (that's a
> (binary) copy from /proc/acpi/dsdt -- is there a way
> to decode it into some text form?)
>
there is a dissasembler call iasl on intel site.
Matthieu
[-- Attachment #2: pnp.patch --]
[-- Type: text/x-patch, Size: 608 bytes --]
Index: drivers/pnp/resource.c
===================================================================
RCS file: /home/mat/dev/linux-cvs-rep/linux-cvs/drivers/pnp/resource.c,v
retrieving revision 1.21
diff -u -r1.21 resource.c
--- drivers/pnp/resource.c 10 Nov 2004 01:11:02 -0000 1.21
+++ drivers/pnp/resource.c 5 Feb 2005 22:29:34 -0000
@@ -42,7 +42,7 @@
option->priority = priority & 0xff;
/* make sure the priority is valid */
- if (option->priority > PNP_RES_PRIORITY_FUNCTIONAL)
+ if (option->priority > PNP_RES_PRIORITY_INDEPENDENT)
option->priority = PNP_RES_PRIORITY_INVALID;
return option;
[-- Attachment #3: pnp_rsparser.patch --]
[-- Type: text/x-patch, Size: 716 bytes --]
Index: drivers/pnp/pnpacpi/rsparser.c
===================================================================
RCS file: /home/mat/dev/linux-cvs-rep/linux-cvs/drivers/pnp/pnpacpi/rsparser.c,v
retrieving revision 1.2
diff -u -r1.2 rsparser.c
--- drivers/pnp/pnpacpi/rsparser.c 10 Nov 2004 01:11:02 -0000 1.2
+++ drivers/pnp/pnpacpi/rsparser.c 5 Feb 2005 22:01:14 -0000
@@ -506,7 +506,11 @@
parse_data->option = option;
break;
case ACPI_RSTYPE_END_DPF:
- return AE_CTRL_TERMINATE;
+ option = pnp_register_independent_option(dev);
+ if (!option)
+ return AE_ERROR;
+ parse_data->option = option;
+ break;
default:
pnp_warn("PnPACPI:Option type: %d not handle", res->id);
return AE_ERROR;
next prev parent reply other threads:[~2005-06-03 5:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 22:24 Re:PNP parallel&serial ports: module reload fails (2.6.11)? castet.matthieu
2005-06-03 0:18 ` PNP " Michael Tokarev
2005-06-03 5:58 ` matthieu castet [this message]
2005-06-05 10:14 ` matthieu castet
2005-06-05 10:27 ` matthieu castet
2005-06-06 15:01 ` Michael Tokarev
2005-06-06 15:43 ` castet.matthieu
2005-06-06 21:18 ` Adam Belay
2005-06-06 22:43 ` Michael Tokarev
2005-06-08 9:52 ` Adam Belay
2005-06-08 20:29 ` Michael Tokarev
2005-06-08 23:52 ` Adam Belay
2005-06-09 21:07 ` Michael Tokarev
2005-06-09 21:16 ` Russell King
2005-06-10 16:01 ` Bjorn Helgaas
2005-06-10 16:20 ` Dmitry Torokhov
2005-06-10 16:26 ` Bjorn Helgaas
2005-06-10 16:30 ` Russell King
2005-06-14 19:40 ` Adam Belay
-- strict thread matches above, loose matches on Subject: below --
2005-05-31 23:01 Michael Tokarev
2005-06-01 5:04 ` Andrew Morton
2005-06-01 15:20 ` Michael Tokarev
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=429FF17C.9080902@free.fr \
--to=castet.matthieu@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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