From: Chuck Ebbert <cebbert@redhat.com>
To: Juan Antonio Martinez <jonsito@teleline.es>
Cc: linux-kernel@vger.kernel.org, Adrian Bunk <bunk@stusta.de>
Subject: Re: ppdev - libieee1284.so conflicts with 2.6.21
Date: Tue, 03 Jul 2007 17:31:03 -0400 [thread overview]
Message-ID: <468AC017.2000300@redhat.com> (raw)
In-Reply-To: <1183443365.3006.10.camel@drake.micasa.es>
On 07/03/2007 02:16 AM, Juan Antonio Martinez wrote:
> Attached 3 reports:
> 2.6.21 with noisapnp pnpacpi=off
> 2.6.21 without extra options
> 2.6.20
>
> I apologize for sending reports with fedora (not vanilla) kernels. I
> have not enought time to recompile and test
>
> By diffin'g reports, I've found these significant ( to me) difference in
> 2.6.20:
>
> < ppdev0: registered pardevice
> < ppdev0: negotiated back to compatibility mode because user-space
> forgot
> < ppdev0: unregistered pardevice
When it is working it says:
ppdev: user-space parallel port driver
ppdev0: registered pardevice
ppdev0: unregistered pardevice
ppdev0: registered pardevice
ppdev0: negotiated back to compatibility mode because user-space forgot
ppdev0: unregistered pardevice
ppdev0: registered pardevice
ppdev0: unregistered pardevice
When broken:
ppdev: user-space parallel port driver
ppdev0: registered pardevice
ppdev0: unregistered pardevice
I give up, what causes that?
next prev parent reply other threads:[~2007-07-03 21:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 6:16 ppdev - libieee1284.so conflicts with 2.6.21 Juan Antonio Martinez
2007-07-03 21:31 ` Chuck Ebbert [this message]
2007-07-04 11:58 ` Jonsito
2007-08-14 11:15 ` RV: ppdev - libieee1284.so conflicts with 2.6.2{0,1,2} Jonsito
-- strict thread matches above, loose matches on Subject: below --
2007-07-02 9:22 ppdev - libieee1284.so conflicts with 2.6.21 Juan Antonio Martinez
2007-07-02 22:47 ` Andrew Morton
2007-07-02 23:12 ` Randy Dunlap
2007-07-03 0:28 ` Adrian Bunk
2007-07-02 23:13 ` Chuck Ebbert
2007-07-03 15:57 ` Juan Antonio Martinez
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=468AC017.2000300@redhat.com \
--to=cebbert@redhat.com \
--cc=bunk@stusta.de \
--cc=jonsito@teleline.es \
--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