public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Markus Koßmann" <mkossmann_ml1@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: parallel port problems with 2.6.21_rc5 and 2.6.21_rc6_git3-20070410174235
Date: Sun, 13 May 2007 15:12:01 -0700	[thread overview]
Message-ID: <20070513151201.f2b38720.randy.dunlap@oracle.com> (raw)
In-Reply-To: <200705051658.22817.mkossmann_ml1@gmx.de>

On Sat, 5 May 2007 16:58:22 +0200 Markus Koßmann wrote:

> Am Donnerstag, 3. Mai 2007 schrieb Randy Dunlap:
> > On Wed, 11 Apr 2007 20:40:23 +0200 Markus Koßmann wrote:
> > > When using either the unpatched  2.6.21_rc5   or SUSEs patched
> > > 2.6.21_rc6_git3-20070410174235 on a SUSE-10.2 x86_64 system the parallel
> > > port doesn't work right. If I "cat some_asciifile >/dev/lp0"  the output
> > > on my Epson Stylus Color 880 is unreadable.  "cat /dev/zero >/dev/lp0" 
> > > creates random characters on the paper. Printing using cups also doesn't
> > > work any more.
> > > Switching back to SUSEs  2.6.18.8-0.1 kernel fixes the problem.
> > > Any Ideas, what might be broken here ?
> >
> > Nope, but I have the same problem.
> > I'll dig into it some day, but it's not very high priority for me.
> >
> > I haven't tested it lately.  Do you still see this problem?
> >
> Yes, it still exists with SUSEs  2.6.21-20070502152652 kernel. Didn't check 
> with vanilla 2.6.21 yet. 

Hi Markus,

I just retested this on 2.6.21-git12 and didn't have a problem
with printing.  Can you test on 2.6.22-rc1?


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2007-05-13 22:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-11 18:40 parallel port problems with 2.6.21_rc5 and 2.6.21_rc6_git3-20070410174235 Markus Koßmann
2007-05-03 20:25 ` Randy Dunlap
2007-05-05 14:58   ` Markus Koßmann
2007-05-13 22:12     ` Randy Dunlap [this message]
2007-05-14 18:28       ` Markus Koßmann
2007-05-06 23:09   ` Bill Davidsen

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=20070513151201.f2b38720.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkossmann_ml1@gmx.de \
    /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