From: Sergey Vlasov <vsu@altlinux.ru>
To: Jason Baron <jbaron@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Patch] 2.4.28-pre3 tty/ldisc fixes
Date: Sun, 31 Oct 2004 20:18:14 +0300 [thread overview]
Message-ID: <20041031171814.GA4013@sirius.home> (raw)
In-Reply-To: <20041030191955.GA2310@sirius.home>
[-- Attachment #1: Type: text/plain, Size: 2238 bytes --]
On Sat, Oct 30, 2004 at 11:19:55PM +0400, Sergey Vlasov wrote:
> On Fri, Oct 29, 2004 at 02:29:43PM -0400, Jason Baron wrote:
> > Here's an updated 2.4 tty patch. I'm not sure if the updated patch would
> > fix the above issue, but it has a lot of changes so it might be worth a
> > try.
>
> This looks better - at least the system boots without hang or oops ;)
However, this seems to break SieFS 0.2
(http://mirror01.users.i.com.ua/~dmitry_z/siefs/; 0.4 is broken with
Siemens x55 models): even "slink i" does not work:
ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, {c_iflags=0x5, c_oflags=0, c_cflags=0xebe, c_lflags=0, c_line=0, c_cc[VMIN]=0, c_cc[VTIME]=2, c_cc="\x00\x00\x00\x00\x00\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00"}) = 0
ioctl(3, SNDCTL_TMR_START or TCSETS, {c_iflags=0x5, c_oflags=0, c_cflags=0x1eb1, c_lflags=0, c_line=0, c_cc[VMIN]=0, c_cc[VTIME]=2, c_cc="\x00\x00\x00\x00\x00\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00"}) = 0
ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, {c_iflags=0x5, c_oflags=0, c_cflags=0x1eb1, c_lflags=0, c_line=0, c_cc[VMIN]=0, c_cc[VTIME]=2, c_cc="\x00\x00\x00\x00\x00\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00"}) = 0
ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, {c_iflags=0x5, c_oflags=0, c_cflags=0x1eb1, c_lflags=0, c_line=0, c_cc[VMIN]=0, c_cc[VTIME]=2, c_cc="\x00\x00\x00\x00\x00\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00"}) = 0
ioctl(3, SNDCTL_TMR_START or TCSETS, {c_iflags=0x5, c_oflags=0, c_cflags=0x1eb1, c_lflags=0, c_line=0, c_cc[VMIN]=0, c_cc[VTIME]=3, c_cc="\x00\x00\x00\x00\x00\x03\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00"}) = 0
ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, {c_iflags=0x5, c_oflags=0, c_cflags=0x1eb1, c_lflags=0, c_line=0, c_cc[VMIN]=0, c_cc[VTIME]=3, c_cc="\x00\x00\x00\x00\x00\x03\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00"}) = 0
write(3, "\2\1\3\24", 4) = 4
read(3, "", 1) = 0
There is no responce to the packet. Without the tty patch SieFS
works; 2.6.9 (where locking fixes are already applied) also works.
The bug might really be in the pl2303 driver (the 2.4 version is
missing some patches which are in 2.6.x). Will try to investigate
this further...
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-10-31 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 17:49 [Patch] 2.4.28-pre3 tty/ldisc fixes Jason Baron
2004-10-28 18:35 ` Sergey Vlasov
2004-10-28 18:42 ` Jason Baron
[not found] ` <Pine.LNX.4.44.0410291426240.13340-200000@dhcp83-105.boston.redhat.com>
2004-10-30 19:19 ` Sergey Vlasov
2004-10-31 9:53 ` Krzysztof Taraszka
2004-11-02 15:02 ` Jason Baron
2004-11-07 20:06 ` Sergey Vlasov
2004-11-07 20:10 ` [PATCH] Update termios to use per tty semaphore (backport from 2.6.x) Sergey Vlasov
2004-11-07 20:13 ` [PATCH] Add back lost call to tty->driver.set_termios Sergey Vlasov
2004-10-31 17:18 ` Sergey Vlasov [this message]
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=20041031171814.GA4013@sirius.home \
--to=vsu@altlinux.ru \
--cc=jbaron@redhat.com \
--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