From: Tim Waugh <twaugh@redhat.com>
To: Will Newton <will@misconception.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VIA audio and parport in 2.4.2
Date: Fri, 16 Mar 2001 10:53:10 +0000 [thread overview]
Message-ID: <20010316105310.G1131@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0103151829040.1581-100000@dogfox.localdomain>
In-Reply-To: <Pine.LNX.4.33.0103151829040.1581-100000@dogfox.localdomain>; from will@misconception.org.uk on Thu, Mar 15, 2001 at 06:45:37PM +0000
[-- Attachment #1: Type: text/plain, Size: 1742 bytes --]
On Thu, Mar 15, 2001 at 06:45:37PM +0000, Will Newton wrote:
> I don't know why it prints it twice.
Looks like the module is getting loaded, then unloaded, then loaded
again. Perhaps because of module autocleaning?
> When printing errors are printed (buffer overrun or something like that,
> it seems RedHat only logs these damn things to console).
Put '*.debug -/var/log/debug' in /etc/syslog.conf and SIGHUP it.
With DMA and PIO debugging messages (especially timeout messages) are
normal and expected. They are still there because DMA and PIO isn't
really widely tested yet.
If you have a Via chipset that provides a parallel port via the PCI
bus, things like IRQ and DMA get used by default. I think this is
also a bug, and shouldn't be done unless 'irq=auto dma=auto' is
supplied to the module.
> Also if I try to disbale interrupt driven printing I get an error:
>
> [root@dogfox log]# /usr/sbin/tunelp /dev/printers/0 -i 0
> tunelp: ioctl: Invalid argument
> /dev/printers/0 using IRQ 7
Yeah, tunelp doesn't work with 2.4 kernels right now. It's on my list
of things to fix. Read Documentation/parport.txt to find out about
how to adjust things like that.
Basically, if you do:
modprobe -r lp parport_pc
modprobe parport_pc irq=none
then parport won't use interrupts.
> The IRQ, DMA, I/O ports etc. are all the same as they are in Windows, but
> in Linux the sound doesn't work and the printer keeps hanging.
For the 'printer hangs' problem, try the latest pre-patch in the
testing directory and let me know if that fixes it.
> I also get spurios interrupts on 7 when the parport is not loaded.
I'm not sure what you mean here. Can you be more specific?
Tim.
*/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-03-16 10:54 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 [this message]
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
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=20010316105310.G1131@redhat.com \
--to=twaugh@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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