All of lore.kernel.org
 help / color / mirror / Atom feed
From: DervishD <raul@pleyades.net>
To: Eva Dominguez <evadom2002@yahoo.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: aditional parallel port problems
Date: Thu, 22 Jul 2004 13:20:56 +0200	[thread overview]
Message-ID: <20040722112056.GD6148@DervishD> (raw)
In-Reply-To: <20040722090106.36880.qmail@web21110.mail.yahoo.com>

    Hi Eva :)

 * Eva Dominguez <evadom2002@yahoo.es> dixit:
>   5. The command "dmesg | grep parport" displays:
> 
>     "parport0: PC-style at 0x378 irq 7 [PCSPP,
> TRISTATE, EPP]" (Is this line telling me the mode of
> the parallel port?? in this case...what does it mean?)
>     "parport1: PC-style at 0x8800 irq 5 [PCSPP,
> TRISTATE, EPP]"
>     "lp0: using parport0 (interrupt-driven)"
>     "lp1: using parport1 (polling)"

    Here I have many VIA chipset PC's, and all of them show the same
problem: the SPP and EPP modes are detected (but only if I give the
proper options, otherwise only SPP works), and ECP is not detected.
The problem is longer to explain properly, but that's more or less.

    I cannot help you (by now...), but I'm trying to isolate and
solve my problem with the help of Dino Klein, and as soon as I have
something, I can contact you.

    Anyway, your card seems to be 'moded' through software, am I
wrong?, so maybe it should work providing in the module options the
io_hi value for the card, so the ECR registers are accessed and you
get ECP. Devices connected to the port shouldn't (IMHO) set the mode
on the port...

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/

  reply	other threads:[~2004-07-22 11:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-22  9:01 aditional parallel port problems Eva Dominguez
2004-07-22 11:20 ` DervishD [this message]
2004-07-22 11:49   ` Eva Dominguez

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=20040722112056.GD6148@DervishD \
    --to=raul@pleyades.net \
    --cc=evadom2002@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.