From: Chiaki <ishikawa@yk.rim.or.jp>
To: Chiaki <ishikawa@yk.rim.or.jp>
Cc: Paul Blazejowski <paulb@blazebox.homeip.net>,
wb <dead_email@nospam.com>, "Justin T. Gibbs" <gibbs@scsiguy.com>,
Patrick Mansfield <patmans@us.ibm.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Badness in device_release at drivers/base/core.c:84
Date: Wed, 13 Aug 2003 11:03:58 +0900 [thread overview]
Message-ID: <3F399C8E.7070109@yk.rim.or.jp> (raw)
In-Reply-To: <3F3138C7.2040404@yk.rim.or.jp>
Chiaki wrote:
>> Kermit was very helpful but due to my inexperience i was not able to get
>> the log due to Linux's box resetting of /dev/ttyS0 when booting, i would
>> get disconnect...
>>
>
> Oh, I forgot some details. You might be able to
> circumvent the problem by
> issueing
> set carrier-watch off
>
> I use the direct-wire connetion with
> a device from a Linux PC's tty port using ckermit and
> so let me check the setup again tomorrow at the office.
Sorry for the delay. Below is the copy of kermit startup file
that I use for talking to a device that does not echo back characters.
I also power-on/off the device while connecting kermit to it, and
I don't think I got kicked off. : so
set carrier-watch off (abbreviated below as set carrier off)
should get you going talking to a linux box via
serial line during booting. (However,
I believe you already captured the necessary log using
uucp suite of tools.)
set line /dev/ttyS0
set speed 38400
set carrier off <- This is key to the disconnect
problem.
set terminal echo local <--- lines below here are for local echo back
set terminal newline on
set terminal cr-display crlf
>> Thanks a lot for suggesting ckermit.
You are very welcome.
From a happy Kermit user.
If you need to ask elaborate ckermit questions,
comp.protocols.kermit.misc is where the original
developers of Kermit hang around.
Happy Hacking,
Ishikawa, Chiaki
--
int main(void){int j=2003;/*(c)2003 cishikawa. */
char t[] ="<CI> @abcdefghijklmnopqrstuvwxyz.,\n\"";
char *i ="g>qtCIuqivb,gCwe\np@.ietCIuqi\"tqkvv is>dnamz";
while(*i)((j+=strchr(t,*i++)-(int)t),(j%=sizeof t-1),
(putchar(t[j])));return 0;}/* under GPL */
next prev parent reply other threads:[~2003-08-13 2:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030801182207.GA3759@blazebox.homeip.net>
2003-08-01 21:44 ` Badness in device_release at drivers/base/core.c:84 Andrew Morton
2003-08-01 23:27 ` Mike Anderson
[not found] ` <20030803015510.GB4696@blazebox.homeip.net>
2003-08-03 2:07 ` Andrew Morton
2003-08-03 21:47 ` Diffie
2003-08-03 21:52 ` Andrew Morton
2003-08-03 22:23 ` Diffie
2003-08-03 22:31 ` Diffie
2003-08-04 16:30 ` Patrick Mansfield
2003-08-04 17:48 ` Paul Blazejowski
2003-08-04 18:26 ` Paul Blazejowski
2003-08-04 18:57 ` Patrick Mansfield
2003-08-04 19:36 ` Justin T. Gibbs
2003-08-05 2:21 ` Paul Blazejowski
2003-08-05 10:20 ` wb
2003-08-05 16:10 ` Ishikawa
2003-08-06 16:58 ` Paul Blazejowski
2003-08-06 17:20 ` Chiaki
2003-08-13 2:03 ` Chiaki [this message]
2003-08-06 16:55 ` Paul Blazejowski
2003-08-05 7:18 ` Paul Blazejowski
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=3F399C8E.7070109@yk.rim.or.jp \
--to=ishikawa@yk.rim.or.jp \
--cc=akpm@osdl.org \
--cc=dead_email@nospam.com \
--cc=gibbs@scsiguy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.com \
--cc=paulb@blazebox.homeip.net \
/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