public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: TimO <hairballmt@mcn.net>
To: Tim Waugh <twaugh@redhat.com>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
	Will Newton <will@misconception.org.uk>,
	Mike Galbraith <mikeg@wen-online.de>,
	linux-kernel@vger.kernel.org
Subject: Re: VIA audio and parport in 2.4.2
Date: Wed, 21 Mar 2001 19:41:15 -0700	[thread overview]
Message-ID: <3AB9664B.10451E6D@mcn.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0103211333440.1541-100000@dogfox.localdomain> <3AB8B877.D36E8719@mandrakesoft.com> <20010321144907.D1323@redhat.com>

Tim Waugh wrote:
> 
> On Wed, Mar 21, 2001 at 09:19:35AM -0500, Jeff Garzik wrote:
> 
> > Attempting to pretend that the parallel port is not in an interrupt
> > driven mode by passing irq=none is folly.
> 
> No, that's not what it's for.  It means 'for Christ sake don't use
> interrupts, I know what I'm doing'.
> 
> > If irq=none is passed to tell the Via code to -force- the parallel
> > port into a non-irq-driven mode is one thing.  If irq=none is passed
> > to hide a problem with spurious interrupts, we need to fix that
> > problem, not hide it.
> 
> irq=none is passed in order to diagnose whether a problem happens on
> only the interrupt-driven path or not.  Read the trouble-shooting
> section parport.txt.  Understand that there are lots of printing code
> paths nowadays (polling, interrupt-driven, PIO, DMA, etc).
> 
> > I still am not convinced that irq=<anything> should affect the Via
> > code at all.  Maybe I can print out a message "irq=foo ignored".
> 
> Jeff, it needs to.  If you want to make irq=auto the default
> (currently it's 'probe only'), then that is an entirely different
> thing.
> 
> When the user tells you not to use interrupts, you'd better not.
> 
> > Optionally, I could handle irq=none by force-disabling the parallel
> > port's interrupt driven modes, if they are active.
> 
> What the hell for?  Just don't use the interrupts.
> 
> Tim.
> */
> 

Hi, Tim

What is the default anyway?  My BIOS is 0x378, 7, 3 and the driver
reports this:

0x378: FIFO is 16 bytes
0x378: writeIntrThreshold is 8
0x378: readIntrThreshold is 8
0x378: PWord is 8 bits
0x378: Interrupts are ISA-Pulses
0x378: possible IRQ conflict!       [Don't know why it always reports
this]
0x378: ECP port cfgA=0x10 cfgB=0x00
0x378: ECP settings irq=<none or set by other means> dma=<none or set by
other means>
parport0: PC-style at 0x378 (0x778), irq 7, using FIFO
[PCSPP,TRISTATE,COMPAT,ECP]
parport0: cpp_daisy: aa5500ff(98)
parport0: assign_addrs: aa5500ff(98)
parport0: cpp_daisy: aa5500ff(98)
parport0: assign_addrs: aa5500ff(98)

With no options in modules.conf, lp0 uses polling; with irq=auto
dma=auto
it uses interrupt-driven but no dma?.

-- 
===============
-- Tim

  reply	other threads:[~2001-03-22  2:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-15 18:45 VIA audio and parport in 2.4.2 Will Newton
2001-03-16 10:53 ` Tim Waugh
2001-03-16 14:53   ` Will Newton
2001-03-17  7:09     ` Mike Galbraith
2001-03-17 17:46       ` Will Newton
2001-03-17 19:13         ` Mike Galbraith
2001-03-19  0:16           ` Will Newton
2001-03-19  0:22             ` Tim Waugh
2001-03-21  4:21               ` Jeff Garzik
2001-03-21 10:04                 ` Tim Waugh
2001-03-21 13:37                 ` Will Newton
2001-03-21 14:19                   ` Jeff Garzik
2001-03-21 14:49                     ` Tim Waugh
2001-03-22  2:41                       ` TimO [this message]
2001-03-27 18:21                         ` Tim Waugh

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=3AB9664B.10451E6D@mcn.net \
    --to=hairballmt@mcn.net \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikeg@wen-online.de \
    --cc=twaugh@redhat.com \
    --cc=will@misconception.org.uk \
    /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