From: Paul Fulghum <paulkf@microgate.com>
To: gxatzipavlis@softnet.tuc.gr
Cc: linux-serial@vger.kernel.org
Subject: Re: selfmade serial driver problem with chipset other than VIA
Date: Mon, 19 Dec 2005 21:15:38 -0600 [thread overview]
Message-ID: <43A7775A.7010402@microgate.com> (raw)
In-Reply-To: <32883.147.27.7.175.1135028325.squirrel@147.27.7.175>
gxatzipavlis@softnet.tuc.gr wrote:
>>the driver isn't working in computers with INTEL and
>>NVIDIA chipsets... when ever i call outb from my
>>writer bottomhalf routine the interrupt isn't generated from the
>>hardware(in machines with inter or nvidia chipset).
> ...
> i can't understand what registers to print during boot as alan proposed
> the registers from 0x03f8 - 0x03ff (aka /dev/ttyS0)?
If the Line Control Register (LCR) Divisor Latch Access Bit (DLAB)
is set, then offsets 0 and 1 access the divisor latch instead
of the transmit holding register (THR) and interrupt enable register (IER).
You do not state if you initialize that bit to zero.
If that bit is set, that could prevent the THR empty
interrupt you expect.
--
Paul Fulghum
Microgate Systems, Ltd
next prev parent reply other threads:[~2005-12-20 3:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-19 21:38 selfmade serial driver problem with chipset other than VIA gxatzipavlis
2005-12-20 3:15 ` Paul Fulghum [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-17 14:07 gxatzipavlis
2005-12-20 12:30 gxatzipavlis
2005-12-19 21:42 gxatzipavlis
2005-12-19 22:08 ` linux-os (Dick Johnson)
[not found] <S964780AbVLSPVy/20051219152154Z+1140@vger.kernel.org>
2005-12-19 16:12 ` giorgos xatzipavlis
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=43A7775A.7010402@microgate.com \
--to=paulkf@microgate.com \
--cc=gxatzipavlis@softnet.tuc.gr \
--cc=linux-serial@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.