From: 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: Mon, 6 Jun 2005 17:43:43 +0200 [thread overview]
Message-ID: <1118072623.42a46f2f472fd@imp1-q.free.fr> (raw)
In-Reply-To: <42A46551.9010707@tls.msk.ru>
Hi,
Selon Michael Tokarev <mjt@tls.msk.ru>:
> matthieu castet wrote:
> > Michael Tokarev wrote:
> >
> In other message, you wrote:
>
> > In your bios, which mode is your parport ?
> >
> > Could you try LPPR mode (or something like that ?)
>
> Are you referring to ECP, EPP, Bi-Di etc modes?
> (note there's serial port too, which has exactly the same prob
> with (re)loading the driver).
>
Yes, but I don't know which LPPR is : there is one mode that use 1 ioport and
the other 2 ioports.
Try EPP ?
> > Have you try the patches ?
>
> Yes, tried the patches you sent last friday - from
> http://bugme.osdl.org/attachment.cgi?id=4504&action=view
> and from your message in this thread with MSGID = 429FF17C.9080902@free.fr
> (this last patch depends on the first). Makes no (visible) difference
> on HP ML 150 box, the same stuff is shown in dmesg, and on reload neither
> parallel nor serial ports works.
>
> I'll try some more experiments later today (hopefully) when my co-workers
> (who are using this box right now so I can't freely reboot it as I wish)
> will go home... ;)
>
try to post
cat /sys/bus/pnp/drivers/parport_pc/*/{options,resources}
and
cat /sys/bus/pnp/drivers/serial/*/{options,resources}
> BTW, looks like 8250_pnp module is also somewhat strange. When loading
> 8250 alone, it detects (at least some) standard serial ports just fine,
> and when loading 8250_pnp, the same port is being "re-detected" again.
> But when unloading 8250_pnp, even when 8250 module is still loaded,
> that only port is disabled. Looks somewhat.. assimetric to me, without
> counting issue with re-enabling of a pnp device.
yes there something strange...
Matthieu
next prev parent reply other threads:[~2005-06-06 23:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 22:24 castet.matthieu
2005-06-03 0:18 ` PNP " Michael Tokarev
2005-06-03 5:58 ` matthieu castet
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 [this message]
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=1118072623.42a46f2f472fd@imp1-q.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
all inboxes | Powered by JetHome®