From: Arkadiusz Miskiewicz <arekm@pld-linux.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Jiri Slaby <jirislaby@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
support@moxa.com.tw
Subject: Re: [PATCH 1/1 -resend] Char: mxser, upgrade to 1.9.1
Date: Wed, 16 Aug 2006 11:27:32 +0200 [thread overview]
Message-ID: <200608161127.32849.arekm@pld-linux.org> (raw)
In-Reply-To: <20060815234512.0d3bc1d7.akpm@osdl.org>
On Wednesday 16 August 2006 08:45, Andrew Morton wrote:
> > > Perhaps we could create an mxser-new.c and offer that in config, plan
> > > to remove mxser.c N months hence?
> >
> > I can test the updated driver with MOXA CP-168U series board if it will
> > compile on 2.6.12.6.
>
> Thanks.
>
> > Unfortunately I can't change kernel to latest one there.
> > Will testing on 2.6.12.6 be enough for you?
[...]
> Perhaps it'll work if you apply the patch to 2.6.18-rc4 then copy the
> patched files over to 2.6.12..
I've copied 2.6.18rc4+1.9.1 update applied to 2.6.12 + applied patch below, started minicom
and tried to write something... at that moment machine blew up - instantly rebooted.
Nothing on serial console unfortunately.
mxser.c from 2.6.18rc4 without proposed 1.9.1 patch works fine (+ problem described
here http://lkml.org/lkml/2005/11/2/175 no longer happens).
--- mxser.c.new.org 2006-08-16 10:50:44.578413363 +0200
+++ mxser.c 2006-08-16 10:54:07.399361546 +0200
@@ -85,7 +85,7 @@
#define RELEVANT_IFLAG(iflag) (iflag & (IGNBRK|BRKINT|IGNPAR|PARMRK|INPCK|\
IXON|IXOFF))
-#define IRQ_T(info) ((info->flags & ASYNC_SHARE_IRQ) ? IRQF_SHARED : IRQF_DISABLED)
+#define IRQ_T(info) ((info->flags & ASYNC_SHARE_IRQ) ? SA_SHIRQ : SA_INTERRUPT)
#define C168_ASIC_ID 1
#define C104_ASIC_ID 2
@@ -1108,7 +1108,8 @@
*/
timeout = jiffies + HZ;
while (!(inb(info->base + UART_LSR) & UART_LSR_TEMT)) {
- schedule_timeout_interruptible(5);
+ set_current_state(TASK_INTERRUPTIBLE);
+ schedule_timeout(5);
if (time_after(jiffies, timeout))
break;
}
@@ -1129,8 +1130,10 @@
info->event = 0;
info->tty = NULL;
if (info->blocked_open) {
- if (info->close_delay)
- schedule_timeout_interruptible(info->close_delay);
+ if (info->close_delay) {
+ set_current_state(TASK_INTERRUPTIBLE);
+ schedule_timeout(info->close_delay);
+ }
wake_up_interruptible(&info->open_wait);
}
@@ -1870,7 +1873,8 @@
#ifdef SERIAL_DEBUG_RS_WAIT_UNTIL_SENT
printk("lsr = %d (jiff=%lu)...", lsr, jiffies);
#endif
- schedule_timeout_interruptible(char_time);
+ set_current_state(TASK_INTERRUPTIBLE);
+ schedule_timeout(char_time);
if (signal_pending(current))
break;
if (timeout && time_after(jiffies, orig_jiffies + timeout))
@@ -2054,7 +2058,7 @@
spin_lock_irqsave(&info->slock, flags);
- recv_room = tty->receive_room;
+ recv_room = tty->ldisc.receive_room(tty);
if ((recv_room == 0) && (!info->ldisc_stop_rx)) {
/* mxser_throttle(tty); */
mxser_stoprx(tty);
--
Arkadiusz Miśkiewicz PLD/Linux Team
arekm / maven.pl http://ftp.pld-linux.org/
next prev parent reply other threads:[~2006-08-16 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 11:00 [PATCH 1/1 -resend] Char: mxser, upgrade to 1.9.1 Jiri Slaby
2006-08-16 5:53 ` Andrew Morton
2006-08-16 6:31 ` Arkadiusz Miskiewicz
2006-08-16 6:45 ` Andrew Morton
2006-08-16 9:27 ` Arkadiusz Miskiewicz [this message]
2006-08-16 9:53 ` Jiri Slaby
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=200608161127.32849.arekm@pld-linux.org \
--to=arekm@pld-linux.org \
--cc=akpm@osdl.org \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=support@moxa.com.tw \
/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.