10:19 p.m.
Greetings all;
rs-232 tech is getting old, like me.
Do we have a tool that can display graphically in near real time, the status
of the commonly used wires/signals in the '7 wire' protocol?
I need something that works a bit like the old db25 tester with a bunch of
LED's to tally the line states like that gismo Radio Shack sold 20 years ago.
Those blinking leds were a very good troubleshooting tool, and I'm having
flow control problems that look like a system freeze on one end or the other,
but when rz times out, I still get a prompt from the shell on the other end,
but nothing I type here arrives there, like hardware flow is still in effect
and turned off on one end or the other.
Thanks All for any hints.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
There's no future in time travel.
3:29 a.m.
On Fri, 29 Jan 2010 23:19:15 -0500
Gene Heskett <gene.heskett(a)verizon.net> wrote:
Greetings all;
rs-232 tech is getting old, like me.
Do we have a tool that can display graphically in near real time, the status
of the commonly used wires/signals in the '7 wire' protocol?
cat /proc/tty/driver/serial
will give you some info
7:41 a.m.
On 01/29/2010 10:19 PM, Gene Heskett wrote:
Greetings all;
rs-232 tech is getting old, like me.
Do we have a tool that can display graphically in near real time, the status
of the commonly used wires/signals in the '7 wire' protocol?
I need something that works a bit like the old db25 tester with a bunch of
LED's to tally the line states like that gismo Radio Shack sold 20 years ago.
Those blinking leds were a very good troubleshooting tool, and I'm having
flow control problems that look like a system freeze on one end or the other,
but when rz times out, I still get a prompt from the shell on the other end,
but nothing I type here arrives there, like hardware flow is still in effect
and turned off on one end or the other.
Thanks All for any hints.
You can try statserial and see if it will do what you want. It is
even in the repos.
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
4:58 p.m.
On Fri, 2010-01-29 at 23:19 -0500, Gene Heskett wrote:
Greetings all;
rs-232 tech is getting old, like me.
Do we have a tool that can display graphically in near real time, the status
of the commonly used wires/signals in the '7 wire' protocol?
I need something that works a bit like the old db25 tester with a bunch of
LED's to tally the line states like that gismo Radio Shack sold 20 years ago.
Those blinking leds were a very good troubleshooting tool, and I'm having
flow control problems that look like a system freeze on one end or the other,
but when rz times out, I still get a prompt from the shell on the other end,
but nothing I type here arrives there, like hardware flow is still in effect
and turned off on one end or the other.
Thanks All for any hints.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
There's no future in time travel.
It sounds like what you want is a
"breakout box". Here is a link to
one:
http://www.topmicrousa.com/break-1.html
There are others, but this should help you find what you want.
Regards,
Les H
6:25 p.m.
On Saturday 30 January 2010, Les wrote:
On Fri, 2010-01-29 at 23:19 -0500, Gene Heskett wrote:
> Greetings all;
>
> rs-232 tech is getting old, like me.
>
> Do we have a tool that can display graphically in near real time, the
> status of the commonly used wires/signals in the '7 wire' protocol?
>
> I need something that works a bit like the old db25 tester with a bunch
> of LED's to tally the line states like that gismo Radio Shack sold 20
> years ago. Those blinking leds were a very good troubleshooting tool, and
> I'm having flow control problems that look like a system freeze on one
> end or the other, but when rz times out, I still get a prompt from the
> shell on the other end, but nothing I type here arrives there, like
> hardware flow is still in effect and turned off on one end or the other.
>
> Thanks All for any hints.
It sounds like what you want is a "breakout box". Here is a link to
one:
http://www.topmicrousa.com/break-1.html
I finally found one of mine, only about a foot down in the Midden Heap my
pool table has become, and it confirms that the other end is not using any
sort of hardware flow control regardless of the options to do that being set
in the device descriptor. xon/xoff appear to work, but for some unk reason,
the flow rate achieved overall at 19,200 baud, is about 50 baud due to
repeats. If you don't disconnect on rzsz, it will get the file moved,
eventually, with very very heavy emphasis on the eventually. :(
So now I have about 25 pages of assembly code to wander thru, and its
comments aren't always that verbose, so those rarely used codes I have to
look up in the moto programmers manual. This should be fun, not!
Q? This code uses the 'sleep(1)' call to time its repeat scans. It is using
no cpu as its the bottom item on an htop sorted by use report.
I assume I can go into the tarball and change those 2 sleep calls to
sleep(0.05) to get 20 scans a second? I'm going to try it anyway & see if it
will still build.
Thanks Les.
There are others, but this should help you find what you want.
Regards,
Les H
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
To be who one is, is not to be someone else.
7:03 p.m.
On 01/30/2010 06:25 PM, Gene Heskett wrote:
Q? This code uses the 'sleep(1)' call to time its repeat scans. It is using
no cpu as its the bottom item on an htop sorted by use report.
I assume I can go into the tarball and change those 2 sleep calls to
sleep(0.05) to get 20 scans a second? I'm going to try it anyway & see if it
will still build.
Nope - sleep only accepts an integer value. Using sleep, 1 second it
the best you will get.
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
9:39 p.m.
On 01/30/2010 07:03 PM, Mikkel wrote:
On 01/30/2010 06:25 PM, Gene Heskett wrote:
>
> Q? This code uses the 'sleep(1)' call to time its repeat scans. It is using
> no cpu as its the bottom item on an htop sorted by use report.
>
> I assume I can go into the tarball and change those 2 sleep calls to
> sleep(0.05) to get 20 scans a second? I'm going to try it anyway & see if it
> will still build.
>
Nope - sleep only accepts an integer value. Using sleep, 1 second it
the best you will get.
Mikkel
He probably wants usleep() which sleeps for microsecond intervals.
--
Rod
9:44 p.m.
On 01/30/2010 09:39 PM, Rod Haper wrote:
On 01/30/2010 07:03 PM, Mikkel wrote:
> On 01/30/2010 06:25 PM, Gene Heskett wrote:
>>
>> Q? This code uses the 'sleep(1)' call to time its repeat scans. It is
using
>> no cpu as its the bottom item on an htop sorted by use report.
>>
>> I assume I can go into the tarball and change those 2 sleep calls to
>> sleep(0.05) to get 20 scans a second? I'm going to try it anyway & see
if it
>> will still build.
>>
> Nope - sleep only accepts an integer value. Using sleep, 1 second it
> the best you will get.
>
> Mikkel
>
He probably wants usleep() which sleeps for microsecond intervals.
--
Rod
Or better yet nanosleep() which is more portable and up to date.
--
Rod
10:59 p.m.
On Saturday 30 January 2010, Rod Haper wrote:
On 01/30/2010 07:03 PM, Mikkel wrote:
> On 01/30/2010 06:25 PM, Gene Heskett wrote:
>> Q? This code uses the 'sleep(1)' call to time its repeat scans. It is
>> using no cpu as its the bottom item on an htop sorted by use report.
>>
>> I assume I can go into the tarball and change those 2 sleep calls to
>> sleep(0.05) to get 20 scans a second? I'm going to try it anyway & see
>> if it will still build.
>
> Nope - sleep only accepts an integer value. Using sleep, 1 second it
> the best you will get.
>
> Mikkel
He probably wants usleep() which sleeps for microsecond intervals.
--
Rod
Precisely, a usleep(50000) would be much better . And some man page studying
for rpmbuild options. I tried to edit the .c source, but then it refused to
build and that was not the error it spit out. We'll poke at it some more
tomorrow unless I start plowing thru the sources I have for sc6551.asm to
make that driver, for an H63C09 equipt trs-80 Color Computer 3, now running
Nitros9.
Specifically, I need rpmbuild to stop after unpacking and patching the
tarball, giving me a chance to edit the .c file to change that, and then
restart at the next step. I've been through the man page a couple of times,
and how to do that hasn't exactly reached up and slapped me. Hints welcome
of course.
Thanks Rod.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
You will be divorced within a year.
12:19 p.m.
Gene Heskett wrote, On 30 Jan 2010 02:59 PM:
Precisely, a usleep(50000) would be much better . And some man page
studying
for rpmbuild options. I tried to edit the .c source, but then it refused to
build and that was not the error it spit out. We'll poke at it some more
tomorrow unless I start plowing thru the sources I have for sc6551.asm to
make that driver, for an H63C09 equipt trs-80 Color Computer 3, now running
Nitros9.
Specifically, I need rpmbuild to stop after unpacking and patching the
tarball, giving me a chance to edit the .c file to change that, and then
restart at the next step. I've been through the man page a couple of times,
and how to do that hasn't exactly reached up and slapped me. Hints welcome
of course.
Thanks Rod.
In case you have not already come across it...
rpmbuild -bp package.spec
-bp Executes the "%prep" stage from the spec file. Normally this
involves unpacking the sources and applying any patches.
After you make your patch(es) [and put the patches in the SOURCES dir, with appropriate
changes to
the spec file], you will probably want to build an SRPM [ -bs ] then clean out/change your
%_topdir,
install the srpm and make sure it builds as expected. [if you had found the -bs command,
made mods
and tried to continue on with building using rpmbuild you might be a bit frustrated about
now,
because rpmbuild always starts from the SOURCES dir and spec.]
the following seems like a good place for you to start setting up your environment, for
the kind of
work you are proposing:
http://bradthemad.org/tech/notes/patching_rpms.php
related link:
http://magazine.redhat.com/2007/06/04/tips-from-an-rhce-building-rpms-wit...
If you want to follow all the fedora rules, then you should probably start setting up
your
environment IAW:
http://fedoraproject.org/wiki/How_to_create_an_RPM_package
http://fedoraproject.org/wiki/How_to_create_an_RPM_package#Setting_up_you...
http://fedoraproject.org/wiki/How_to_create_an_RPM_package#.25prep_sectio...
Hope you find this helpful.
--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter
10:49 p.m.
On Saturday 30 January 2010, Mikkel wrote:
On 01/30/2010 06:25 PM, Gene Heskett wrote:
> Q? This code uses the 'sleep(1)' call to time its repeat scans. It is
> using no cpu as its the bottom item on an htop sorted by use report.
>
> I assume I can go into the tarball and change those 2 sleep calls to
> sleep(0.05) to get 20 scans a second? I'm going to try it anyway & see
> if it will still build.
Nope - sleep only accepts an integer value. Using sleep, 1 second it
the best you will get.
Mikkel
Ok, is there some other time waster with a finer resolution that can be
subbed?
Thanks Mikkel.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Type cat vmlinuz > /dev/audio to hear the Voice of God.
4:24 p.m.
Mikkel <mikkel(a)infinity-ltd.com> writes:
Nope - sleep only accepts an integer value. Using sleep, 1 second it
the best you will get.
$ time sleep 0.5
real 0m0.503s
user 0m0.001s
sys 0m0.002s
-wolfgang
--
Wolfgang S. Rupprecht
If the airwaves belong to the public why does the public only get 3
non-overlapping WIFI channels?
4:28 p.m.
On 31 January 2010 22:24, Wolfgang S. Rupprecht
<wolfgang.rupprecht(a)gmail.com> wrote:
Mikkel <mikkel(a)infinity-ltd.com> writes:
> Nope - sleep only accepts an integer value. Using sleep, 1 second it
> the best you will get.
$ time sleep 0.5
real 0m0.503s
user 0m0.001s
sys 0m0.002s
We're talking about the C sleep function...
http://www.opengroup.org/onlinepubs/000095399/functions/sleep.html
--
Sam
5:09 a.m.
Sam Sharpe <lists.redhat(a)samsharpe.net> writes:
On 31 January 2010 22:24, Wolfgang S. Rupprecht
<wolfgang.rupprecht(a)gmail.com> wrote:
>
> Mikkel <mikkel(a)infinity-ltd.com> writes:
>> Nope - sleep only accepts an integer value. Using sleep, 1 second it
>> the best you will get.
>
> $ time sleep 0.5
>
> real 0m0.503s
> user 0m0.001s
> sys 0m0.002s
We're talking about the C sleep function...
http://www.opengroup.org/onlinepubs/000095399/functions/sleep.html
Thanks. I saw a sleep(1) in one of the upstream messages and assumed
they were talking about the "man 1" shell command by the same name
(which used to also be an integer-only command at one time).
-wolfgang
--
Wolfgang S. Rupprecht
If the airwaves belong to the public why does the public only get 3
non-overlapping WIFI channels?
5206
days inactive
5208
days old
13 comments
8 participants
participants (8)
-
Alan Cox -
Gene Heskett -
Howard Howell -
Mikkel -
Rod Haper -
Sam Sharpe -
Todd Denniston -
Wolfgang S. Rupprecht