From: Michael Berger <mikeb1@t-online.de>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Modem connection problems with Kernel 2.6.11-bk1 + bk2
Date: Tue, 08 Mar 2005 20:57:36 +0100 [thread overview]
Message-ID: <422E03B0.9090208@t-online.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 572 bytes --]
Michael Berger wrote:
>Dear LKML
>
>Since Kernel Release 2.6.11-bk1 + bk2 it is not possible to connect in
>to the Internet via a modem connection.
>
>Following message is in my System Log:
>
>> Mar 6 19:02:08 Odin wvdial[3079]: stdin not read/write and $MODEM
>not set Mar 6 19:02:08 Odin pppd[3032]: Connect script failed
>
>
>Kernel 2.6.11 works without any problems. Attached is my config file.
>
>Best regards,
>
>
>-- Michael
-- snip->
Dear LKML
Reverting attached patch fixes my serial modem connection problem.
Best regards,
-- Michael
[-- Attachment #2: b_drivers_serial_8250.c --]
[-- Type: text/plain, Size: 1583 bytes --]
diff -Nru a/drivers/serial/8250.c b/drivers/serial/8250.c
--- a/drivers/serial/8250.c 2005-02-28 08:05:18 -08:00
+++ b/drivers/serial/8250.c 2005-01-24 08:00:57 -08:00
@@ -642,6 +642,7 @@
static void autoconfig_16550a(struct uart_8250_port *up)
{
unsigned char status1, status2;
+ unsigned int iersave;
up->port.type = PORT_16550A;
up->capabilities |= UART_CAP_FIFO;
@@ -736,6 +737,40 @@
up->capabilities |= UART_CAP_AFE | UART_CAP_SLEEP;
return;
}
+
+ /*
+ * Try writing and reading the UART_IER_UUE bit (b6).
+ * If it works, this is probably one of the Xscale platform's
+ * internal UARTs.
+ * We're going to explicitly set the UUE bit to 0 before
+ * trying to write and read a 1 just to make sure it's not
+ * already a 1 and maybe locked there before we even start start.
+ */
+ iersave = serial_in(up, UART_IER);
+ serial_outp(up, UART_IER, iersave & ~UART_IER_UUE);
+ if (!(serial_in(up, UART_IER) & UART_IER_UUE)) {
+ /*
+ * OK it's in a known zero state, try writing and reading
+ * without disturbing the current state of the other bits.
+ */
+ serial_outp(up, UART_IER, iersave | UART_IER_UUE);
+ if (serial_in(up, UART_IER) & UART_IER_UUE) {
+ /*
+ * It's an Xscale.
+ * We'll leave the UART_IER_UUE bit set to 1 (enabled).
+ */
+ DEBUG_AUTOCONF("Xscale ");
+ up->port.type = PORT_XSCALE;
+ return;
+ }
+ } else {
+ /*
+ * If we got here we couldn't force the IER_UUE bit to 0.
+ * Log it and continue.
+ */
+ DEBUG_AUTOCONF("Couldn't force IER_UUE to 0 ");
+ }
+ serial_outp(up, UART_IER, iersave);
}
/*
next reply other threads:[~2005-03-08 20:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 19:57 Michael Berger [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-06 18:20 Modem connection problems with Kernel 2.6.11-bk1 + bk2 Michael Berger
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=422E03B0.9090208@t-online.de \
--to=mikeb1@t-online.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox