From daemon@csg.lbl.gov  Sat Nov  1 04:01:13 1997
From: daemon@csg.lbl.gov
Date: Sat Nov  1 04:01:15 PST 1997
Subject: comp.os.vxworks newsdigest
Comp.Os.Vxworks Daily Digest    Sat Nov  1 04:01:09 PST 1997
        Subject: Re: for the GNU Compiler(x86) and BIOS?
-------------------------------------------------------
Newsgroups: comp.os.vxworks
Subject: Re: for the GNU Compiler(x86) and BIOS?
Date: Fri, 31 Oct 1997 23:24:08 -0700
From: Wes Peters <softweyr@xmission.com>
Organization: Softweyr LLC
Message-ID: <345ACB08.1302BC08@xmission.com>
References: <344C75DC.7A79@khgw.info.samsung.co.kr> <62ik6f$366$1@rosenews.rose.hp.com>
This is a multi-part message in MIME format.
- --------------29631EF0275A155E2124C28E
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Andrew Crabtree wrote:
> >If the compiler is not specific for the Pentium II, I think that it can
> >not use the MMX instruction of Pentium II. If it is right, what is the
> >solution to utilize fully the function of Pentium II?
There is no difference between the MMX instructions on the Pentium and
Pentium II, except the execution speed, of course.
> I believe the latest version of GAS (2.8.x) does understand MMX
> instructions.
> However, there are no x86 compilers that I am aware of that will optimize C
> code to
> use MMX.  Its not just GNU.  If you want to use MMX you will
> need to hand code it.
There is a Pentium-optimized version of GCC-2.7.x, known as pgcc,
available
for FreeBSD and Linux, amongst others.  You may be able to compile pgcc
as
a VxWorks cross-compiler as well.  Rumor has it that GCC 2.8, when
released,
will have better support for Pentium-class processors, although I don't
know
if that includes MMX instruction generation or not.
- --
             "Where am I, and what am I doing in this handbasket?"
Wes Peters
Softweyr LLC
softweyr@xmission.com
http://www.xmission.com/~softweyr
- --------------29631EF0275A155E2124C28E
Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Wes Peters
Content-Disposition: attachment; filename="vcard.vcf"
begin:          vcard
fn:             Wes Peters
n:              Peters;Wes
org:            Softweyr LLC
adr:            4034 Ascot Downs Dr.;;;South Jordan;UT;84095-7100;US
email;internet: softweyr@xmission.com
title:          Director of Hacking
tel;work:       801.269.7246
tel;fax:        801.269.7363
tel;home:       801.280.4077
x-mozilla-cpt:  ;0
x-mozilla-html: FALSE
version:        2.1
end:            vcard
- --------------29631EF0275A155E2124C28E--
---------------------------
End of New-News digest
**********************
From R.Kirnum@dialogic.com  Sat Nov  1 07:12:46 1997
From: "Kirnum, Robert" <R.Kirnum@dialogic.com>
Date: Sat Nov  1 07:12:50 PST 1997
Subject: ARM
--MimeMultipartBoundary
Content-Type: text/plain
Has anyone looked into using ARM and VxWorks?  Will ARM be supported? If
so, will VxWorks use a GNU compiler that supports ARM or compiler
provided by ARM?
________________________________________________________________________
D I A L	Bob Kirnum
_|_|_|O	Project Engineer
_|_|_|G	973-993-3000 Ext. 6589
_|_|_|I	973-993-5916 Fax
_|_|_|C	mailto:R.Kirnum@dialogic.com
Get the Dialogic Edge at http://www.dialogic.com
Dialogic Corp.  /  1515 Rt. 10  /  Parsippany, NJ 07054
________________________________________________________________________
           Did you know . . . that FireWire was developed by Apple?
       . . . that Apple is 150 in the Fortune 500 and Microsoft is 172?
Believe in Macintosh? Check out http://www.evangelist.macaddict.com/
--MimeMultipartBoundary--
From business@mail.t-1net.com  Sun Nov  2 12:07:10 1997
From: business@mail.t-1net.com
Date: Sun Nov  2 12:07:13 PST 1997
Subject: Get Paid To Advertise!
     Hello!
     If you would like to find out how you can get paid to advertise
your own product, service or business on the Internet, please reply
to <megamoneymakers@mail.t-1net.com> and type 'info' in the
subject line.
     If this has been sent to you in error, please accept my apology
and reply to the forementioned address and type 'remove' in the
subject line to be taken off my mailing list.
From warwicke@syd.csa.com.au  Sun Nov  2 18:51:43 1997
From: Warwick Edwards <warwicke@syd.csa.com.au>
Date: Sun Nov  2 18:51:46 PST 1997
Subject: Upgrading to 16Mbyte memory
I believe I may have stuffed up with my last post.  I sent it to
vxwexplo@lbl.gov but I am not a member of the exploder so any replies to the
exploder would not get through to me.  (I don't know how to get on the
exploder.)
So if you replied to my e-mail could you please send your reply to me at
warwicke@syd.csa.com.au.  Thanks.
The problem was that we are upgrading to a card with 32Mbyte memory from cards
with 8Mbytes memory.  I have gone to a vxWorks of 16Mbytes by updating
LOCAL_MEM_SIZE in config.h.  I can access all this memory but as soon as I
try and configure our image to talk to the periferals I find I can't talk
to a serial card.  This serial card uses short IO address mapping.  Even using
the original 8Mbyte version of vxWorks has the same problem.  It seems just
having the extra memory existing on the card is causing the problem.  What do
I have to do to get this to work?  I assume the problem is in vxWorks.
We are using vme 147 cards and I believe the periferal card in question may
only have 16bit addressing.
Warwick Edwards
warwicke@syd.csa.com.au
From daemon@csg.lbl.gov  Mon Nov  3 04:01:55 1997
From: daemon@csg.lbl.gov
Date: Mon Nov  3 04:01:58 PST 1997
Subject: comp.os.vxworks newsdigest
Comp.Os.Vxworks Daily Digest    Mon Nov  3 04:01:52 PST 1997
        Subject: Re: 2000 problem
        Subject: BSP for the MVME2300 board
-------------------------------------------------------
Newsgroups: comp.os.vxworks,comp.realtime,comp.unix.programmer,comp.lang.c,comp.lang.c++
Subject: Re: 2000 problem
Date: 31 Oct 1997 14:32:14 GMT
From: Aegis <aegis@outland.cyberwar.com>
Organization: Cyber Warrior, Inc.
Message-ID: <63cq5e$cgp$1@bandit.cyberwar.com>
References: <62fk8h$mjq@bcarh8ab.bnr.ca>     <34509979.60FFA516@absyss.fr> <1997Oct24.131957.19653@leeds.ac.uk> <345145DA.5EE9@ici.net>
I think we should just write the year 2000 as 19A0.
Aegis
---------------------------
Newsgroups: comp.os.vxworks
Subject: BSP for the MVME2300 board
Date: 2 Nov 1997 16:47:14 GMT
From: Marc Le Roy <le_roy@maheva.localnet>
Organization: Running Linux
Message-ID: <63iaqi$da@maheva.localnet>
I would like to know if anybody uses the MVME2300 board
with PPC 604 @ 300 MHz under vxWorks.
I applied the jumbo3 patch and I followed the procedure
to build the MVME2300 BSP from the MVME2600 BSP, but
when attempting to boot, I get messages saying that
I was trying to run PPC 604 code on a 603 processor!
I suspect that the BSP do not recognize the new 300MHz
PPC604 processor.
Marc.
---------------------------
End of New-News digest
**********************
From ajohnston@rainbow.robins.af.mil  Mon Nov  3 04:46:15 1997
From: "Albert S. Johnston" <ajohnston@rainbow.robins.af.mil>
Date: Mon Nov  3 04:46:18 PST 1997
Subject: used force 2ce cards needed
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
We need to get a hold of a few more 80Mhz 16 Meg ram Force 2ce cards.  If anyone
has any
they would like to sell please email me.
 thanks,
           a. johnston
--MimeMultipartBoundary--
From ddavies@worf.utsci.com  Mon Nov  3 07:55:03 1997
From: ddavies@worf.utsci.com (Douglas Davies)
Date: Mon Nov  3 07:55:06 PST 1997
Subject: remove
remove
From wheat@wg.com  Mon Nov  3 11:12:33 1997
From: Lee Wheat <wheat@wg.com>
Date: Mon Nov  3 11:12:36 PST 1997
Subject: udp packet size limit
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
we're doing a distributed system and use udp for communication between the
clients and the server. we've recently run into a problem sending udp packets
greater than 2K in length. i've searched the symbol file an don't see anything
that looks like a global that we can change to make this size bigger.
does anyone know how to increase this size? we're running tornado 1.0.1 and
targeting the x86 platform.
thanks,
lee wheat
wheat@wg.com
--MimeMultipartBoundary--
From kheck@cs5.dasd.honeywell.com  Mon Nov  3 12:28:39 1997
From: Kevin Heck <kheck@cs5.dasd.honeywell.com>
Date: Mon Nov  3 12:28:42 PST 1997
Subject: sendmsg(), sendto() VxWorks commands
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Does anyone know what the "flags" argument is that is used in
the sendmsg() and sendto() commands?  I'm wondering if there is
a way to prioritize a network message by setting something
these flags to some value.  Thanks, Kevin Heck
--MimeMultipartBoundary--
From baumann@optivus.com  Mon Nov  3 14:46:55 1997
From: baumann@proton.llumc.edu
Date: Mon Nov  3 14:46:58 PST 1997
Subject: Re: sendmsg(), sendto() VxWorks commands
--MimeMultipartBoundary
Content-Type: TEXT/plain; CHARSET=US-ASCII
On  3 Nov, the vxWorks Users Group Exploder wrote:
> Submitted-by kheck@cs5.dasd.honeywell.com  Mon Nov  3 12:28:39 1997
> Submitted-by: Kevin Heck <kheck@cs5.dasd.honeywell.com>
>
> Does anyone know what the "flags" argument is that is used in
> the sendmsg() and sendto() commands?  I'm wondering if there is
> a way to prioritize a network message by setting something
> these flags to some value.  Thanks, Kevin Heck
> --MimeMultipartBoundary--
I am going to assume that the VxWorks stuff is really *really* close to
BSD networking (I've not had a reason to use those flags to date..)
flags is made by or-ing together:
MSG_OOB  Out of Band Data
MSG_DONTROUTE Don't route the packet
--
--
Michael Baumann  Optivus Technology Inc.|Loma Linda University Medical Center
San Bernardino, California. (909)799-8308 |Internet: baumann@llumc.edu
--MimeMultipartBoundary--
From wong@vms.masd.northgrum.com  Mon Nov  3 15:05:09 1997
From: wong@vms.masd.northgrum.com (J. Pierre Wong)
Date: Mon Nov  3 15:05:13 PST 1997
Subject: Compact PCI support
Could anyone please send me a list of tornado/vxWorks supported CompactPCI
processor boards that use any CPU architecture from x86 to whatever?
Thanks,
Pierre Wong
wong@vms.masd.northgrum.com
From antloga@whqvax.picker.com  Mon Nov  3 17:50:00 1997
From: Lou Antloga <antloga@whqvax.picker.com>
Date: Mon Nov  3 17:50:05 PST 1997
Subject: C-interpreter commands
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hello all.
 I am trying to use the C-interpreter command "lkup" inside an =
application C routine. The purpose is to dynamically
determine the address of a module that can be unlaoided and re-laoded =
during  target operation. I nedd to re-spawn
a task with the 'taskSpawn' call, but I cannot use a hard-coded entry pt =
argument.  How do I get the lkup output re-directed to a local variable =
of type FUNCPTR, so I can determine the new entry point of my loaded =
module ?
NOTE: the entry point is uniaquely named, so there is only one address =
returned by lkup.
Thanks,
lou Antloga
--MimeMultipartBoundary--
From david.seltz@wrs.com  Mon Nov  3 19:16:48 1997
From: David Seltz <david.seltz@wrs.com>
Date: Mon Nov  3 19:16:51 PST 1997
Subject: non representable output section in a.out format.
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Hi,
	Has anyone out there seen the GNU linker error "error: final linking fail
".got" non representable output section in a.out format."?  Any one know a
way to get around the error?  Any help would be appreciated.
Dave
****************************************************************
David Seltz                              email: dseltz@wrs.com
Field Application Engineer               phone: 978-453-4100 x56
Wind River Systems                       Fax:   978-453-9834 fax
150 Industrial Ave, East                 www:   http://www.wrs.com
Lowell, MA 01852
****************************************************************
--MimeMultipartBoundary--
From oren@radguard.com  Tue Nov  4 00:12:55 1997
From: Oren Markovitz <oren@radguard.com>
Date: Tue Nov  4 00:12:58 PST 1997
Subject: linker problem
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
The object i am trying to link has two text sections, (text and text1),
when trying to link those sections and assign a fix address to the text
section with -Ttext option the linker assigns the correct address to the
first Text section but leaves the other text section at addr 0.
Has anyone tried to link more then one text section ?
Thanks
Oren
--MimeMultipartBoundary--
From daemon@csg.lbl.gov  Tue Nov  4 04:01:17 1997
From: daemon@csg.lbl.gov
Date: Tue Nov  4 04:01:20 PST 1997
Subject: comp.os.vxworks newsdigest
Comp.Os.Vxworks Daily Digest    Tue Nov  4 04:01:13 PST 1997
        Subject: Bulletin Board
        Subject: Bulletin Board
        Subject: Using only cluster mbufs??
        Subject: Re: 2000 problem
-------------------------------------------------------
Newsgroups: comp.os.vxworks
Subject: Bulletin Board
Date: Sat, 01 Nov 1997 13:03:07 +0800
From: zjchina <zjchina@pub.zhanjiang.gd.cn>
Organization: zjchina
Message-ID: <345AB80B.52D1@pub.zhanjiang.gd.cn>
Reply-To: zjchina@pub.zhanjiang.gd.cn
Bulletin Board
  http://www.china-contact.com
Here is free!
You can exchange business message here.
You can make friends here.
You can announce your website here.
Welcome!
---------------------------
Newsgroups: comp.os.vxworks
Subject: Bulletin Board
Date: Sat, 01 Nov 1997 13:03:12 +0800
From: zjchina <zjchina@pub.zhanjiang.gd.cn>
Organization: zjchina
Message-ID: <345AB810.4AC9@pub.zhanjiang.gd.cn>
Reply-To: zjchina@pub.zhanjiang.gd.cn
Bulletin Board
  http://www.china-contact.com
Here is free!
You can exchange business message here.
You can make friends here.
You can announce your website here.
Welcome!
---------------------------
Newsgroups: comp.protocols.tcp-ip,comp.os.vxworks
Subject: Using only cluster mbufs??
Date: Mon, 03 Nov 1997 15:52:42 -0500
From: "Jerry Freedman,Jr" <Jerome.Freedman@GSC.GTE.com>
Organization: GTE Government Systems
Message-ID: <345E399A.F10@GSC.GTE.com>
Reply-To: Jerome.Freedman@GSC.GTE.com
I am using a port of the BSD stack (VxWorks). For various,
unconventional reasons ( I'll explain via email if you really, really
want to know ) I would like use cluster mbufs for ALL my ip packets,
sending and receiving (most would be forwarded without going up the
stack at all). This really amounts to setting the threshold above which
cluster mbufs are used to an artificially low limit. It looks to me like
this should work ( I know it would we wasteful of memory etc). Are there
any reasons it shouldn't?
                               Jerry Freedman,Jr
                               GTE Gov't Systems
Please respond by email since my news-reader is highly erratic - I often
am forced to use dejanews to post news articles
---------------------------
Newsgroups: comp.os.vxworks,comp.realtime,comp.unix.programmer,comp.lang.c,comp.lang.c++
Subject: Re: 2000 problem
Date: 3 Nov 1997 20:50:46 GMT
From: thornley@visi.com (David Thornley)
Organization: Vector Internet Services, Inc.
Message-ID: <63ldf6$b4e$1@darla.visi.com>
References: <62fk8h$mjq@bcarh8ab.bnr.ca> <345DF05D.3FAF@ici.net> <345DF992.41C6@ptc.com> <345E0BBB.1EAC493E@calfp.co.uk>
In article <345E0BBB.1EAC493E@calfp.co.uk>,
Nick Leaton  <nickle@pauillac> wrote:
>Robert Egan wrote:
>>
>> I think your missing the heart of the 2000 millenium bug, the legacy
>> systems.
>>
>> It is true today that computers have enough dynamic memory and physical
>> storage capacity to render storage efficiency moot, and that processors
>> have cycles to spare. But in the sixties and seventies, when these
>> applications were written, that wasn't the case. On those old systems
>> every bit (let alone byte) counted, and every cpu cycle you could cut
>> was a bonus. In COBOL they even went so far as to pack the numbers 2 to
>> a byte!
>>
I started programming professionally in the mid-70s, and it didn't
seem that the storage capacity was that restricted.  We used two-digit
years for two reasons:  for compatibility with earlier applications,
and because COBOL supported them well.  (COBOL has a method for
getting the current date, in YYMMDD format of course.)
>> The problem is that as capacity was upgraded, the applications weren't.
>> And now time is running out. Just another case of short sighted
>> corporate management worrying more about the next quarter's profit
>> margins than the inevitable crisis. The last company I worked for
>> started upgrading their legacy systems in 1985, and they're now ready
>> for the year 2000. But a lot of their competitors aren't.
>>
The second to last place I worked for started working on it in 1981.
They're not ready yet, but they're closer.
It is likely that somewhere there is a company that doesn't mortgage
its future to get stuff done/out/cheaper now, but I've never worked
at it and I don't think I've interviewed at it.  Capacity is simple to
add, but applications are hard to upgrade.  You've got to go through
programs in detail, tracing the dataflow.  This means tracing the control
flow, which is a thoroughly nontrivial problem on some of the old
systems.  Once you've got everything ready to go, you've got to
replace all the programs effectively simultaneously with changing the
data.  I've done this sort of thing, and it's neither easy nor fun,
and something is bound to go wrong.
>
>The capacity and representation issue is not the problem. Representing
>data
>with 2 digit years is not the issue. The real issue was people who cut
>and pasted
>or re-wrote all the code that used the representation. If it was
>properly
>encapsulated in some functions or procedures you would have an easy job
>of
>changing the functions. You would also have an easier job of finding and
>altering
>the data that uses 2 digit years.
>
Ever done COBOL?  The function support is awfully clumsy.  In most
languages I've used, other than COBOL and some BASICs, it's easy to
substitute access functions for variables.  This doesn't mean it's
done all the time, of course.  If a program was written in 1970,
and its expected lifetime was ten years, tops, there was no reason to
encapsulate the date representation.
There were good reasons for the short expected lifetimes, BTW.  Up
until the 60s, big and complicated programs were written in machine
language (assembler if you were lucky), and the underlying machine
structures had this interesting habit of changing frequently.
Higher-level (read machine-independent) languages became popular in
the sixties, and scalable machine architectures (IBM 360, say) became
popular also.  Both of these relied on the fact that the new machines
were more powerful, in that both of these constituted large performance
hits.  Once these were in place, there was a chance for programs to
last decades.  What nobody actually knew was that programs would last
for decades, since there was no experience to say that a program written
twenty years ago might still be relevant.
You're blaming 1960s and 1970s programmers for not doing things that
are fairly standard in, say, C++ in the late 90s.  I assure you that
with the usual systems available in the 70s, it would have been a lot
easier and more likely to simply use 4-digit years in the first place
rather than to use access functions.
>Extrapolate the same coding policy to other things that Y2K. Its been
>done everywhere.
>
Would you care to tell me about shops that use accessors with hidden
variable representations for everything?  It doesn't sound likely to
me.  It doesn't work at all for I/O, and it doesn't completely solve
the problem for data storage either.  It certainly helps insulate
programmers from data format changes, but it does have costs and
isn't a panacea.
- --
David H. Thornley                        | These opinions are mine.  I
david@thornley.net                       | do give them freely to those
http://www.thornley.net/~thornley/david/ | who run too slowly.
---------------------------
End of New-News digest
**********************
From jshaw_shade@compuserve.com  Tue Nov  4 04:54:45 1997
From: John Shaw <jshaw_shade@compuserve.com>
Date: Tue Nov  4 04:54:49 PST 1997
Subject: Re: C-interpreter commands
--MimeMultipartBoundary
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
Regarding the message:-
> I am trying to use the C-interpreter command "lkup" inside an =3D
>application C routine. The purpose is to dynamically
>determine the address of a module that can be unlaoided and re-laoded =3D=
>during  target operation. I nedd to re-spawn, etc.
>lou Antloga
The unld and reld functions expect a string pointer argument that
names the object file to unload or reload. The argument can also
be a MODULE_ID.
The functions moduleFindByName (char name [ ]) and
moduleFindByNameAndPath (char name [ ], char path [ ]) can be
used to return the MODULE_ID associated with the given file
name and path of a previously loaded object.
Use the moduleShow function from the shell to list currently
loaded object modules.
Below is some code to load a module and find a symbol in
that module. You could adapt this to get the function you want
to spawn:-
/* usrRshd.c - optionally included modules */
/*
DESCRIPTION
This file is used to include the third-party VxWorks Remote Shell Daemon
by both loading the relevant object and calling the function that spawns
the Remote Shell Daemon task.
*/
#ifndef __INCusrRshdc
#define __INCusrRshdc
/* includes */
#include <ioLib.h>
#include <symLib.h>
#include <loadLib.h>
/* externs */
IMPORT SYMTAB_ID sysSymTbl;
STATUS usrRshdLoadObj
        (
        caddr_t vxRshdObj       /* full pathname of object file */
        )
{
        SYM_TYPE junk;
        FUNCPTR  spawnRshd;
        int fd =3D open (vxRshdObj, O_RDONLY, 0);
        int stackSize =3D 0;
        if (fd < 0)
        {
                return (ERROR);
        }
        loadModule (fd, ALL_SYMBOLS);
        close (fd);
        vxRshdObj =3D "_vxRshdInit";      /* function to call in object *=
/
        if (symFindByName (sysSymTbl, vxRshdObj, (char **) &spawnRshd,
&junk) =3D=3D OK)
        {
                return spawnRshd (stackSize);
        }
        return (OK);
}
#endif /* __INCusrRshdc */
John Shaw,
Shade (Computer Services) Limited,
Calne, Wiltshire, England, UK.
jshaw_shade@compuserve.com
john.shaw@shade.co.uk
--MimeMultipartBoundary--
From jbrandt@sadira.gb.nrao.edu  Tue Nov  4 05:24:45 1997
From: jbrandt@sadira.gb.nrao.edu (JOE BRANDT)
Date: Tue Nov  4 05:24:49 PST 1997
Subject: Re: udp packet size limit
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
You can change the defaults by setting the global variables:
unsigned long udp_sendspace;
unsigned long udp_recvspace;
If you have source you can change the values directly in udp_usrreq.c.
Another approach would be to set the value in usrNetInit() or the like.
A third approach is to set the values in a startup script:
udp_sendspace=8192
udp_recvspace=8192
Thank goodness for global variables!
------------------------------------------------------------------------
    _/       _/   _/_/_/_/       _/           _/_/_/     National
   _/ _/    _/   _/      _/    _/ _/        _/     _/    Radio
  _/   _/  _/   _/_/_/_/      _/____/      _/     _/     Astronomy
 _/     _/_/   _/      _/    _/     _/    _/     _/      Observatory
_/       _/   _/        _/  _/       _/    _/_/_/        Green Bank, WV
Joe Brandt (N0NYO) N.R. EMT/FF          jbrandt@nrao.edu (304)456-2210
------------------------------------------------------------------------
--MimeMultipartBoundary--
From cgrames@mdc.com  Tue Nov  4 06:50:30 1997
From: Charlie Grames <cgrames@mdc.com>
Date: Tue Nov  4 06:50:33 PST 1997
Subject: udp packet size limit -Reply
--MimeMultipartBoundary
Content-Type: text/plain
Content-Disposition: inline
Lee,
Use the setsockopt() call to increase the receive or send buffer sizes.  The calls might look
something like this:
    sockSize = UDPIP_HDR + msgSize;
    setsockopt(sockFd,SOL_SOCKET,SO_RCVBUF,(char *)&sockSize,sizeof(sockSize));
    sockSize = msgSize;
    setsockopt(sockFd,SOL_SOCKET,SO_SNDBUF,(char *)&sockSize,sizeof(sockSize));
It's probably a good idea to check return status, even though I did not show it here.  Note that when
setting the receive buffer size, you must allow for the size of the IP and UDP headers (typically 28
bytes).  You do not need to allow for the headers when setting the send buffer size.
There is also a possible bug in the IP stack that limits message sizes (including IP and UDP
headers) to 32767 bytes.  Refer to TSR 45230.
Hope this helps.
Charlie Grames
The Boeing Company
(314) 233-1956
Charles.R.Grames@boeing.com
>>> the vxWorks Users Group Exploder <vxwexplo@lbl.gov> 11/03/97 01:12pm >>>
Submitted-by wheat@wg.com  Mon Nov  3 11:12:33 1997
Submitted-by: Lee Wheat <wheat@wg.com>
we're doing a distributed system and use udp for communication between the
clients and the server. we've recently run into a problem sending udp packets
greater than 2K in length. i've searched the symbol file an don't see anything
that looks like a global that we can change to make this size bigger.
does anyone know how to increase this size? we're running tornado 1.0.1 and
targeting the x86 platform.
thanks,
lee wheat
wheat@wg.com
--MimeMultipartBoundary--
From cgrames@mdc.com  Tue Nov  4 06:54:12 1997
From: Charlie Grames <cgrames@mdc.com>
Date: Tue Nov  4 06:54:15 PST 1997
Subject: C-interpreter commands -Reply
--MimeMultipartBoundary
Content-Type: text/plain
Content-Disposition: inline
Lou,
Take a look at the routine symFindByName.  It returns the information you are looking for in a
useable format.
Charlie Grames
The Boeing Company
(314) 233-1956
Charles.R.Grames@boeing.com
>>> the vxWorks Users Group Exploder <vxwexplo@lbl.gov> 11/03/97 07:50pm >>>
Submitted-by antloga@whqvax.picker.com  Mon Nov  3 17:50:00 1997
Submitted-by: Lou Antloga <antloga@whqvax.picker.com>
Hello all.
 I am trying to use the C-interpreter command "lkup" inside an =
application C routine. The purpose is to dynamically
determine the address of a module that can be unlaoided and re-laoded =
during  target operation. I nedd to re-spawn
a task with the 'taskSpawn' call, but I cannot use a hard-coded entry pt =
argument.  How do I get the lkup output re-directed to a local variable =
of type FUNCPTR, so I can determine the new entry point of my loaded =
module ?
NOTE: the entry point is uniaquely named, so there is only one address =
returned by lkup.
Thanks,
lou Antloga
--MimeMultipartBoundary--
From espin@idiom.com  Tue Nov  4 07:54:54 1997
From: Geoffrey Espin <espin@idiom.com>
Date: Tue Nov  4 07:54:58 PST 1997
Subject: PPP on Solaris 5.5.1
--MimeMultipartBoundary
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Folks,
Has anyone got any tips for running PPP directly (hard-wired) from a Sun
to a VxWorks target (Ultra603 PPC)?  I hooked up via a Livingston PortMaster
and that worked without the slightest hitch.  But I still want to
configure my Sun Solaris 5.5.1 system.
I've done everything according the the PPP Cookbook.
    http://ddi.digital.net/~dcb/ppp.html
Here are some clues, perhaps:
% tail /var/adm/log/asppp.log
...
15:15:12 Link manager (90) started 10/23/97
15:15:12 parse_config_file: Successful configuration
15:15:16 process_ipd_msg: ipdptp0 needs connection
conn(ppp_user)
Call Failed: SYSTEM NOT IN Systems FILE
15:21:32 get_fifo_msg: can't find path with peer_system_name root
15:42:21 Link manager (90) exited 10/23/97
...
I'm puzzled by the ipdptp0 and Systems messages.
% netstat -rn
192.168.100.126      192.168.100.125       UH       2      0  ipdptp0
% ifconfig -a
le0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
        inet 192.168.100.69 netmask ffffff00 broadcast 192.168.100.255
        ether 8:0:20:73:d6:1a
ipdptp0: flags=8d1<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 8232
        inet 192.168.100.125 --> 192.168.100.126 netmask ffffff00
        ether 0:0:0:0:0:0
...
I don't have anything in my /etc/uucp/Systems file, need I?
On the VxWorks side all is configured "out of the box" and
verified with the PortMaster.  I tip'd cuaa and saw what
looks like 5 (?) PPP requests eminating from VxWorks (38400):
% tip cuaa
connected
 ~}#@!}!>} }2}!}$}%\}%}&} } 6}9}'}"}(}"bc~~}#@!}!>} }2}!}$}%\}%}&} } 6}9}'}"}(}"
bc~~}#@!}!>} }2}!}$}%\}%}&} } 6}9}'}"}(}"bc~~}#@!}!>} }2}!}$}%\}%}&} } 6}9}'}"}(
}"bc~~}#@!}!>} }2}!}$}%\}%}&} } 6}9}'}"}(}"bc~~}#@!}%?} }$d]
Any ideas?  Thanks in advance,
Geoff
--
Geoffrey Espin espin@idiom.com
--MimeMultipartBoundary--
From ajay@mailhost.avici.com  Tue Nov  4 08:44:26 1997
From: Ajay Kachrani <ajay@mailhost.avici.com>
Date: Tue Nov  4 08:44:30 PST 1997
Subject: Re: udp packet size limit
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
At 11:12 AM 11/3/97 PST, the vxWorks Users Group Exploder wrote:
>Submitted-by wheat@wg.com  Mon Nov  3 11:12:33 1997
>Submitted-by: Lee Wheat <wheat@wg.com>
>
>--MimeMultipartBoundary
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
>we're doing a distributed system and use udp for communication between the
>clients and the server. we've recently run into a problem sending udp packets
>greater than 2K in length. i've searched the symbol file an don't see
anything
>that looks like a global that we can change to make this size bigger.
>
>does anyone know how to increase this size? we're running tornado 1.0.1 and
>targeting the x86 platform.
>
Use socket option "SO_SNDBUF" to change the default "2k" buffer size for
output (and "SO_RCVBUF" for input).
--Ajay
===========================================================
Ajay Kachrani
ajay@avici.com
Tel:(978)250-3344 x239
http://www.avici.com
--MimeMultipartBoundary--
From johan.bostedt@styrex.se  Tue Nov  4 09:46:03 1997
From: johan.bostedt@styrex.se
Date: Tue Nov  4 09:46:06 PST 1997
Subject: RE: udp packet size limit
Lee Wheat writes:
"we're doing a distributed system and use udp for communication between the
clients and the server. we've recently run into a problem sending udp packets
greater than 2K in length. i've searched the symbol file an don't see anything
that looks like a global that we can change to make this size bigger.
does anyone know how to increase this size? we're running tornado 1.0.1 and
targeting the x86 platform."
The limitation is restricted to broadcast transmission and is 1472 bytes.
/Regards
Johan Bostedt, Styrex AB
----------------------------------------------------------------------------
Johan Bostedt		Email: johan.bostedt@styrex.se
Styrex AB		Tel:    018-24 22 50
Box 23033		Mobil: 070-592 99 99
750 23 Uppsala		Fax:   018-24 22 80
From intrepid!eci-cec.com!bellafai@uunet.uu.net  Tue Nov  4 11:14:05 1997
From: Andy Bellafaire <bellafai@eci-cec.com>
Date: Tue Nov  4 11:14:09 PST 1997
Subject: DEC 21140 Hangup During Filter Frame Send
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
We're building systems running 25 of Vi's powerPC 604 Power4b boards over two
VME busses.  These cards use the Motorola MPC106 PCI bridge chip.
We're having a problem with the DC-21140 chip hanging during initialization
The chip hangs up sporadically when the processor sends it the filter frame
setup descriptor.  The driver sets the OWN bit for the chip to take the
descriptor and starts the transmit process, but the chip never relinquishes the
descriptor back to the processor.
I've limitied the initialization wait loops to to prevent the processor from
hanging up and dumped the DC chip CSRs to a safe area in memory before init,
before the filter frame transmit and just after the attempt to send the frame.
The CSR dumps indicate that the chip comes out of reset the same when it fails
as when it works.
When it fails, the dump just before and after the transmit indicates a stopped
receive process and a receive state of 1 (which is "Running - Fetching
receive descriptor").
When it works, the dump just before the transmit indicates a stopped receive
process and usually a receive state of 6 (which is "Running - Flushing the
current fram from the receive FIFO because of unavailable receive buffer.  The
other times when it works, the receive state just before the transmit is 4
("Suspended - Unavailable receive buffer"), or 5 ("Running - Closing receive
descriptor").  The dump after it works always has a receive state of 6.
This is happening on two of our systems and with processor cards using the
latest MPC106 as well as those with the older rev of it.
I've double checked that we have the code which forces the descriptors to
cross cache lines to compensate for the problem on the older MPC-106.
Has anyone else seen this problem?  If so, what did you find out?
Its happening VERY sporadically, so anything I use to analyze or debug the
problem has to be able to catch the problem and save the info without
crippling the system (so others can continue using it).
I would use a PCI bus analyzer, but the systems which this error is happening
in are water cooled and I cannot leave the door opened to have analyzer cables
hanging out.  Nor can I remove the processor to the right of the card under
test, since the system is used by the other members of our team and I can't
leave it in a butchered-up state.
Any I-dears would be greatly appreciated.
~~:-(
Andy
--MimeMultipartBoundary--
From d.luck@ieee.org  Tue Nov  4 12:04:26 1997
From: Dale Luck <d.luck@ieee.org>
Date: Tue Nov  4 12:04:30 PST 1997
Subject: RE: DEC 21140 Hangup During Filter Frame Send
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Don't know if this will actually help but I had a problem with the 21143 which
was traced to the chip coming up sleeping. Maybe the 21140 chip is once
in awhile coming up in sleep mode. Make sure you program the bits to wake
it up.
Dale
--MimeMultipartBoundary--
From laksh@pvdsw.amat.com  Tue Nov  4 13:02:49 1997
From: laksh@pvdsw.amat.com (Laksh Karuppiah x33230)
Date: Tue Nov  4 13:02:52 PST 1997
Subject: COFF to a.out
Has anyone used objcopy or similar utilities to convert COFF object format to a.out format?.
-Laksh
Applied Materials
From laksh@pvdsw.amat.com  Tue Nov  4 13:06:17 1997
From: laksh@pvdsw.amat.com (Laksh Karuppiah x33230)
Date: Tue Nov  4 13:06:21 PST 1997
Subject: greehills to gnu tools
We are looking for a consultant who can help us to convert oasys/greenhills 68 k code to gnu's 68k code. Also to migrate form a proprietry real time OS to vxworks. If you have experience in this area , please reply to this mail or call 408-563-3230.
-Laksh
Applied Materilas
From daemon@csg.lbl.gov  Wed Nov  5 04:02:54 1997
From: daemon@csg.lbl.gov
Date: Wed Nov  5 04:02:57 PST 1997
Subject: comp.os.vxworks newsdigest
Comp.Os.Vxworks Daily Digest    Wed Nov  5 04:02:50 PST 1997
        Subject: Re: 2000 problem
        Subject: Re: Skeleton or example device driver?
        Subject: File flush problem?
        Subject: Re: 2000 problem
        Subject: Re: 2000 problem
-------------------------------------------------------
Newsgroups: comp.os.vxworks,comp.realtime,comp.unix.programmer,comp.lang.c,comp.lang.c++
Subject: Re: 2000 problem
Date: 3 Nov 1997 14:15:44 -0600
From: madings@earth.execpc.com (Steve Mading)
Organization: ExecPC -- (800)-EXECPC-1
Message-ID: <63lbdg$jkg$1@earth.execpc.com>
References: <62fk8h$mjq@bcarh8ab.bnr.ca> <62ijm7$qmu@bgtnsc02.worldnet.att.net> <344DCDF8.26351658@absyss.fr> <OzBgx$r48GA.289@nih2naac.prod2.compuserve.com> <M77Nmaz48GA.75@news2.ingr.com> <Pine.A41.3.95.971028190810.11082D-100000@acis.mc.yu.edu> <34596AB1.5237@ici.net> <63kic7$kka$1@route1.mdrf.france3.fr> <345DF05D.3FAF@ici.net> <345DF992.41C6@ptc.com> <345E0BBB.1EAC493E@calfp.co.uk>
Followup-To: comp.os.vxworks,comp.realtime,comp.unix.programmer,comp.lang.c,comp.lang.c++
Nick Leaton (nickle@calfp.co.uk) wrote:
[re-formatted for readability]
: The  capacity  and  representation  issue  is  not  the  problem.
: Representing  data  with 2 digit years is not the issue. The real
: issue was people who cut and pasted or re-wrote all the code that
: used  the representation. If it was properly encapsulated in some
: functions or procedures you would have an easy  job  of  changing
: the  functions.  You would also have an easier job of finding and
: altering the data that uses 2 digit years.
"properly encapsulated"??!  We're talking mostly COBOL programs
here, where cut & paste is the only concept of reusability the
language supports.  It's truly a reflection of the idiocy of
upper management that crap like that had become the worldwide
standard for financial institutions.
- --
Steve Mading:  madings@execpc.com   http://www.execpc.com/~madings
---------------------------
Newsgroups: comp.os.vxworks
Subject: Re: Skeleton or example device driver?
Date: 4 Nov 1997 15:02:39 -0500
From: ted@telematics.com (Ted Goldblatt)
Organization: Telematics International - Ft Lauderdale, FL
Message-ID: <63nv0v$ipp@taurus.ftl.telematics.com>
References: <63l7pj$i2i@taurus.ftl.telematics.com> <345E4C0B.529D@llnl.gov>
In article <345E4C0B.529D@llnl.gov>, Doug Owens  <owens2@llnl.gov> wrote:
>We got an App Note with Tornado 1.0 called
>"Upgrading a vxWorks BSP for Tornado 1.0" that
>has skeleton code for serial drivers.  I think there
>are files in the distribution also.
Yes, I saw these (at least, I saw the code in the distribution, which
I assume is the same as you are talking about).  Part of the problem
is terminology (I've run into that here over the last couple of days).
The term "driver" covers at least 2 separate concepts related to this:
    the "driver" is the code that diddles the I/O chips to get them to
    do good stuff (I'll call this the "device side")
    the "driver" is the code that implements the open/close/read/write
    abstraction visible to users of the driver (the "VxWorks side")
Both of these are normally needed to create a functional driver.  The
former is basically what is encompassed by the code in the Tornado
target/src/drv directory (e.g., the templateSio.c file that I assume
you are referring to).  The latter is discussed in section 3.9 of the
VxWorks Programmer's Guide, and a couple of hypothetical generic
drivers (xxDrv and arkDrv) are outlined.  What I was looking for was a
complete driver (merging the items talked about with the xxDrv and
arkDrv examples) that stubbed the "device side", but fleshed out the
"VxWorks side".
ted
- --
Ted Goldblatt    Ted.Goldblatt@telematics.com     (954) 351-4367
    Telematics Intl., Inc.   Ft. Lauderdale, FL
---------------------------
Newsgroups: comp.os.vxworks
Subject: File flush problem?
Date: 3 Nov 1997 15:09:57 -0800
From: van@venice.dh.trw.com (Ken VanCouvering)
Organization: TRW Data Technologies Division, Carson CA
Message-ID: <63llk5$qvh@venice.dh.trw.com>
I am attempting to write a log file during a test run from our
target Sparc 5ce card to our Sun host.  This works fine as long
as the file is short, but long test runs crash VxWorks.  Further
investigation shows the file isn't openned or written to until
the program closes it.  Trying the ioctl FIOFLUSH doesn't appear
to do anything and isn't pushing the data to disk.
Has somebody else solved this?  I would think it would be a common
problem.
Ken VanCouvering
TRW
van@venice.dh.trw.com
---------------------------
Newsgroups: comp.os.vxworks,comp.realtime,comp.unix.programmer,comp.lang.c,comp.lang.c++
Subject: Re: 2000 problem
Date: Wed, 05 Nov 1997 09:10:42 +0000
From: Paul Black <paul.black@vf.vodafone.co.uk>
Organization: Vodafone Ltd.
Message-ID: <34603812.EBB@vf.vodafone.co.uk>
References: <62fk8h$mjq@bcarh8ab.bnr.ca> <01bcdf9c$71b5bfc0$daac2ac0@pub00005m> <62np2n$e4t@dg-rtp.dg.com> <345E1269.628F95FE@webvision.com> <63o174$4e8@top.mitre.org>
mfb@mbunix.mitre.org (Michael F Brenner) wrote:
>
> In particular, this shows why the twentieth century certainly
> does begin with the year 2000, not the year 2001. Anyone who
> says otherwise is using an arbitrary convention.
Pots, kettles and colours?
Paul
---------------------------
Newsgroups: comp.os.vxworks,comp.realtime,comp.unix.programmer,comp.lang.c,comp.lang.c++
Subject: Re: 2000 problem
Date: 5 Nov 1997 00:38:44 GMT
From: dgy@rtd.com (Don Yuniskis)
Organization: none
Message-ID: <63of6k$oe6$1@baygull.rtd.com>
References: <62fk8h$mjq@bcarh8ab.bnr.ca> <63ldf6$b4e$1@darla.visi.com> <63o8a2$j7m$1@baygull.rtd.com> <63obi8$718$1@darla.visi.com>
In article <63obi8$718$1@darla.visi.com>,
David Thornley <thornley@visi.com> wrote:
>In article <63o8a2$j7m$1@baygull.rtd.com>, Don Yuniskis <dgy@rtd.com> wrote:
>>In article <63ldf6$b4e$1@darla.visi.com>,
>>David Thornley <thornley@visi.com> wrote:
[snip]
>>>Ever done COBOL?  The function support is awfully clumsy.  In most
>>>languages I've used, other than COBOL and some BASICs, it's easy to
>>>substitute access functions for variables.  This doesn't mean it's
>>>done all the time, of course.  If a program was written in 1970,
>>>and its expected lifetime was ten years, tops, there was no reason to
>>>encapsulate the date representation.
>>
>>I don't understand this "expected lifetime" notion.  I can't recall *ever*
>>writing a piece of code and putting a number on how many years I *expected*
>>it to be around.  And *most* of the code I've written resides in EPROM's
>>that have *published* lifetimes, etc.  (i.e. at the time, 10 years until
>>they started dropping bits).
>
>Usually, nobody comes up with an estimate for how long the code will
>last, but that's more sloppiness than anything else.  Programs
Agreed.
>were expected to die after a while, and one training course I took
>suggested five years as when a system designed now would be obsolete.
>I'm not saying there were any good reasons for this, mind you.
I guess my experience has been different (what are now called "embedded
systems").  A "consumer" would be annoyed if a "product" he purchased
*didn't* last 5 years (or more).
>>Was there anything at the time that made you think they *wouldn't*
>>be relevant?
>
>Not really, but when programs have never lasted ten years before, why
>*would* you assume they would last over thirty years?  Yes, it was
>a bad call, but there were reasons behind it.
>
>Remember that everybody who uses four-digit dates will be screwed if
>their programs last another eight thousand years.  Are you worried
>about that?  Are you worried about making your programs readable for
>AIs or just for humans?  People don't tend to prepare for things that
>their experience tells them won't be problems.
I think, again, that depends on your application domain.  Building
"things" (vs. just "writing code") I think makes you think about
how long someone will actually want to *use* that "thing".  Products
I've designed in the 70's are still in use today (though spare
parts are becoming a nuisance... anyone have a few spare i4004's?  :>)
The products I'm designing lately are targeted for a minimum 30 year
"service life" (who knows how much *longer* than that some customers
will elect to use them).  Of course, now the problem is getting
silicon vendors to commit to producing things for more than *3*
years... :-(
>>>You're blaming 1960s and 1970s programmers for not doing things that
>>>are fairly standard in, say, C++ in the late 90s.  I assure you that
>>>with the usual systems available in the 70s, it would have been a lot
>>>easier and more likely to simply use 4-digit years in the first place
>>>rather than to use access functions.
>>
>>Yes.  However, I've never designed a piece of hardware that used a
>>RTC with a 4 digit calendar.  Some have actually implemented *1* year
>>calendars or perhaps *4* year calendars (and they assume that "year 4"
>>is a leapyear). Yet, the products containing these RTC's all were
>>capable of dealing with the year 2100 leap year adjustments, etc.
>>Of course, perhaps when you *have* to write the timekeeping routines
>>in software (instead of just reading a "system value") you probably
>>tend to think of implementing a "real" calendar instead of just
>>a two digit year (since going from a "two bit" hardware representation
>>of the current year to 4 *digits* is probably more intuitive than
>>"stopiing short" with a two digit representation).  And all of *those*
>>suffered from the "non-portable" assembly language implementation, etc.
>
>You seem to be talking about specialized applications.  Most of the
>systems that will crash and burn communicated with humans about dates,
>and it would be significant that a date was 1960 rather than 1964.
I guess I wasn't clear.  The *hardware* maintained dates on a one or
four year calendar.  The *software* extended this to a 4 digit
scheme (e.g., by storing ``1997'' in the ``year_offset'' nonvolatile
variable).  In essence, the hardware was just used as something
that kept track of elapsed time while the device was *off*.  Users
dealt in terms of "real" dates and the devices behaved accordingly.
>These dates were stored in digit form for various reasons, including
>that they were very easy to read out of a file dump or core dump.
>Given that they were going to be stored in digits, doing so in two
>digits reduced the necessary storage by one or two bytes.  After all,
>how many people consistently write "1997" as today's date, and not
>(say) "97".  My checks have the "19" pre-printed on them, so I'll
>have to get new checks in a couple of years.
I suspect the "2 digit" issue was arose from someone coding the year
in a 2 character field on a punched card and it just "naturally"
carried over into the code, etc.  And, once established, it was
never changed.
>Two-digit dates seemed reasonable at the time.  It doesn't matter that
>it seems unreasonable now, because the problem stems from then.
>There's a lot of things I did in the sixties and seventies that I
>wouldn't do now, professionally and unprofessionally.  I dislike
Oh?  What was her name??  :>
>the attitude that what is clearly stupid now was clearly stupid at
>the time, because it required a good deal of extrapolation from
>current experience.  Of course we wouldn't do things that way now,
>and besides we'd be better at encapsulating it if we did.
>
>It doesn't matter what you think is intuitive, or what you think
>people should have expected as part of massive changes in the industry.
While all the newscasts forecast doom-and-gloom and airliners falling
out of the sky at midnight on Dec 31 1999, I haven't seen any "fuss"
over this issue in the embedded systems community.  I think this
reflects a different attitude towards the "software" (firmware)
as part of a "thing" instead of as a (generic) "software".  So,
whether it's a *game* or a *gas pump*, it tends to have a good
knowledge of what the future holds in terms of "dates"...
>You're using decades of hindsight, and have absorbed the notion that
Not at all.  The products I designed in the 70's didn't have decades
behind them!  :>
>code does hang around indefinitely, and that four-digit years are good.
>Many things that are clear now were very fuzzy then.  Check out a
>copy of Brooks' Mythical Man-Month:  among many other good observations
Yes I read it as an undergraduate 20 years ago...
>was a statement that information hiding is likely to cause disasters.
>Brooks was highly intelligent and perceptive, and he blew that one
>as hard as it can be blown (as he says, with more proper language,
>in the silver anniversary edition, which is well worth getting).
>
>BTW, how do you handle 2100 properly with a four-bit calendar?  How
>does the thing know it's 2100 and not 1204?
Again, my explanation probably wasn't clear enough.  The RTC is *not*
consulted for the current date.  That is all maintained in software.
This gets around the problem that many (early) RTC's had varying
degrees of "date" support -- some were just 24 hour clocks!  So,
by moving all of the time keeping functions into software (and
solving that problem *once*), the hardware was allowed to evolve and
vary from product to product.  Obviously, if your *code* knows it is
2104 (vs. 2100) there's no problem!
- --don
---------------------------
End of New-News digest
**********************
From ajohnston@rainbow.robins.af.mil  Wed Nov  5 05:24:32 1997
From: "Albert S. Johnston" <ajohnston@rainbow.robins.af.mil>
Date: Wed Nov  5 05:24:36 PST 1997
Subject: port from sunos to solaris vs RPC's
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hello,
I am in the process of trying to port from sunOS 4.1.4 to 5.6 (solaris
2.6).  I am concerned about
the impact that this change will have on my rpc clients and servers.
Has anywone walked this
road yet?... I could use some advice as to approach....
thanks,
    -al
--MimeMultipartBoundary--
From prb@aplexus.jhuapl.edu  Wed Nov  5 05:51:06 1997
From: prb@aplexus.jhuapl.edu (Paul R. Bade)
Date: Wed Nov  5 05:51:10 PST 1997
Subject: Re: File flush problem?
Ken VanCouvering writes:
> I am attempting to write a log file during a test run from our
> target Sparc 5ce card to our Sun host.  This works fine as long
> as the file is short, but long test runs crash VxWorks.  Further
> investigation shows the file isn't openned or written to until
> the program closes it.  Trying the ioctl FIOFLUSH doesn't appear
> to do anything and isn't pushing the data to disk.
You need to use file pointers or NFS.
With File descriptors (and not NFS), vxWorks always keeps
the entire open file resident in RAM.
+====================================================================+
|       __     ____         __     __                                |
|      /\ \   /  \ \       /\_\__ /\ \      Johns Hopkins University |
|     /  \_\ | /\ \ \     / / /\_\\ \ \     Applied Physics Lab.     |
|    / /\ | |\ \/  \ \   / / / / / \ \ \                             |
|   /  \/ |_| \  /\ \_\ / / / / /   \ \ \   Paul R. Bade             |
|  / /\__/_/   \ \ \/_// / / / /    / / /   (301)-953-6000 x8681     |
| / / /         \ \_\  \ \/ / /    / / /    prb@aplexus.jhuapl.edu   |
| \/_/           \/_/   \__/_/     \/_/                              |
|               __     ____         __       __                      |
|              /\ \   /  \ \       /\ \     /\ \                     |
|             /  \_\ | /\ \ \     /  \_\   /  \ \                    |
|            / /\ | |\ \/  \ \   / /\ |_| / /\ \ \                   |
|           /  \/ |_| \  /\ \_\ / / / | | \/ /  \ \                  |
|          / /\  / /   \ \ \/_// / / / /    / /\ \_\                 |
|          \ \/ / /     \ \_\  \ \/ / /     \/ / / /                 |
|           \__/_/       \/_/   \__/_/        /_/_/                  |
|                                                                    |
+====================================================================+
From yzur@qualcomm.com  Wed Nov  5 05:56:43 1997
From: Joseph  Zur <yzur@qualcomm.com>
Date: Wed Nov  5 05:56:46 PST 1997
Subject: Problems running the default vxWorks code ...
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Hi,
I installed a mv177 motorola card (68060) and I am trying to attach to it
with the target server to run tornado.
I took the default vxWorks code and loaded it into the card assuming it
includes the target agent (so I understand from the configAll.h file).
when trying to load and run the file I get those messages:
Any one can help ? what is the cause of the problem ?
----- printouts from the console follow ---------------
Backplane anchor at 0x80000600... Attaching network interface sm0... done.
Attaching network interface lo0... done.
Loading... 585728 + 86272 + 36064
Starting at 0x1000...
Backplane anchor at 0xf0800000... Attaching network interface sm0... done.
smIsAlive: bus error checking anchor
smIsAlive:  readyValue = 0x6, heartbeat = 0x0
smIsAlive: bus error checking anchor
smIsAlive:  readyValue = 0x6, heartbeat = 0x0
smIsAlive: bus error checking anchor
smIsAlive:  readyValue = 0x6, heartbeat = 0x0
------------ printouts end ---------------
Does anyone has guidlines or recomendation as to how to create the code to
load to the target, in order to run tornado on the unis machine ?
the tgtsvr command does not sem to attach to the target card !
thanks in advance
--- joseph
--MimeMultipartBoundary--
From froeber@bbn.com  Wed Nov  5 06:36:09 1997
From: Fred Roeber <froeber@bbn.com>
Date: Wed Nov  5 06:36:12 PST 1997
Subject: Re: File flush problem?
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Ken VanCouvering wrote:
> I am attempting to write a log file during a test run from our
> target Sparc 5ce card to our Sun host.  This works fine as long
> as the file is short, but long test runs crash VxWorks.  Further
> investigation shows the file isn't openned or written to until
> the program closes it.  Trying the ioctl FIOFLUSH doesn't appear
> to do anything and isn't pushing the data to disk.
>
> Has somebody else solved this?  I would think it would be a common
> problem.
The problem is that you are writing to a file on a disk that is
being handled using the VxWorks netDrv driver. This disk driver
acts by keeping the file in memory until it is closed. If you set
up a disk connection that will use NFS then you will see that the
file is handled the way you expect. Check the programmers guide
on mounting and using NFS disk interfaces. You are right that this
is a common problem since the default disk connection after bootup
uses netDrv.  Fred
--
   |     Fred J Roeber,  BBN Systems & Technologies     |
   |   4 John Clarke Road   Middletown, RI  02842-5202  |
   |         froeber@bbn.com     401-848-3548           |
--MimeMultipartBoundary--
From WILLIAMK@wpg.lmcda.lmco.com  Wed Nov  5 07:13:13 1997
From: "Williams, Kerry @ WIN" <WILLIAMK@wpg.lmcda.lmco.com>
Date: Wed Nov  5 07:13:17 PST 1997
Subject: Re: File Flush Problems
I ran into the same problem a couple of months ago.
The problem is that you have opened your log file with the netDrv device
driver,
which is the vxWorks default for accessing files across the network. For
some
unknown reason, netDrv tries to buffer any files it opens in RAM until
the file is
closed. However, there seems to be no built in limit on the size of the
file netDrv
thinks it can buffer. So your file will merrily tromp through RAM until
is blows
away something critical and your system crashes.
The solution is to get vxWorks to use another file system to create your
logfile.
We have used vxWorks' NFS driver to good success. Email me if you want
the
details of getting this to work.
Cheers!
Kerry.
_______________________
#include <stdDisclaimer.h>
Kerry Williams
Computer Engineer
Lockheed Martin Canada
kerry.williams@lmco.com
 ------------------------------------------------------------------------
Newsgroups: comp.os.vxworks
Subject: File flush problem?
Date: 3 Nov 1997 15:09:57 -0800
From: van@venice.dh.trw.com (Ken VanCouvering)
Organization: TRW Data Technologies Division, Carson CA
Message-ID: <63llk5$qvh@venice.dh.trw.com>
I am attempting to write a log file during a test run from our
target Sparc 5ce card to our Sun host.  This works fine as long
as the file is short, but long test runs crash VxWorks.  Further
investigation shows the file isn't openned or written to until
the program closes it.  Trying the ioctl FIOFLUSH doesn't appear
to do anything and isn't pushing the data to disk.
Has somebody else solved this?  I would think it would be a common
problem.
Ken VanCouvering
TRW
van@venice.dh.trw.com
From wbrown@csg.lbl.gov  Wed Nov  5 07:48:45 1997
From: wbrown@csg.lbl.gov (Bill Brown)
Date: Wed Nov  5 07:48:48 PST 1997
Subject: Re: Compact PCI support
wong@vms.masd.northgrum.com (J. Pierre Wong) said:
>
> Could anyone please send me a list of tornado/vxWorks supported CompactPCI
> processor boards that use any CPU architecture from x86 to whatever?
>
Replies to the list, or a summary from the wong@vms.masd.northgrum.com would
be greatly appreciated, as we are also interested in the subject.
Disclaimer:  Any opinions are my own and have	    |  -bill
    nothing to do with the official policy or the   |   wlbrown@lbl.gov
    management of L.B.N.L, who probably couldn't    |   Berkeley, CA
    care less about employees who play with trains. |   aka wlbrown@netcom.com
From cgrames@mdc.com  Wed Nov  5 07:53:55 1997
From: Charlie Grames <cgrames@mdc.com>
Date: Wed Nov  5 07:53:58 PST 1997
Subject: File flush problem? -Reply
Ken,
You did not discuss what file system you are using.  Is it a local disk or network?  If it is a network
disk, then the driver used is important.  The default netDrv driver is based on FTP or RSH.  When a
file is opened, the entire file is copied into target memory, and all I/O is performed there.  Data is
not written back out to disk until the file is closed, even if you flush.  If this behavior is unacceptable
(which it appears to be in your case), you need to use NFS instead.  Refer to the Programmer's
Guide or nfsDrv in the Reference Guide.
Hope this helps.
Charlie Grames
The Boeing Company
(314) 233-1956
Charles.R.Grames@boeing.com
-----
Newsgroups: comp.os.vxworks
Subject: File flush problem?
Date: 3 Nov 1997 15:09:57 -0800
From: van@venice.dh.trw.com (Ken VanCouvering)
Organization: TRW Data Technologies Division, Carson CA
Message-ID: <63llk5$qvh@venice.dh.trw.com>
I am attempting to write a log file during a test run from our
target Sparc 5ce card to our Sun host.  This works fine as long
as the file is short, but long test runs crash VxWorks.  Further
investigation shows the file isn't openned or written to until
the program closes it.  Trying the ioctl FIOFLUSH doesn't appear
to do anything and isn't pushing the data to disk.
Has somebody else solved this?  I would think it would be a common
problem.
Ken VanCouvering
TRW
van@venice.dh.trw.com
From Richard_W_Mattox@ccmail.orl.lmco.com  Wed Nov  5 08:21:07 1997
From: Richard_W_Mattox@ccmail.orl.lmco.com
Date: Wed Nov  5 08:22:19 PST 1997
Subject: C++ vs. Ada
--MimeMultipartBoundary
Content-type: TEXT/PLAIN
Content-transfer-encoding: 7BIT
Hello Fellow VxWorkers,
I am requesting any information or studies that people have done comparing C++
and Ada 95 in a VxWorks environment.  I prefer a commercial company over a DoD
organization because all the studies from the DoD are biased towards Ada.  Any
information would be greatly appreciated and can be sent to me directly at the
address below.
Rick Mattox
richard.w.mattox@lmco.com
--MimeMultipartBoundary--
From fbh@vdragon.gsfc.nasa.gov  Wed Nov  5 08:59:05 1997
From: fbh@vdragon.gsfc.nasa.gov (Frank Hallahan)
Date: Wed Nov  5 08:59:08 PST 1997
Subject: Re: Problems running the default vxWorks code ...
>
> Submitted-by yzur@qualcomm.com  Wed Nov  5 05:56:43 1997
> Submitted-by: Joseph  Zur <yzur@qualcomm.com>
>
> Hi,
>
> I installed a mv177 motorola card (68060) and I am trying to attach to it
> with the target server to run tornado.
> .....
> ----- printouts from the console follow ---------------
>
> Backplane anchor at 0x80000600... Attaching network interface sm0... done.
> Attaching network interface lo0... done.
> Loading... 585728 + 86272 + 36064
> Starting at 0x1000...
>
> Backplane anchor at 0xf0800000... Attaching network interface sm0... done.
>
> smIsAlive: bus error checking anchor
> smIsAlive:  readyValue = 0x6, heartbeat = 0x0
>
>  .....
> ------------ printouts end ---------------
>
> Does anyone has guidlines or recomendation as to how to create the code to
> load to the target, in order to run tornado on the unis machine ?
> the tgtsvr command does not sem to attach to the target card !
>
> thanks in advance
>
> --- joseph
First, I am assuming that you are booting the mv177 as a slave processor
over the shared memory network.  A quick and dirty test is to hookup
a network connection directly to the mv177, boot over the "ei" device,
and see whether or or not tornado works.
The "smIsAlive" messages are telling you that the mv177 is NOT actually
available on the shared memory network.  I have seen a lot of problems
getting cache and MMU configured correctly on mv167s and mv177s.
Any problems with the mv177 memory map can prevent the mv1x7s working
with the shared memory network.  I don't know haw WRS configured your
default vxworks image, but you might try rebuilding it with the MMU off.
Another reason to get bus errors on the shared memory net is that your
VME bus is either configured incorrectly (like 2 boards at the same
address) or that the VME bus is extremely busy.  A busy bus is
 the hardest problem to fix
in a full rack; I can offer additional suggestion if this is your case
To test for VME problems, try running only the mv177 and your master
(and your memory board if using SM_OFF_BOARD).  If just these two cards
work together, then look at what activity is on your VME bus.
Hope this helps.
Frank Hallahan
---------------------------------------------------------------------------
| Frank Hallahan                            |  Hallahan@gsfc.nasa.gov     |
|   Software Environment Leader - Code 521  |  fbh@vlsi.gsfc.nasa.gov     |
| Computer Sciences Corporation             |                             |
| at Nasa Goddard Space Flight Center       |  Phone (301) 286 7064       |
---------------------------------------------------------------------------
From cruz_nojunk@xyplex.com  Wed Nov  5 09:19:13 1997
From: Roger Cruz <cruz_nojunk@xyplex.com>
Date: Wed Nov  5 09:19:16 PST 1997
Subject: Re: DEC 21140 Hangup During Filter Frame Send
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
>The chip hangs up sporadically when the processor
If you are using WRS if_dcfast.c,  it has a bug that cause sporadic
hangs for me.  It didn't happen just during setup, though.  If you look
at their code, you'll notice that they change bit 18 (Port Select) of
CSR6 and do not reset the chip as required!  Change the code so it does
and see if your problems go away.
--
Roger Cruz                           cruz_nojunk@xyplex.com
Xyplex Networks                      w: 508-952-4783
295 Foster Street                    f: 508-952-4887
Littleton, MA 01460
--MimeMultipartBoundary--
From harvey@wrs.com  Wed Nov  5 09:19:36 1997
From: Harvey Wong <harvey@wrs.com>
Date: Wed Nov  5 09:19:38 PST 1997
Subject: 100 Mbit ethernet cards
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Dear VxWorks community,
I'm looking for VMEbus or Sbus 100Mbit ethernet cards with VxWorks drivers
support.
I'd appreciate any suggestions or recommendations.
Thanks,
Harvey
***************************************************************
Harvey Wong			Wind River Systems, Inc.
Field Applications Engineer,		1010 Atlantic Avenue
Asia-Pacific Operations		Alameda, CA  94501
e-mail:  harvey@wrs.com		Ph:  510/748-4100
				Fax:  510/814-2011
--MimeMultipartBoundary--
From mea@mclean.sparta.com  Wed Nov  5 11:16:05 1997
From: "Mike Anderson" <mea@mclean.sparta.com>
Date: Wed Nov  5 11:16:17 PST 1997
Subject: Any experiences with vxworks_rom.hex?
--MimeMultipartBoundary
Content-Type: text/plain;
	charset="windows-1252"
Content-Transfer-Encoding: 7bit
Greetings!
  Anyone out there in net land had any experiences they could share on making
and using the standalone VxWorks from ROM flavor (vxworks_rom.hex) especially
on the MVME162LX?  Just doing a make on the object and burning the ROM results
in a dead system.  Any pointers would be appreciated.
TIA,
---------------------------------------------------------------------
|Michael E. Anderson        | Voice -> 703 448 1683 x235            |
|Chief Engineer             | FAX   -> 703 893 5494                 |
|mea@mclean.sparta.com      | http://www.mclean.sparta.com          |
|___________________________|_______________________________________|
|             SPARTA, Inc.              |                           |
|     /\\     C4I Operation             |"Software Development is   |
|    ///\\    7926 Jones Branch Drive   | like making a baby...     |
|   /////\\   Suite 900                 | You can't make a baby in  |
|  /////  \\  McLean, VA 22102          | one month by impregnating |
| / \\\\\  \\ 703-448-0210              | nine women.               |
| \  \\\\\ //                           |                           |
|  \  //////                            | Some things just take     |
|   \//////   SPARTA                    | time."                    |
|    \////    Pride In Performance      |                           |
|     \//     --------------------      |                           |
---------------------------------------------------------------------
--MimeMultipartBoundary--
From d.luck@ieee.org  Wed Nov  5 11:19:46 1997
From: Dale Luck <d.luck@ieee.org>
Date: Wed Nov  5 11:19:50 PST 1997
Subject: taskSuspend/taskResume usage question
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Is taskSuspend/taskResume quicker to use then other methods for restarting a task?
I have a device that when it interrupts requires about 1millisecond of processing to
exchange data withit. I have to do this every 5msecs.
This meant that I was holding off interrupts for 1msec every 5 msecs. Which adversely
affected the serial port (running at 38400) as well as other devices.
So I've moved almost the entire code to a separate thread which basically looks like this.
DeviceThread(void)
{
	while (1)
	{
		/* go to sleep waiting to be woke up by interrupt */
		taskSuspend(0);
		/* Woke up */
		While (worktodo)
		{
			/* do all the messy work with interrupts enabled */
		}
	}
}
InterruptRoutine(void)
{
	AckTheInterrupt();
	taskResume(DeviceThreadID);
}
Questions:
Is there a counter for Suspend/Resume?
If so can the interrupt routine call taskResume more than once and the
Device thread will only actually Suspend itself when it gets back to zero?
Is there a better/faster way to do this?
Dale Luck
--MimeMultipartBoundary--
From brett@rti.com  Wed Nov  5 11:19:58 1997
From: brett@rti.com (Brett Murphy)
Date: Wed Nov  5 11:20:01 PST 1997
Subject: RTI Job Opportunies
Hi Everyone,
I've noticed a rash of job postings lately.  We thought we'd throw in that RTI is looking for real-time engineers.  We're also looking for engineers who want to move into sales or technical marketing.  Great opportunities with a fun,
fast-growing company!
-Brett Murphy
 brett@rti.com
 http://www.rti.com
From d.luck@ieee.org  Wed Nov  5 11:44:45 1997
From: Dale Luck <d.luck@ieee.org>
Date: Wed Nov  5 11:44:48 PST 1997
Subject: serial port hardware handshake
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
I've modified the 8530 serial port to do hardware handshake,
at least on the transmission side. According to the documentation
the serial port subsystem does software flow control. Is there a way
to turn this off so it will run faster?
Seems to me hardware flow control is the obvious way to go in
a realtime system.
Dale Luck
--MimeMultipartBoundary--
From piyush@net.com  Wed Nov  5 12:31:47 1997
From: Piyush Shah <piyush@net.com>
Date: Wed Nov  5 12:31:51 PST 1997
Subject: Job opportunity in California bay area
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Position Title: Senior Software Engineer
Responsibilities include:
- Support the development staff in the use of WindRiver, VxWorks,
  Tornado and other development tools.
- Vendor liaison, maintain and drive upgrades working with the team
  leads.  Be aware of version delta's, new releases, bugs and patches.
- Ensuring the integrity of WindRiver Tools in the ClearCase
  environment.  Ownership of the Release Engineering Process and its
  integration with other software development processes (ClearCase,
  DDTS, etc)
- Facilitate training class in Software Tools usage.
Qualifications required:
- A bachelors or higher degree in a technical discipline (eg. CS,
  Software Engineering, Computer Engineering, EE) or equivalent experience.
- 3-5 years experience as a developer/user of WindRiver, VxWorks and
  Tornado tools, preferably in SunOS/Solaris environment.
- 1-2 years experience supporting software development groups.
  Experience in C, make, imake, gnumake, shell scripts, perl, html.
- Familiar with the processes related to Software Tools Management and
  Software Quality Assurance.
- Experience in problem determination with the ability to solve
  problems quickly and accurately.
- Ability to build consensus among the different Engineering groups.
  Contributing to the productivity of software development groups.
- Experience creating user documentation and good communication skills.
If you are interested, email/fax your resume.
---------------------------------------------------------------------
Piyush Shah                              Email: piyush@net.com
Network Equipment Technologies           http://www.net.com/
800 Saginaw Drive                        Voice: (650)569-7061
Rewdwood City CA 94063                   Fax:   (650)780-5001
---------------------------------------------------------------------
--MimeMultipartBoundary--
From jford@sadira.gb.nrao.edu  Wed Nov  5 13:47:10 1997
From: John Ford <jford@bara.gb.nrao.edu>
Date: Wed Nov  5 13:47:15 PST 1997
Subject: Re: taskSuspend/taskResume usage question
> Submitted-by d.luck@ieee.org  Wed Nov  5 11:19:46 1997
> Submitted-by: Dale Luck <d.luck@ieee.org>
>
> Is taskSuspend/taskResume quicker to use then other methods for restarting a task?
I would use a semaphore and a semgive()/semtake pair.
>
> I have a device that when it interrupts requires about 1millisecond of processing to
> exchange data withit. I have to do this every 5msecs.
>
> This meant that I was holding off interrupts for 1msec every 5 msecs. Which adversely
> affected the serial port (running at 38400) as well as other devices.
>
> So I've moved almost the entire code to a separate thread which basically looks like this.
>
> DeviceThread(void)
> {
> 	while (1)
> 	{
> 		/* go to sleep waiting to be woke up by interrupt */
> 		taskSuspend(0);
> 		/* Woke up */
> 		While (worktodo)
> 		{
> 			/* do all the messy work with interrupts enabled */
> 		}
> 	}
> }
>
> InterruptRoutine(void)
> {
> 	AckTheInterrupt();
> 	taskResume(DeviceThreadID);
> }
>
> Questions:
> Is there a counter for Suspend/Resume?
> If so can the interrupt routine call taskResume more than once and the
> Device thread will only actually Suspend itself when it gets back to
zero?
>
> Is there a better/faster way to do this?
How about this?  Note that using a counting semaphore allows you to
stack up the semgive() calls.
SEM_ID sem;
DeviceThread(void)
 {
    semCCreate(OPTIONS_YOU_NEED,INITIAL_COUNT);
 	while (1)
 	{
 		/* go to sleep waiting to be woke up by interrupt */
 		semtake(sem,WAIT_FOREVER);
 		/* Woke up */
 		While (worktodo)
 		{
 			/* do all the messy work with interrupts enabled */
 		}
 	}
 }
InterruptRoutine(void)
{
    semgive(sem);
    AckTheInterrupt();
}
Hope this helps.
--
John Ford
National Radio Astronomy Observatory
Green Bank, WV 24944-0002
jford@nrao.edu
From currie@ghg.net  Wed Nov  5 14:12:45 1997
From: currie@ghg.net (Alan Currie)
Date: Wed Nov  5 14:12:49 PST 1997
Subject: Re: taskSuspend/taskResume usage question
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
I would not make any taskSuspend/taskDelete calls from interrupt level.
 You need to develop a way to poll your device until it is ready and not
do any task operations in my opinion.
--MimeMultipartBoundary--
From bm417929@muenchen.org  Wed Nov  5 14:16:34 1997
From: bm417929@muenchen.org (Max Seeger)
Date: Wed Nov  5 14:16:39 PST 1997
Subject: Re: Compact PCI support
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Hi,
I know for sure that FORCE has a PowerPC based 3U CompactPCI
board and VxWorks/Tornado 1.0.1 support.
What I heard is that they will follow up soon with a 6U board
based on PowerPC.
They have also a Intel based CompactPCI board, but I do not know
if they have VxWorks support for it. Maybe you can check it
with them directly.
Max
At 07:48 05.11.97 PST, the vxWorks Users Group Exploder wrote:
>Submitted-by wbrown@csg.lbl.gov  Wed Nov  5 07:48:45 1997
>Submitted-by: wbrown@csg.lbl.gov (Bill Brown)
>
>wong@vms.masd.northgrum.com (J. Pierre Wong) said:
>>
>> Could anyone please send me a list of tornado/vxWorks supported CompactPCI
>> processor boards that use any CPU architecture from x86 to whatever?
>>
>
>Replies to the list, or a summary from the wong@vms.masd.northgrum.com would
>be greatly appreciated, as we are also interested in the subject.
--MimeMultipartBoundary--
From currie@ghg.net  Wed Nov  5 14:20:33 1997
From: currie@ghg.net (Alan Currie)
Date: Wed Nov  5 14:20:38 PST 1997
Subject: Re: Any experiences with vxworks_rom.hex?
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
We are using the DY4 SVME163 68040 board in rom standalone mode.  When
we burn new PROMs we are overlaying the foundation firmware with the new
changes.  I have had problems if the PROM burn is configured for the
wrong type of EPROM devices.  You can end up with a dead board via this
method.  Your addresses and jump addresses must be configured
correctly.  Another good way to end up with a dead board.  A dead board
requires us to program the board across the VME backplane with another
board.  Hope this helps!
--MimeMultipartBoundary--
From d.luck@ieee.org  Wed Nov  5 15:12:48 1997
From: Dale Luck <d.luck@ieee.org>
Date: Wed Nov  5 15:12:55 PST 1997
Subject: RE: taskSuspend/taskResume usage question
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
I'm not doing any taskSuspend/taskDelete calls, only taskResume.
Is this still a problem?
> I would not make any taskSuspend/taskDelete calls from interrupt level.
>  You need to develop a way to poll your device until it is ready and not
> do any task operations in my opinion.
>
--MimeMultipartBoundary--
From kb+@andrew.cmu.edu  Wed Nov  5 16:17:59 1997
From: Kevin Bradley <kb+@andrew.cmu.edu>
Date: Wed Nov  5 16:18:03 PST 1997
Subject: Re: taskSuspend/taskResume usage question
Excerpts from mail: 5-Nov-97 taskSuspend/taskResume usag.. by the U. G.
Exploder@lbl.g
> Is taskSuspend/taskResume quicker to use then other methods for
> restarting a task?
This I don't know.  However, I suspect it may not be, as I think
this is a seldom-used technique.
> Questions:
> Is there a counter for Suspend/Resume?
> If so can the interrupt routine call taskResume more than once and the
> Device thread will only actually Suspend itself when it gets back to zero?
Pretty sure there isn't a counter for Suspend/Resume. Using taskResume
could lead to a nasty condition wherein your ISR does a resume right
before the task Suspends().
To quote from the manual about taskSuspend(),
    "However, as a synchronization mechanism, this facility
     should be rejected in favor of the more general semaphore
     facility."
The usual technique for doing this is using semaphores, which have
a very quick give/take mechanism (measured at a couple microseconds
on a Pentium/75, depending on flavor).
I've used this technique on a device that takes interrupts every 10 ms,
and there's about 10-20 us delay from the semGive to the task resuming.
This I attribute to scheduler overhead (interrupt resuming to task
suspended, task suspended swapping out for high priority task).
If you're concerned about your routine taking longer than 5 ms, then
a counting semaphore with an initial value of 0 is the way to go:
InterruptRoutine()
{
    AckTheInterrupt();
    semGive(countId);
}
Routine()
{
    countId = semCCreate(SEM_Q_PRIORITY, 0);
    while(1) {
        semTake(countId, WAIT_FOREVER);
        while(Work)
            DoIt();
     }
}
This way, if multiple interrupts occur, countId will have a record
of how many passed, in that it'll pass that many "semTakes".
Other people had some suggestions about using the SEMAPHORE
structure explicitly to find out different pieces of information
about the semaphore (taken, etc.); I think the consensus was
that it's probably not a good idea due to portability, but
could be done if you're desparate to find out.
Look in $(WIND_BASE)/target/h/private/semLibP.h  for the SEMAPHORE
definition.
You could also try using message queues with a fairly deep
number of messages, should you actually need to send data
from the ISR to Routine():
ISR()
{
    Ack();
    msgQSend(msgQ_ID, data_buf, sizeof(data_struct), NO_WAIT, MSG_PRI_NORMAL);
}
Routine()
{
    msgQ_ID = msgQCreate(LOTS_OF_MESSAGES, sizeof(data_struct),
                         MSG_Q_PRIORITY);
    while(1) {
        msgQReceive(msgQ_ID, data_buf, sizeof(data_struct) * 1, WAIT_FOREVER);
        Process(data_buf);
    }
}
This has the advantage that you'll not lose data if multiple interrupts
go by (presuming that your device gets data), and you pay a small
penalty for copying the data around and manipulating the queue structure.
If the pipeline gets filled up, then the msgQSend just drops the data
with NO_WAIT (must be used in ISR).
Hope this helps...
                                                    -- Kevin
From espin@idiom.com  Wed Nov  5 16:24:50 1997
From: Geoffrey Espin <espin@idiom.com>
Date: Wed Nov  5 16:24:53 PST 1997
Subject: Re: Compact PCI support
--MimeMultipartBoundary
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Pierre,
> I know for sure that FORCE has a PowerPC based 3U CompactPCI
> board and VxWorks/Tornado 1.0.1 support.
> What I heard is that they will follow up soon with a 6U board
> based on PowerPC.
>
> They have also a Intel based CompactPCI board, but I do not know
> if they have VxWorks support for it. Maybe you can check it
> with them directly.
Tornado BSPs:
Ziatech has two 6U boards: zt5510 & zt5520 Pentiums (+Pro x2) plus a 3U Enet.
Radisys has a Pentium EPC-100 with 10/100Mbit Enet onboard.
Check their respective web-sites for contact info.
Geoff
--
Geoffrey Espin espin@idiom.com
--MimeMultipartBoundary--
From kareem@isys.com  Wed Nov  5 16:58:01 1997
From: kareem@isys.com (Kareem Fawell)
Date: Wed Nov  5 16:58:05 PST 1997
Subject: Parity Errors
Hello:
We are going to be moving from 68Ks on VME backplanes to generic PC's.
Reliability is a concern, especially in terms of uptime, that is, how
long can the PC run without a hardware error that can cause a software
failure.  Would anyone have advice or comments about this?  Also, would
ECC RAM be a sensible kind of RAM to use?
Thank you very much,
Kareem Fawell
SWE, Cognex Corp.
Alameda, CA
kareem@isys.com
From Robert.J.Bollhorst@lmco.com  Wed Nov  5 17:19:19 1997
From: Robert J Bollhorst <Robert.J.Bollhorst@lmco.com>
Date: Wed Nov  5 17:19:22 PST 1997
Subject: Re: taskSuspend/taskResume usage question
--PART.BOUNDARY.phad.710d.34611b11.0001
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Dale,
     You're close, but I would suggest that you investigate using a Counting
Semaphore (see semCLib).  Instead of calling taskSuspend and taskResume, you
would simply call semTake and semGive, respectively.  This, I believe, will
be much more efficient than suspending/resuming a task.  Read the last
paragraph of the taskSuspend description.
     Hope that helps!  :-)
     Bob Bollhorst
     Lockheed Martin Corp.
     Aero & Naval Systems
     Middle River, MD
     Robert.J.Bollhorst@lmco.com
----------------------------------------------------------------------------
Submitted-by d.luck@ieee.org  Wed Nov  5 11:19:46 1997
Submitted-by: Dale Luck <d.luck@ieee.org>
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Is taskSuspend/taskResume quicker to use then other methods for restarting a
task?
I have a device that when it interrupts requires about 1millisecond of
processing to
exchange data withit. I have to do this every 5msecs.
This meant that I was holding off interrupts for 1msec every 5 msecs. Which
adversely
affected the serial port (running at 38400) as well as other devices.
So I've moved almost the entire code to a separate thread which basically looks
like this.
DeviceThread(void)
{
        while (1)
        {
                /* go to sleep waiting to be woke up by interrupt */
                taskSuspend(0);
                /* Woke up */
                While (worktodo)
                {
                        /* do all the messy work with interrupts enabled */
                }
        }
}
InterruptRoutine(void)
{
        AckTheInterrupt();
        taskResume(DeviceThreadID);
}
Questions:
Is there a counter for Suspend/Resume?
If so can the interrupt routine call taskResume more than once and the
Device thread will only actually Suspend itself when it gets back to zero?
Is there a better/faster way to do this?
Dale Luck
--MimeMultipartBoundary--
--PART.BOUNDARY.phad.710d.34611b11.0001
Content-Type: application/octet-stream; name="ATTACH01."
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="ATTACH01."
Content-Description: ATTACH01.
FTBP-Modification-Date: 06 Nov 1997 01:19:00 Z
FTBP-Object-Size: 1493
U3VibWl0dGVkLWJ5IGQubHVja0BpZWVlLm9yZyAgV2VkIE5vdiAgNSAxMToxOTo0NiAxOTk3
DQpTdWJtaXR0ZWQtYnk6IERhbGUgTHVjayA8ZC5sdWNrQGllZWUub3JnPg0KDQotLU1pbWVN
dWx0aXBhcnRCb3VuZGFyeQ0KQ29udGVudC1UeXBlOiB0ZXh0L3BsYWluOyBjaGFyc2V0PSJ1
cy1hc2NpaSINCkNvbnRlbnQtVHJhbnNmZXItRW5jb2Rpbmc6IDdiaXQNCg0KSXMgdGFza1N1
c3BlbmQvdGFza1Jlc3VtZSBxdWlja2VyIHRvIHVzZSB0aGVuIG90aGVyIG1ldGhvZHMgZm9y
IHJlc3RhcnRpbmcgYSB0YXNrPw0KDQpJIGhhdmUgYSBkZXZpY2UgdGhhdCB3aGVuIGl0IGlu
dGVycnVwdHMgcmVxdWlyZXMgYWJvdXQgMW1pbGxpc2Vjb25kIG9mIHByb2Nlc3NpbmcgdG8N
CmV4Y2hhbmdlIGRhdGEgd2l0aGl0LiBJIGhhdmUgdG8gZG8gdGhpcyBldmVyeSA1bXNlY3Mu
DQoNClRoaXMgbWVhbnQgdGhhdCBJIHdhcyBob2xkaW5nIG9mZiBpbnRlcnJ1cHRzIGZvciAx
bXNlYyBldmVyeSA1IG1zZWNzLiBXaGljaCBhZHZlcnNlbHkNCmFmZmVjdGVkIHRoZSBzZXJp
YWwgcG9ydCAocnVubmluZyBhdCAzODQwMCkgYXMgd2VsbCBhcyBvdGhlciBkZXZpY2VzLg0K
DQpTbyBJJ3ZlIG1vdmVkIGFsbW9zdCB0aGUgZW50aXJlIGNvZGUgdG8gYSBzZXBhcmF0ZSB0
aHJlYWQgd2hpY2ggYmFzaWNhbGx5IGxvb2tzIGxpa2UgdGhpcy4NCg0KRGV2aWNlVGhyZWFk
KHZvaWQpDQp7DQoJd2hpbGUgKDEpDQoJew0KCQkvKiBnbyB0byBzbGVlcCB3YWl0aW5nIHRv
IGJlIHdva2UgdXAgYnkgaW50ZXJydXB0ICovDQoJCXRhc2tTdXNwZW5kKDApOw0KCQkvKiBX
b2tlIHVwICovDQoJCVdoaWxlICh3b3JrdG9kbykNCgkJew0KCQkJLyogZG8gYWxsIHRoZSBt
ZXNzeSB3b3JrIHdpdGggaW50ZXJydXB0cyBlbmFibGVkICovDQoJCX0NCgl9DQp9DQoNCklu
dGVycnVwdFJvdXRpbmUodm9pZCkNCnsNCglBY2tUaGVJbnRlcnJ1cHQoKTsNCgl0YXNrUmVz
dW1lKERldmljZVRocmVhZElEKTsNCn0NCg0KUXVlc3Rpb25zOg0KSXMgdGhlcmUgYSBjb3Vu
dGVyIGZvciBTdXNwZW5kL1Jlc3VtZT8NCklmIHNvIGNhbiB0aGUgaW50ZXJydXB0IHJvdXRp
bmUgY2FsbCB0YXNrUmVzdW1lIG1vcmUgdGhhbiBvbmNlIGFuZCB0aGUNCkRldmljZSB0aHJl
YWQgd2lsbCBvbmx5IGFjdHVhbGx5IFN1c3BlbmQgaXRzZWxmIHdoZW4gaXQgZ2V0cyBiYWNr
IHRvIHplcm8/DQoNCklzIHRoZXJlIGEgYmV0dGVyL2Zhc3RlciB3YXkgdG8gZG8gdGhpcz8N
Cg0KRGFsZSBMdWNrDQotLU1pbWVNdWx0aXBhcnRCb3VuZGFyeS0tDQoNCioqKioqKioqKioN
Cg0KICAgIFRoaXMgaXMgYSB1c2VyIGdyb3VwIG1haWxpbmcgbGlzdCBmb3IgdnhXb3JrcyBy
ZWxhdGVkIHRvcGljcw0KICAgIFN1Ym1pdCBhcnRpY2xlcyB0byB2eHdleHBsb0BsYmwuZ292
IGZvciAnZXhwbG9zaW9uJw0KICAgIFNlbmQgc3Vic2NyaXB0aW9uIHJlcXVlc3RzICYgY29t
bWVudHMgdG8gdnh3ZXhwbG8tcmVxdWVzdEBsYmwuZ292DQo=
--PART.BOUNDARY.phad.710d.34611b11.0001--
From eric_johnson@BayNetworks.COM  Wed Nov  5 17:24:20 1997
From: Eric Johnson <eric_johnson@BayNetworks.COM>
Date: Wed Nov  5 17:24:24 PST 1997
Subject: Need vxWorks telnet "out" code
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Does anyone out there have object or source code  for telneting out of a
vxWorks
target?  Also, has anyone written a remote shell daemon for vxWorks?
Thanks for any information,
Eric
--
Eric Johnson                      email:eric_johnson@baynetworks.com
Bay Networks, Rapid City Division voice:       415-237-8670
1215 Terra Bella Avenue           fax:         415-237-7388
Mountain View, CA 94043           http://www.rapid-city.com
--MimeMultipartBoundary--
From currie@ghg.net  Wed Nov  5 18:33:39 1997
From: currie@ghg.net (Alan Currie)
Date: Wed Nov  5 18:33:42 PST 1997
Subject: Re: taskSuspend/taskResume usage question
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
the vxWorks Users Group Exploder wrote:
>
> I'm not doing any taskSuspend/taskDelete calls, only taskResume.
> Is this still a problem?
>
If you are doing a taskResume, you must also be suspending the task.  I
would not do either in an interrupt service routine.  I like the
suggestion of giving/taking semaphores previously suggested.
--
                                           <|
    Alan, Debbie, and Amanda Currie         |___      ~~O  __O
    currie@ghgcorp.com     Houston, Tx      |~~@\   _-\<,_-\<,_
    '96 Santana Arriva & Burley D'Lite      `(*)'--(*)/---|/-(*)
--MimeMultipartBoundary--
From d.luck@ieee.org  Wed Nov  5 20:01:29 1997
From: Dale Luck <d.luck@ieee.org>
Date: Wed Nov  5 20:01:32 PST 1997
Subject: RE: taskSuspend/taskResume usage question (thanks for the info)
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thanks for all your suggestions regarding Semaphores vs
Suspend/Resume. I'm now using the simple binary semaphores
and they are working as documented and solve the problem.
Thanks again,
Dale
--MimeMultipartBoundary--
From meitav@netvision.net.il  Wed Nov  5 23:33:37 1997
From: Irit <meitav@netvision.net.il>
Date: Wed Nov  5 23:33:41 PST 1997
Subject: Archive
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
I am looking for the URL address of the exploder archive .
e.g. all queries which were sent in the past to the exploder system
thanks
--MimeMultipartBoundary--
From daemon@csg.lbl.gov  Thu Nov  6 04:01:41 1997
From: daemon@csg.lbl.gov
Date: Thu Nov  6 04:01:44 PST 1997
Subject: comp.os.vxworks newsdigest
Comp.Os.Vxworks Daily Digest    Thu Nov  6 04:01:37 PST 1997
        Subject: Re: 2000 problem
        Subject: Re: 2000 problem
-------------------------------------------------------
Newsgroups: comp.os.vxworks,comp.realtime,comp.unix.programmer,comp.lang.c,comp.lang.c++
Subject: Re: 2000 problem
Date: 5 Nov 1997 00:03:58 GMT
From: seebs@plethora.net (Peter Seebach)
Organization: Plethora Internet
Message-ID: <63od5e$835$3@darla.visi.com>
References: <62fk8h$mjq@bcarh8ab.bnr.ca> <62np2n$e4t@dg-rtp.dg.com> <345E1269.628F95FE@webvision.com> <63o174$4e8@top.mitre.org>
In article <63o174$4e8@top.mitre.org>,
Michael F Brenner <mfb@mbunix.mitre.org> wrote:
>In particular, this shows why the twentieth century certainly
>does begin with the year 2000, not the year 2001. Anyone who
>says otherwise is using an arbitrary convention.
And anyone who says what you say is using an arbitrary convention.  Indeed,
anyone who isn't using the Hebrew calendar is using an arbitrary convention.
Hint:  The numbers are *ALL* arbitrary.
- -s
- --
seebs@plethora.net -- Speaking for myself.  No spam please.
Copyright 1997.  All rights reserved.  This was not written by my cat.
C/Unix wizard - send mail for help! -- <URL:http://www.plethora.net/~seebs>
<URL:http://www.plethora.net/> - More Net, Less Spam!
---------------------------
Newsgroups: comp.os.vxworks,comp.realtime,comp.unix.programmer,comp.lang.c,comp.lang.c++
Subject: Re: 2000 problem
Date: Mon, 03 Nov 1997 17:25:29 -0500
From: Robert Egan <nospam@ptc.com>
Message-ID: <345E4F59.41C6@ptc.com>
References: <62fk8h$mjq@bcarh8ab.bnr.ca> <62ijm7$qmu@bgtnsc02.worldnet.att.net> <344DCDF8.26351658@absyss.fr> <OzBgx$r48GA.289@nih2naac.prod2.compuserve.com> <M77Nmaz48GA.75@news2.ingr.com> <Pine.A41.3.95.971028190810.11082D-100000@acis.mc.yu.edu> <34596AB1.5237@ici.net> <63kic7$kka$1@route1.mdrf.france3.fr> <345DF05D.3FAF@ici.net> <345DF992.41C6@ptc.com> <345E0BBB.1EAC493E@calfp.co.uk>
The type of encapsulation you describe is not applicable to the COBOL
applications environment, where 95% (probably more) of the legacy code
was written. And in fact those were exactly the issues in the really old
COBOL environments. I was there, so I'm speaking from first hand
experience. And yes, I can remember when "core" was actually a "magnetic
core" and not just a program dump.
BTW: Other posters have raised an equally valid point, and that is life
expectancy. Given how fast systems change we never dreamed that our code
and data would last ten years, let alone thirty. If we had known, we
would have used all four digits regardless of other considerations.
Think about it. How many machines will be running Win 3.1 in the year
2015, or Win 95 in the year 2025?
There are so many guilty parties in this whole situation that it's
impossible to truly fix blame. I just bash management because they're a
convenient target.
Robert Egan
Nick Leaton wrote:
>
> The capacity and representation issue is not the problem. Representing
> data  with 2 digit years is not the issue. The real issue was people who cut
> and pasted or re-wrote all the code that used the representation. If it was
> properly encapsulated in some functions or procedures you would have an easy job
> of changing the functions. You would also have an easier job of finding and
> altering the data that uses 2 digit years.
>
- --
To reply by mail, set nospam ==> regan
---------------------------
End of New-News digest
**********************
From patrick_soulard@compuserve.com  Thu Nov  6 04:17:34 1997
From: Patrick SOULARD <patrick_soulard@compuserve.com>
Date: Thu Nov  6 04:17:37 PST 1997
Subject: FTP Server not allowing login
--MimeMultipartBoundary
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
Security option is enabled in FTP server.
Use loginUserAdd() before connecting.
-------------------------------------------------------------------------=
--
---
 Patrick SOULARD
 patrick_soulard@compuserve.com   COMPUSERVE: 100635,1717
 CEGELEC Division CGA (ALCATEL group)  BP 57  91229 Bretigny-sur-Orge =
FRANCE
-------------------------------------------------------------------------=
--
---
--MimeMultipartBoundary--
From jford@sadira.gb.nrao.edu  Thu Nov  6 05:15:37 1997
From: John Ford <jford@bara.gb.nrao.edu>
Date: Thu Nov  6 05:15:41 PST 1997
Subject: Re: Parity Errors
> Submitted-by kareem@isys.com  Wed Nov  5 16:58:01 1997
> Submitted-by: kareem@isys.com (Kareem Fawell)
>
> Hello:
>
> We are going to be moving from 68Ks on VME backplanes to generic PC's.
> Reliability is a concern, especially in terms of uptime, that is, how
> long can the PC run without a hardware error that can cause a software
> failure.  Would anyone have advice or comments about this?  Also, would
> ECC RAM be a sensible kind of RAM to use?
If I was concerned about reliability, I would not do this.  Especially
not move to a "generic PC".  A brand-name PC (Dell, Compaq, IBM, DEC,
HP) that is not in the bottom tier of thier product line might be
O.K, but you would need to burn-in every one, and test it at the
environmental extremes you expect your product to encounter.  This is
not usually a problem with VME based stuff, because it is designed
in.
Yet another problem is that you will have a hard time doing any sort
of configuration control of the hardware, as every time you buy
another machine you will likely end up with a slightly different
machine.  This is true of even the major vendors.
When you say "generic PC", that scares me.  If you buy a cheap
motherboard and fill it with cheap memory, you are in for a world of
trouble.  I think a lot of the bad press Windows gets is due to flaky
hardware.  The last 2 systems I bought had to have the cache memory
and at least one SIMM replaced due to random errors at runtime that
locked Windows, but just caused Linux programs to core dump.
Just my opinion.
John
From jford@sadira.gb.nrao.edu  Thu Nov  6 06:32:22 1997
From: John Ford <jford@bara.gb.nrao.edu>
Date: Thu Nov  6 06:32:26 PST 1997
Subject: mv167 and Tornado serial port question
Has anyone tried to make the CTS handshake line interrupt work?  I`m
looking at doing that, and I was hoping for some pointers.
Thanks!
--
John Ford
National Radio Astronomy Observatory
Green Bank, WV 24944-0002
jford@nrao.edu
From mmcquade@pop.aa.net  Thu Nov  6 09:07:13 1997
From: Mike McQuade <mmcquade@pop.aa.net>
Date: Thu Nov  6 09:07:17 PST 1997
Subject: Re: Parity Errors
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
At 05:15 AM 11/6/97 PST, you wrote:
>
>When you say "generic PC", that scares me.  If you buy a cheap
>motherboard and fill it with cheap memory, you are in for a world of
>trouble.  I think a lot of the bad press Windows gets is due to flaky
>hardware.  The last 2 systems I bought had to have the cache memory
>and at least one SIMM replaced due to random errors at runtime that
>locked Windows, but just caused Linux programs to core dump.
>
Well said, the term "Reliable" and "Generic PC" are mutually exclusive.
We needed very reliable hardware, we went with a Motorola PowerPC MVME-2603
board, now that we have about 25 instruments up and running, I can say
that we are happy with these boards, sure they may cost a little more
than "generic PC" hardware, but our instruments run continuous for
hours at a time, in harsh environments, at high VME interrupt rates.
Im sure PC hardware has its place.
Mike.
--MimeMultipartBoundary--
From currie@ghg.net  Thu Nov  6 09:26:58 1997
From: currie@ghg.net (Alan Currie)
Date: Thu Nov  6 09:27:02 PST 1997
Subject: Re: mv167 and Tornado serial port question
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
the vxWorks Users Group Exploder wrote:
>
> Submitted-by jford@sadira.gb.nrao.edu  Thu Nov  6 06:32:22 1997
> Submitted-by: John Ford <jford@bara.gb.nrao.edu>
>
> Has anyone tried to make the CTS handshake line interrupt work?  I`m
> looking at doing that, and I was hoping for some pointers.
> Not all serial ports support hardware handshaking.  Check your
documentation.
--MimeMultipartBoundary--
From bawilson@llnl.gov  Thu Nov  6 13:26:24 1997
From: "Bruce A. Wilson" <bawilson@llnl.gov>
Date: Thu Nov  6 13:26:28 PST 1997
Subject: Re: Compact PCI support
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Gespac (www.gespac.com) has a PCIPPC series of 3U CompactPCI boards, too.
>> I know for sure that FORCE has a PowerPC based 3U CompactPCI
>> board and VxWorks/Tornado 1.0.1 support.
>> What I heard is that they will follow up soon with a 6U board
>> based on PowerPC.
>>
>> They have also a Intel based CompactPCI board, but I do not know
>> if they have VxWorks support for it. Maybe you can check it
>> with them directly.
>
>Tornado BSPs:
>Ziatech has two 6U boards: zt5510 & zt5520 Pentiums (+Pro x2) plus a 3U Enet.
>Radisys has a Pentium EPC-100 with 10/100Mbit Enet onboard.
>
--MimeMultipartBoundary--
From wong@vms.masd.northgrum.com  Thu Nov  6 13:27:34 1997
From: wong@vms.masd.northgrum.com (J. Pierre Wong)
Date: Thu Nov  6 13:27:37 PST 1997
Subject: Compact PCI SBCs
Here's the list of CompactPCI boards "uncomfirmed" supported by
vxWorks so far. Please feel free to correct/add to this list
and repost the list to the vxWorks exploder.
Thanks for all the responses...
Pierre Wong
wong@vms.masd.northgrum.com
Company                 Model           CPU Type        Contact
--------------------------------------------------------------------------
Gespac                  PCISYS-56       Pentium         www.gespac.com
Gespac                  PCIPPC-1        PowerPC         www.gespac.com
Alta Technology         SBC/P164        Alpha           www.altatech.com
Acuity Imaging          Unreleased                      tballant@acut.com
Smart Modular Technologies              MIPS R5000      www.smartm.com
Smart Modular Technologies Unreleased   PowerPC         www.smartm.com
Ziatech                 ZT5510          Pentium         www.ziatech.com
Ziatech                 ZT5520          Pentium Pro+    www.ziatech.com
RadiSys                 EPC-100         Pentium         www.radisys.com
Cyclone Microsystems    cPCI-940/1/2    i960            www.cyclone.com
OR Computers            CC4/5/6         x86/Pentium     www.or-computers.com
OR Computers            CR5/6           Pentium/Pro     www.or-computers.com
Force Computers         CPCI-360x       PowerPC         www.forcecomputers.com
Force Computers         CPCI-520        Sparc           www.forcecomputers.com
Force Computers         CPCI-720        Pentium         www.forcecomputers.com
Motorola                MPC750          PowerPC         www.mot.com
VI Computers            4e              PowerPC         www.vicomp.com
From laksh@pvdsw.amat.com  Thu Nov  6 20:26:48 1997
From: laksh@pvdsw.amat.com (Laksh Karuppiah x33230)
Date: Thu Nov  6 20:26:53 PST 1997
Subject: Coff to a.out
We are looking for a consultant who could covert existing 68k code(motorlla format) to a.out format. We are currently using greenhills tools for a proprietry real time os. The format is oasys/coff format. We wouldlike to use greenhills vxworks/greenhill
tool environment with their MULTI debug tools. This requires a.out format using gnu's 68k assembler. If anyone is interested please call 408-563-3230 . The greenhills tools is working well for us to date.
-Laksh
Applied MAterials
From rajgopal@sonicsys.stph.net  Thu Nov  6 23:57:59 1997
From: "M.Raj Gopal" <rajgopal@sonicsys.stph.net>
Date: Thu Nov  6 23:58:30 PST 1997
Subject: Re:
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Remove my account from the list <rajgopal@sonicsys.stph.net>
M.RajGopal
Sonic Sofware Systems (India) Pvt. Ltd.
--MimeMultipartBoundary--
From espin@idiom.com  Wed Nov  5 16:24:50 1997
From: Geoffrey Espin <espin@idiom.com>
Date: Fri Nov  7 01:03:01 PST 1997
Subject: Re: Compact PCI support
--MimeMultipartBoundary
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Pierre,
> I know for sure that FORCE has a PowerPC based 3U CompactPCI
> board and VxWorks/Tornado 1.0.1 support.
> What I heard is that they will follow up soon with a 6U board
> based on PowerPC.
>
> They have also a Intel based CompactPCI board, but I do not know
> if they have VxWorks support for it. Maybe you can check it
> with them directly.
Tornado BSPs:
Ziatech has two 6U boards: zt5510 & zt5520 Pentiums (+Pro x2) plus a 3U Enet.
Radisys has a Pentium EPC-100 with 10/100Mbit Enet onboard.
Check their respective web-sites for contact info.
Geoff
--
Geoffrey Espin espin@idiom.com
--MimeMultipartBoundary--
From lars.antback@pullmax.se  Fri Nov  7 01:02:58 1997
Received: from lbl.gov by csg.lbl.gov (4.1/0.0)
	id AA23257; Fri, 7 Nov 97 01:02:58 PST
Received: from mn1.swip.net by lbl.gov (SMI-8.6/SMI-SVR4)
	id BAA26672; Fri, 7 Nov 1997 01:02:52 -0800
From: lars.antback@pullmax.se
Received: by mn1.swip.net (8.8.8/2.01)
	id IAA20098; Fri, 7 Nov 1997 08:47:31 GMT
Message-Id: <199711070847.IAA20098@mn1.swip.net>
Date: Fri, 7 Nov 1997 9:39:28 +0100
To: vxwexplo@lbl.gov (the vxWorks Users Group Exploder)
Subject: How to catch crash info
X-Mailer: TFS Gateway /220000000/220040016/220000029/220090004/
Hi All !
I am trying to implement a exception monitor on MVME2603 to catch all
unhandled exceptions and display information within my application to the
user. The basic idea is to collect information about the excepting task
and display it via our user interface so that the end user may call us
and identify what happend. I would like to produce the same type of data
as is shown on the console when running in the development environment,
i.e. information about task, crashing function and also the caller stack.
A short sample is shown below:
alignment
program counter:  0xffed38
access address:   0x2001
machine status:   0xb130
170b8c   vxTaskEntry    +60 : f_crash__Fv ([])
Note, normally a caller stack is display to identify how the crashed
function was called, it is not present in my short example.
I have solved the problem to catch execptions but is there any built in
function to retreive the crashed function name and the caller stack info
that is displayed ?
/Ant
             ////
            (0 0)
 _______o00o_( )_o00o_______
/                           \
| Lars Antbck              |
| Pullmax AB                |
| tel: +46 31 57 07 00      |
| email: ant@pullmax.se     |
\___________________________/
From mam@pluto.dspt.com  Fri Nov  7 11:06:47 1997
From: "Mark Menge" <mam@pluto.dspt.com>
Date: Fri Nov  7 11:06:51 PST 1997
Subject: Is it possible to store Processor Exceptions?
I have been trying to design a good processor exception handler that
puts the exception into non-volatile ram and allows an uploading to the
customer's disk after a reboot.
vxWorks claims that sysExcMsg is the location that the messages are
written into.  So why doesn't this work?
-> sp -1
task spawned: id = 0x349270, name = t18
value = 3445360 = 0x349270
->
Address Error
Program Counter: 0x000d90f4
Status Register: 0x3000
Access Address : 0xfffffffe
Task: 0x349270 "t18"
-> sysExcMsg
_sysExcMsg = 0x130052: value = 2048 = 0x800
-> d sysExcMsg
00000800:  0000 0000 0000 0000 0000 0000 0000 0000
*................*
???
From msa@redifon.com  Fri Nov  7 11:12:12 1997
From: Mark Armstrong <msa@redifon.com>
Date: Fri Nov  7 11:12:16 PST 1997
Subject: MVME162 STAT light failure
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hello everyone,
	I'm just about to start debugging a system using the MVME162
and the 68040 processor.  A set of these boards receive serial data
via Greenspring MP-IPSerial modules and a large amount of register
and FIFO interrogation takes place to these IP modules.
Under certain input signal conditions, the MVME162 fails with the
STAT light illuminated.  This LED indicates that a halt condition
exists in the MC68040 processor by decoding the status lines from
that chip. No more interaction can take place with the processor
until a reset occurs.
Does anyone have any experience of the kind of software problem
that could cause this result?
Hope someone can give me a hint.
Mark Armstrong
Redifon MEL Ltd
--MimeMultipartBoundary--
From POST@IMS.fhg.de  Fri Nov  7 11:39:38 1997
From: Rainer Stelzer <POST@IMS.mailgw1.fhg.de>
Date: Fri Nov  7 11:39:42 PST 1997
Subject: vxworks jpeg porting
Hi,
I am trying to use the JPEG Library version 6a in an
VXWorks application .
The application runs on an embedded system where no disk drives
are available. The application gets pictures from a camera and uses
its own HTTP-Server providing them in the internet.
At compile time i include jmemnobs.c as memory manager to suppress
i/o instructions.
Using the library in my application problems occure due to memory
management.
My Questions are:
1. Do you have any experience using the jpeg library with the operating
   system VXWorks?
2. Is it possible to use the jmemnobs.c as memory manager on VXWorks?
3. I only need the JPEG Software to get a picture file format that a
   browser can use(Netscape or Internet Explorer).
	My picture is stored in the PBM (Portable Bitmap) format.
	Is there a easier way to archieve this aim?
Please remail. Thanks a lot!
--
**********************************************************************
fraunhofer institute of microelectronic circuits and systems
department sat
name       rainer stelzer
address    finkenstrasse 61
           47057 duisburg
           germany
phone      +0049/203/3783-238
fax        +0049/203/3783-266
email      rstelzer@ims.fhg.de
**********************************************************************
From Huang.Wu@nrc.ca  Fri Nov  7 12:22:39 1997
From: "Wu, Huang" <Huang.Wu@nrc.ca>
Date: Fri Nov  7 12:22:43 PST 1997
Subject: to catch interrupts
--MimeMultipartBoundary
Content-Type: text/plain
Hello, there,
I am working on an Acromag A/D 9325 board for vxworks 5.3 (in
vme167, MC68040). I am tring to use the interrupt generated by
the board to wake up a process after data acquisition flag is set. The
board interrupt level is set to be level 5; and the global interrupt
BIT is enabled.  The code is like:
SEM_ID syncSem;
void Main_process()
{
	  interrupt.vector=200;/* initialize the board */
	  syncSem=semCCreate(SEM_Q_FIFO,SEM_EMPTY);
	while(1)
	 {
	intConnect(INUM_TO_IVEC(200),myInterrupt,0);
	/* enable global interrupt bit after data acquisition)
	...
	semTake(syncSem,WAIT_FOREVER);
	/* write: process is waken up */
	  }
}
void myInterrupt()
{
  semGive(syncSem);
}
But  the main process is not catching the interrupt, and
I am wondering whether someone can give me some light to show how
vxworks
deals with interrupts. I am using driver and application code at same
level in this case, and it seems to me I should link the interrupt
vector
and interrupt level somehow, which is not clear to me.I have checked the
acqusition complete flag which is indeed set in seconds.
Any suggestions are greatly appreciated!!
Huang
huang.wu@nrc.ca
--MimeMultipartBoundary--
From wbrown@csg.lbl.gov  Fri Nov  7 12:57:03 1997
From: wbrown@csg.lbl.gov (Bill Brown)
Date: Fri Nov  7 12:57:06 PST 1997
Subject: Re: to catch interrupts
Take a look at sysIntEnable().
Disclaimer:  Any opinions are my own and have	    |  -bill
    nothing to do with the official policy or the   |   wlbrown@lbl.gov
    management of L.B.N.L, who probably couldn't    |   Berkeley, CA
    care less about employees who play with trains. |   aka wlbrown@netcom.com
From Richard_W_Mattox@ccmail.orl.lmco.com  Fri Nov  7 14:09:12 1997
From: Richard_W_Mattox@ccmail.orl.lmco.com
Date: Fri Nov  7 14:09:16 PST 1997
Subject: i960rp problems
--MimeMultipartBoundary
Content-type: TEXT/PLAIN
Content-transfer-encoding: 7BIT
Hello Fellow VxWorkers,
We are developing a custom ATM NIC with an i960rp with the PMC Sierra LASAR ATM
chip set.  We are having difficulty in getting the processor to come up.  Does
anyone have any experience in developing an i960rp processor board who could
help?  The processor jumps to the invalid operation fault immediately after
executing the first instruction.  The instruction is valid as seen by a logic
analyzer.  Anyone have any suggestions?
TIA,
Rick Mattox
richard.w.mattox@lmco.com
--MimeMultipartBoundary--
From egbert@ra.timeplex.com  Fri Nov  7 16:50:46 1997
From: egbert@ra.timeplex.com (Stephen L. Egbert)
Date: Fri Nov  7 16:50:49 PST 1997
Subject: Re: i960rp problems
--MimeMultipartBoundary
Content-type: TEXT/PLAIN
> We are developing a custom ATM NIC with an i960rp with the PMC Sierra LASAR ATM
> chip set.  We are having difficulty in getting the processor to come up.  Does
> anyone have any experience in developing an i960rp processor board who could
> help?  The processor jumps to the invalid operation fault immediately after
> executing the first instruction.  The instruction is valid as seen by a logic
> analyzer.  Anyone have any suggestions?
>
> TIA,
> Rick Mattox
Usually this is an indication of several things, one of which I've experienced:
1. Core initialization Block has an invalid IP address (which in turns points to
   an invalid opcode.
2. Checksum of Initialization Block is invalid.
Stephen (Steve) L. Egbert              Work: (214) 340-3300
ascom Timeplex                          Fax: (214) 341-3654
Dallas, Texas 75243-7095                Net: egbert @ ra.timeplex.com
        Linux O/S: Vilius, fortius, centius quam Microsoft
--MimeMultipartBoundary--
From daemon@csg.lbl.gov  Sat Nov  8 04:02:26 1997
From: daemon@csg.lbl.gov
Date: Sat Nov  8 04:02:29 PST 1997
Subject: comp.os.vxworks newsdigest
Comp.Os.Vxworks Daily Digest    Sat Nov  8 04:02:23 PST 1997
        Subject: Re: 2000 problem
        Subject: Re: VxWorks 5.2 To Tornado Conversion Questions
-------------------------------------------------------
Newsgroups: comp.os.vxworks,comp.realtime,comp.unix.programmer,comp.lang.c,comp.lang.c++
Subject: Re: 2000 problem
Date: 31 Oct 1997 16:18:17 -0600
From: madings@earth.execpc.com (Steve Mading)
Organization: ExecPC -- (800)-EXECPC-1
Message-ID: <63dlf9$354$1@earth.execpc.com>
References: <62fk8h$mjq@bcarh8ab.bnr.ca> <ckoyb3aljun.fsf@systems.dhl.com>
Followup-To: comp.os.vxworks,comp.realtime,comp.unix.programmer,comp.lang.c,comp.lang.c++
Chris Waters (cwaters@systems.dhl.com) wrote:
: boyd@france3.fr (Boyd Roberts) writes:
: > The real problem with the the year 2000 is that there are too many zero
: > bits and that adversely affects the global bit density.
: And as for binary representations, like C's time_t, why are we going
: to have overflow in 2038?  Wouldn't 20_4_8 make more sense?
time_t measures # of seconds since 1970 (presumably this is when
C's time_t was invented).  It just so turns out that 2^32 seconds
after 1970 puts you into the year 2038.  So with most machines
measuring time_t in 32-bit numbers, they will fall over on 2038.
Of course, the easy solution is to just change time_t so it is
a 64-bit int instead, and any well-written software should be able
to handle it with just a recompile.
(Actually, it might be 2^31 seconds, not 2^32 seconds.  I think
that time_t might be a signed integer.)
- --
Steve Mading:  madings@execpc.com   http://www.execpc.com/~madings
---------------------------
Newsgroups: comp.os.vxworks
Subject: Re: VxWorks 5.2 To Tornado Conversion Questions
Date: 7 Nov 1997 11:53:52 -0700
From: bgeer@xmission.xmission.com (bgeer)
Organization: XMission Internet (801 539 0900)
Message-ID: <63vo40$7va$1@xmission.xmission.com>
References: <346734db.9739306@news01.cahners.com>
JLally@DRC.COM (Jim Lally) writes:
 >The sub-contractors are now assessing the replacement of VxWorks 5.2
 >with Tornado (VxWorks 5.3.1).  Our customer is reluctant to authorize
 >conversion to Tornado
 >Could you please identify any problems you had with the Wind Micro
 >kernel between 5.2 and 5.3.1?
I've ported 5.2 stuff to 5.3 [not using Launcher] by merely tweaking
my Makefiles to use the 5.3.0 directory tree.  I don't remember any
particular problems, so if there were any, they must be trivial.
I'm starting to use Launcher & Configuration Tool because everyone
else around here thinks it's wonderful.  It provides useful support
for configuring & building network loadable development kernels, &
makes linking applications modules to the kernel easier.
But I still had to tweak the Makefile & run "make" from the command
line to build FlashROM'able kernels & bootroms.
 >How successful was your conversion?  Can you identify any problems you
 >had with target components?
Not so far.
I don't have answers to your other questions for one reason or
another.
- --
<> Robert Geer & Donna Tomky /              *             <>
<>    bgeer@xmission.com    |    _o      *   o *      o   <>
<>   Salt Lake City, Utah   |   -\<,      * <\      </L   <>
<>          U S A           |   O/ O     __ /__,    />    <>
---------------------------
End of New-News digest
**********************
From System_Administrator@postal.essd.northgrum.com  Sat Nov  8 06:34:54 1997
From: System_Administrator@postal.essd.northgrum.com (System Administrator)
Date: Sat Nov  8 06:34:57 PST 1997
Subject: Undeliverable: comp.os.vxworks newsdigest
--MimeMultipartBoundary
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Your message was not delivered to all recipients.
     Subject:  comp.os.vxworks newsdigest
     Sent:     11/8/97 4:02:00 AM
The message was not delivered to the following receipient(s):
     KEVIN T Exchange MCARDLE
     The recipient name is not recognized
     MSEXCH:MSExchangeMTA:CA002:XCGCA014
--MimeMultipartBoundary--
From System_Administrator@postal.essd.northgrum.com  Sat Nov  8 08:33:51 1997
From: System_Administrator@postal.essd.northgrum.com (System Administrator)
Date: Sat Nov  8 08:33:55 PST 1997
Subject: Undeliverable: Undeliverable: comp.os.vxworks newsdigest
--MimeMultipartBoundary
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Your message was not delivered to all recipients.
     Subject:  Undeliverable: comp.os.vxworks newsdigest
     Sent:     11/8/97 6:34:00 AM
The message was not delivered to the following receipient(s):
     KEVIN T Exchange MCARDLE
     The recipient name is not recognized
     MSEXCH:MSExchangeMTA:CA002:XCGCA014
--MimeMultipartBoundary--
From System_Administrator@postal.essd.northgrum.com  Sat Nov  8 10:33:34 1997
From: System_Administrator@postal.essd.northgrum.com (System Administrator)
Date: Sat Nov  8 10:33:37 PST 1997
Subject: Undeliverable: Undeliverable: Undeliverable: comp.os.vxworks
--MimeMultipartBoundary
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Your message was not delivered to all recipients.
     Subject:  Undeliverable: Undeliverable: comp.os.vxworks newsdigest
     Sent:     11/8/97 8:33:00 AM
The message was not delivered to the following receipient(s):
     KEVIN T Exchange MCARDLE
     The recipient name is not recognized
     MSEXCH:MSExchangeMTA:CA002:XCGCA014
--MimeMultipartBoundary--
From System_Administrator@postal.essd.northgrum.com  Sat Nov  8 12:22:49 1997
From: System_Administrator@postal.essd.northgrum.com (System Administrator)
Date: Sat Nov  8 12:22:53 PST 1997
Subject: Undeliverable: Undeliverable: Undeliverable: Undeliverable:
--MimeMultipartBoundary
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Your message was not delivered to all recipients.
     Subject:  Undeliverable: Undeliverable: Undeliverable: comp.os.vxworks
     Sent:     11/8/97 10:33:00 AM
The message was not delivered to the following receipient(s):
     KEVIN T Exchange MCARDLE
     The recipient name is not recognized
     MSEXCH:MSExchangeMTA:CA002:XCGCA014
--MimeMultipartBoundary--
From System_Administrator@postal.essd.northgrum.com  Sat Nov  8 14:16:21 1997
From: System_Administrator@postal.essd.northgrum.com (System Administrator)
Date: Sat Nov  8 14:16:24 PST 1997
Subject: Undeliverable: Undeliverable: Undeliverable: Undeliverable:
--MimeMultipartBoundary
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Your message was not delivered to all recipients.
     Subject:  Undeliverable: Undeliverable: Undeliverable: Undeliverable:
     Sent:     11/8/97 12:22:00 PM
The message was not delivered to the following receipient(s):
     KEVIN T Exchange MCARDLE
     The recipient name is not recognized
     MSEXCH:MSExchangeMTA:CA002:XCGCA014
--MimeMultipartBoundary--
From System_Administrator@postal.essd.northgrum.com  Sat Nov  8 15:57:45 1997
From: System_Administrator@postal.essd.northgrum.com (System Administrator)
Date: Sat Nov  8 15:57:49 PST 1997
Subject: Undeliverable: Undeliverable: Undeliverable: Undeliverable:
--MimeMultipartBoundary
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Your message was not delivered to all recipients.
     Subject:  Undeliverable: Undeliverable: Undeliverable: Undeliverable:
     Sent:     11/8/97 2:16:00 PM
The message was not delivered to the following receipient(s):
     KEVIN T Exchange MCARDLE
     The recipient name is not recognized
     MSEXCH:MSExchangeMTA:CA002:XCGCA014
--MimeMultipartBoundary--
From daemon@csg.lbl.gov  Mon Nov 10 04:00:55 1997
From: daemon@csg.lbl.gov
Date: Mon Nov 10 04:00:59 PST 1997
Subject: comp.os.vxworks newsdigest
Comp.Os.Vxworks Daily Digest    Mon Nov 10 04:00:51 PST 1997
        Subject: Re: 2000 problem
-------------------------------------------------------
Newsgroups: comp.os.vxworks,comp.realtime,comp.unix.programmer,comp.lang.c,comp.lang.c++
Subject: Re: 2000 problem
Date: 4 Nov 1997 14:31:20 +0100
From: kanze@gabi-soft.fr (J. Kanze)
Organization: GABI Software, S`rl.
Message-ID: <m3bu00yeed.fsf@gabi-soft.fr>
References: <62fk8h$mjq@bcarh8ab.bnr.ca> <ckoyb3aljun.fsf@systems.dhl.com>
	<63dlf9$354$1@earth.execpc.com>
madings@earth.execpc.com (Steve Mading) writes:
|>  Chris Waters (cwaters@systems.dhl.com) wrote:
|>  : boyd@france3.fr (Boyd Roberts) writes:
|>
|>  : > The real problem with the the year 2000 is that there are too many zero
|>  : > bits and that adversely affects the global bit density.
|>
|>  : And as for binary representations, like C's time_t, why are we going
|>  : to have overflow in 2038?  Wouldn't 20_4_8 make more sense?
|>
|>  time_t measures # of seconds since 1970 (presumably this is when
|>  C's time_t was invented).  It just so turns out that 2^32 seconds
|>  after 1970 puts you into the year 2038.  So with most machines
|>  measuring time_t in 32-bit numbers, they will fall over on 2038.
|>  Of course, the easy solution is to just change time_t so it is
|>  a 64-bit int instead, and any well-written software should be able
|>  to handle it with just a recompile.
After which, it won't be able to read all of the files written before
with 32 bit timestamps.
Converting programs is (or should be) trivial.  Except that said
programs still have to read files written with the old format.
|>  (Actually, it might be 2^31 seconds, not 2^32 seconds.  I think
|>  that time_t might be a signed integer.)
It is.
- --
James Kanze    +33 (0)1 39 23 84 71    mailto: kanze@gabi-soft.fr
GABI Software, 22 rue Jacques-Lemercier, 78000 Versailles, France
        I'm looking for a job -- Je recherche du travail
---------------------------
End of New-News digest
**********************
From jbrandt@sadira.gb.nrao.edu  Mon Nov 10 05:40:53 1997
From: jbrandt@sadira.gb.nrao.edu (Joe Brandt)
Date: Mon Nov 10 05:40:58 PST 1997
Subject: Re: How to catch crash info
--4eca_2da6-23b9_64bd-6721_59c
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-MD5: JZQFGH5yaoWztVTe/kOkiA==
X-Sun-Data-Type: text
The solution is of course architecture & OS dependent. Attached are files
that work for SUNOS/sparc and MC68K/VxWorks.
The basic idea behind it all is to get the frame ptr, and walk the stack
back up to the top. To print out names of functions, us the symbol library.
The sparc architecture requires a trap to flush registers to ram, (hence the
getStackPtr.s file) the MC68k trace can be written in pure C/C++, other
architectures may require similar efforts.
Hope this helps
------------------------------------------------------------------------
    _/       _/   _/_/_/_/       _/           _/_/_/     National
   _/ _/    _/   _/      _/    _/ _/        _/     _/    Radio
  _/   _/  _/   _/_/_/_/      _/____/      _/     _/     Astronomy
 _/     _/_/   _/      _/    _/     _/    _/     _/      Observatory
_/       _/   _/        _/  _/       _/    _/_/_/        Green Bank, WV
Joe Brandt (N0NYO) N.R. EMT/FF          jbrandt@nrao.edu (304)456-2210
------------------------------------------------------------------------
--4eca_2da6-23b9_64bd-6721_59c
Content-Type: text/plain; charset=us-ascii; name=StackTracer.cc
Content-Transfer-Encoding: 7bit
Content-MD5: f3yoYoMJdmdehFl6OwGKiQ==
Content-Description: StackTracer.cc
Content-Disposition: attachment; filename=StackTracer.cc
// Copyright (C) 1994 Associated Universities, Inc. Washington DC, USA.
//
// This program is free software; you can redistribute it and/or modify
// it under the terms of the GNU General Public License as published by
// the Free Software Foundation; either version 2 of the License, or
// (at your option) any later version.
//
// This program is distributed in the hope that it will be useful, but
// WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
// General Public License for more details.
//
// You should have received a copy of the GNU General Public License
// along with this program; if not, write to the Free Software
// Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
//
// Correspondence concerning GBT software should be addressed as follows:
//	GBT Operations
//	National Radio Astronomy Observatory
//	P. O. Box 2
//	Green Bank, WV 24944-0002 USA
static char rcs_id[] =  "$Id: StackTracer.cc,v 1.7 1995/04/26 21:28:16 jbrandt Exp $";
// Derived from work done by:
//     1993-10-02 Lesley Stoa, CAP Programator AB.
//     Email: lesley@sypro.cap.se
#include "StackTracer.h"
// Standard includes
#include	<stdio.h>
#include	<stdlib.h>
#include	<string.h>
#ifdef SUNOS_4_BSD
#include	<a.out.h>
#include	<stab.h>
#endif
#ifdef SOLARIS2
#include <sys/elf.h>
#endif
#if defined(SUNOS_4_BSD) || defined(SOLARIS2)
#include	<strings.h>
#include	<ctype.h>
#include	<sys/types.h>
#include	<sys/file.h>
#include	<link.h>
#include	<unistd.h>
#endif
#ifdef VXWORKS
#include    <symLib.h>
#include    <taskLib.h>
#endif
#include "StackListing.h"
#ifdef __cplusplus
extern "C" unsigned long getStackPointer();
#endif
StackTracer::StackTracer() :
    stack_start(0), stack_end(0), stack_tmp(0), stack_tmp2(0),
    argv(0), pname(0), symb_list(), no_of_symb(0), progFileName(0)
{
    progFileName = new char[512];
    memset(progFileName, 0, 512);
#if ! defined(SOLARIS2)
    memset((char *)&header, 0, sizeof(struct exec));
    memset((char *)&lheader, 0, sizeof(struct exec));
#endif
}
StackTracer::~StackTracer()
{
    if(progFileName) {
        delete progFileName;
        progFileName = 0;
    }
    if(stack_start) {
        StackType *tmpPtr;
        for(stack_tmp=stack_start; stack_tmp;) {
            tmpPtr = stack_tmp;
            stack_tmp = tmpPtr->next;
            delete tmpPtr;
        }
        stack_start = 0;
    }
}
StackType *
StackTracer::lookupSym(StackType *stk)
{
#if ! defined(VXWORKS) && !defined(SOLARIS2)
    /* SunOS4 Code */
int i;
    i = findSymIndex(stk->frame->fr_savpc);
    strcpy(stk->funcname, symb_list[i].n_un.n_name);
    stk->symValue = symb_list[i].n_value;
#elif defined(SOLARIS2)
    sprintf(stk->funcname, "0x%x", stk->frame->fr_savpc);
    stk->symValue = stk->frame->fr_savpc;
#else
    /* VXWORKS is defined */
    extern SYMTAB_ID sysSymTbl;
    SYM_TYPE ptype;
    symFindByValue(sysSymTbl,
                   (unsigned)stk->frame->fr_savpc,
                   stk->funcname,
                   (int *)&stk->symValue,
                   &ptype);
#endif
    return(stk);
}
#ifdef VXWORKS
static unsigned long get68kStkPtr(int a)
{
    return((unsigned long)((unsigned long *)(&a)[-2]));
}
unsigned long getStackPointer()
{
int a = 0;
frame *f = (frame *)get68kStkPtr(a);
    return((unsigned long)(f->fr_savfp));
}
#endif
#if !defined(VXWORKS) && !defined(SOLARIS2)
int
StackTracer::findSymIndex(unsigned long adr)
{
	int             i, n;
	if (adr > symb_list[no_of_symb - 1].n_value) {
		return(no_of_symb - 1);
	}
	if (adr <= symb_list[0].n_value) {
		return(0);
	}
	n = no_of_symb / 2 + 1;
	i = n - 1;
	do {
		if (adr >= symb_list[i].n_value && adr < symb_list[i + 1].n_value) {
			return(i);
		}
		if (n > 1) {
			n = n / 2;
		}
		if (adr > symb_list[i].n_value) {
			i += n;
		} else {
			i -= n;
		}
	} while (n > 1 || i >= 0);
	return(i >= 0 ? i : 0);
}
int
StackTracer::compar(nlist *a, nlist *b)
{
	unsigned long   i, j;
	i = a->n_value;
	j = b->n_value;
	if (i < j) {
		return -1;
	} else if (i > j) {
		return 1;
	} else {
		return 0;
	}
}
#endif
char *
StackTracer::taskExecFile(char *pname)
{
	FILE           *fp;
	int             ll;
	char           *path;
	char           *ptr, trial[512];
	/*---------------------------------*/
	/* get name of program */
	strcpy(progFileName, pname);
	/* 1: if progFileName contains a slash, assume it is the direct path */
	ptr = strchr(progFileName, '/');
	if (ptr != NULL) {
		fp = fopen(progFileName, "r");
		if (fp != NULL) {
			fclose(fp);
			return progFileName;
		}
	}
	/* 2: try the local directory */
	strcpy(trial, "./");
	strcat(trial, progFileName);
	fp = fopen(trial, "r");
	if (fp != NULL) {
		fclose(fp);
		strcpy(progFileName, trial);
		return progFileName;
	}
	/* 3: look in the user's path */
	ptr = getenv("PATH");
	ll = strlen(ptr);
	path = new char[ll + 1];
	strcpy(path, ptr);
	/* separate path string into its components */
	ptr = strtok(path, ":");
	while (ptr != NULL) {
		strcpy(trial, ptr);
		strcat(trial, "/");
		strcat(trial, progFileName);
		fp = fopen(trial, "r");
		if (fp != NULL) {
			fclose(fp);
			strcpy(progFileName, trial);
			delete path;
			return progFileName;
		}
		ptr = strtok((char *)NULL, ":");
	}
    delete path;
    return((char *)NULL);
}				/* end of taskExecFile */
#if !defined(VXWORKS) && !defined(SOLARIS2)
void
StackTracer::processSymTbl()
{
	FILE           *fp, *fp2;
	struct nlist    symbol;	/* symbol table entry */
	unsigned long   address, match, lastaddress;
	int             type, line, funcsymbol, filesymbol;
	int             i, ll, status;
	long            fileaddr, funcaddr;
	char           *ptr, ttext[256];
	char            funcname[256], filename[256];
	/*----------------------*/
	/* initialize */
	address = 0;
	funcsymbol = 0;
	filesymbol = 0;
	lastaddress = 0xFFFF;
	/* use first file pointer to read symbol table */
	fp = fopen(pname, "r");
	if (fp == NULL) {
		printf("can't open %s\n", pname);
		exit(1);
	}
	/* use second file pointer to read the string table */
	fp2 = fopen(pname, "r");
	/* read all symbols, look at source lines, file & function names */
	fseek(fp, N_SYMOFF(header), 0);
	for (i = 0; i < header.a_syms / sizeof(symbol); i++) {
		status = fread(&symbol, sizeof(symbol), 1, fp);
		if (status == 0)
			printf("could not read symbol\n");
		type = symbol.n_type;
		/* what type of symbol is it */
        switch(type) {
        case N_SLINE: /* src line: 0,,0,linenumber,address */
		    line = symbol.n_desc;
		    address = symbol.n_value;
        break;
        case N_FUN:   /* procedure: * name,,0,linenumber,address */
			funcaddr = symbol.n_un.n_strx;
			address = symbol.n_value;
			funcsymbol = i;
			fseek(fp2, N_STROFF(header), 0);
			fseek(fp2, funcaddr, 1);
			ptr = fgets(ttext, sizeof(ttext), fp2);
			ptr = strtok(ttext, ":");
			ll = strlen(ptr);
			if (ll > 250) {
				strncpy(funcname, ptr, 250);
				funcname[250] = NULL;
			} else
				strcpy(funcname, ptr);
        break;
        case N_SO:    /* source file name: * name,,0,0,address */
			fileaddr = symbol.n_un.n_strx;
			address = symbol.n_value;
			filesymbol = i;
			fseek(fp2, N_STROFF(header), 0);
			fseek(fp2, fileaddr, 1);
			ptr = fgets(filename, sizeof(filename), fp2);
        break;
        /* from stab.h */
        case N_GSYM:
        case N_FNAME:
        case N_STSYM:
        case N_LCSYM:
        case N_MAIN:
        case N_RSYM:
        case N_SSYM:
        case N_LSYM:
        case N_BINCL:
        case N_SOL:
        case N_PSYM:
        case N_EINCL:
        case N_ENTRY:
        case N_LBRAC:
        case N_EXCL:
        case N_RBRAC:
        case N_BCOMM:
        case N_ECOMM:
        case N_ECOML:
        case N_LENG:
        default:
            /* This may not be an error */
        break;
		} /* end switch */
		/* does this address match one of ours? */
        for(stack_tmp = stack_start; stack_tmp->next;
            stack_tmp = stack_tmp->next) {
			if (!stack_tmp->found) {
				match = stack_tmp->frame->fr_savpc;
				if (address == match) {
					stack_tmp->found = 1;
                    /* store symbol# of the file */
					stack_tmp->filesymbol = filesymbol;
                    /* symbol# of the function */
					stack_tmp->funcsymbol = funcsymbol;
					strcpy(stack_tmp->funcname, funcname);
					strcpy(stack_tmp->filename, filename);
					stack_tmp->line = line;
				} else if (address > match && lastaddress < match && lastaddress > (match - 64)) {
					stack_tmp->found = 1;
                    /* store symbol# of the file */
					stack_tmp->filesymbol = filesymbol;
                    /* symbol# of the function */
					stack_tmp->funcsymbol = funcsymbol;
					strcpy(stack_tmp->funcname, funcname);
					strcpy(stack_tmp->filename, filename);
					stack_tmp->line = line - 1;
				}
			}
		}
		lastaddress = address;
	}	/* end of loop over all nsym */
	fclose(fp2);
	fclose(fp);
}	/* end of processSymTbl */
nlist *
StackTracer::readSymbols(char *pname)
{
	FILE           *fdcore, *fdsyms;
	struct link_map *map_ent;
	long            symoff, stroff;
	int             symsize, i, j;
	char            name[256];
	int             len;
	if (!symb_list.list()) {
		// printf("Reading symbols... ");
		fflush(stdout);
		fdcore = fopen(pname, "r");
		if (fdcore == NULL) {
			fprintf(stderr, "Can't find %s.\n", pname);
			exit(1);
		}
		fdsyms = fopen(pname, "r");
		if (fdsyms == NULL) {
			fprintf(stderr, "Can't find %s.\n", pname);
			exit(1);
		}
		fread(&header, sizeof(struct exec), 1, fdcore);
		symoff = (long) N_SYMOFF(header);
		stroff = (long) N_STROFF(header);
		if (header.a_syms == 0) {
			fprintf(stderr, "Sorry, no symbol table exist. File is striped!\n");
		}
		symsize = (int)(header.a_syms / sizeof(struct nlist));
		fseek(fdcore, symoff, 0);
		// symb_list = (struct nlist *) malloc((int)header.a_syms);
		no_of_symb = 0;
		j = 0;
		for (i = 0; i < symsize; i++) {
			fread(&symb_list[no_of_symb], sizeof(struct nlist), 1, fdcore);
			if (symb_list[no_of_symb].n_type ==  N_TEXT ||
               (symb_list[no_of_symb].n_type == (N_TEXT | N_EXT))) {
				fseek(fdsyms, stroff + symb_list[no_of_symb].n_un.n_strx, 0);
				fgets(name, 255, fdsyms);
				len = strlen(name);
                /* Skip fileName labels */
				if (len >= 2 && !strcmp(&name[len - 2], ".o")) {
                    symb_list[no_of_symb].n_un.n_strx = 0;
					continue;
				}
				symb_list[no_of_symb].n_un.n_name = new char [len+1];
				if (*name == '_') {
					strcpy(symb_list[no_of_symb].n_un.n_name, &name[1]);
				} else {
					strcpy(symb_list[no_of_symb].n_un.n_name, name);
				}
				no_of_symb++;
				j++;
			} else {
                symb_list[no_of_symb].n_un.n_strx = 0;
            }
		}
		// printf("%d ", j);
		fflush(stdout);
		// symb_list = (struct nlist *) realloc(symb_list, no_of_symb * sizeof(struct nlist));
		fclose(fdcore);
		fclose(fdsyms);
		if (_DYNAMIC != NULL) {
			map_ent = (struct link_map *) _DYNAMIC[9];
		} else {
			map_ent = NULL;
		}
		while (map_ent) {
            // cache a copy of lm_addr to prevent thousands of errors from
            // testcenter about accessing illegal memory (sigh)
            char *lm_addr = map_ent->lm_addr;
			fdcore = fopen(map_ent->lm_name, "r");
			if (fdcore == NULL) {
				fprintf(stderr, "Can't find %s.\n", map_ent->lm_name);
				exit(1);
			}
			fdsyms = fopen(map_ent->lm_name, "r");
			if (fdsyms == NULL) {
				fprintf(stderr, "Can't find %s.\n", map_ent->lm_name);
				exit(1);
			}
			fread(&lheader, sizeof(struct exec), 1, fdcore);
			symoff = (long) N_SYMOFF(lheader);
			stroff = (long) N_STROFF(lheader);
			if (lheader.a_syms == 0) {
				fprintf(stderr, "Sorry, no symbol table exist. File is striped!\n");
			}
			symsize = (int)(lheader.a_syms / sizeof(struct nlist));
			fseek(fdcore, symoff, 0);
			// symb_list = (struct nlist *)
            //             realloc(symb_list,
            //              (int)(no_of_symb * sizeof(struct nlist) +
            //                    lheader.a_syms));
			j = 0;
			for (i = 0; i < symsize; i++) {
				fread(&symb_list[no_of_symb], sizeof(struct nlist), 1, fdcore);
				if (symb_list[no_of_symb].n_type == N_TEXT ||
                    symb_list[no_of_symb].n_type == (N_TEXT | N_EXT)) {
					fseek(fdsyms, stroff + symb_list[no_of_symb].n_un.n_strx, 0);
					fgets(name, 255, fdsyms);
					len = strlen(name);
					if (len >= 2 && !strcmp(&name[len - 2], ".o")) {
                        symb_list[no_of_symb].n_un.n_strx = 0;
						continue;
					}
					symb_list[no_of_symb].n_un.n_name = new char [len+1];
					if (*name == '_') {
						strcpy(symb_list[no_of_symb].n_un.n_name, &name[1]);
					} else {
						strcpy(symb_list[no_of_symb].n_un.n_name, name);
					}
					symb_list[no_of_symb].n_value += (unsigned int)lm_addr;
					no_of_symb++;
					j++;
				} else {
                    symb_list[no_of_symb].n_un.n_strx = 0;
                }
			}
			// printf("+ %d ", j);
			fflush(stdout);
			// symb_list = (struct nlist *) realloc(symb_list, no_of_symb * sizeof(struct nlist));
            // symb_list = new nlist[no_of_symb];
			fclose(fdcore);
			fclose(fdsyms);
			map_ent = map_ent->lm_next;
		}
		// printf("= %d symbols read.\n", no_of_symb);
		qsort(symb_list.list(), no_of_symb, sizeof(struct nlist),
              (int (*)(const void *, const void *))StackTracer::compar);
	    processSymTbl();
	}
    return(0);
}
/* endif ! VXWORKS */
#endif
StackListing *
StackTracer::traceStack()
{
	char            name[256];
    char            traceBuf[1024];
    if(stack_start) {
        StackType *tmpPtr;
        for(stack_tmp=stack_start; stack_tmp;) {
            tmpPtr = stack_tmp;
            stack_tmp = tmpPtr->next;
            delete tmpPtr;
        }
        stack_start = 0;
    }
	stack_start = stack_end = stack_tmp = stack_tmp2 = (StackType *)NULL;
    struct frame *fp;
	fp = (frame *)getStackPointer();
	while (fp) {
		stack_tmp =  new StackType();
        stack_tmp->frame = new frame();
        /* Stack Boundry Errors will occur here. This is OK since I need
         * to walk the stack upward past the current stack frame.
         * I copy (needlessly) the frames so that it only occurs here,
         * rather than have (literally thousands) of SBR's occuring
         * everywhere.  */
        memcpy((char *)stack_tmp->frame, (char *)fp, sizeof(frame));
        fp = stack_tmp->frame->fr_savfp;
		if (stack_start) {
			stack_end->next = stack_tmp;
			stack_tmp2 = stack_end;
			stack_end = stack_tmp;
		} else {
			stack_start = stack_end = stack_tmp;
		}
	}
#if !defined(VXWORKS)
    /* e.g. Sunos4 code */
    /* argv is the list of parameters passed into main. argv[0] should be
       the filename of the program (in almost all cases of well-behaved
       programs. (Some programs change argv[0]) */
    /* argv is located 100 bytes above the 2nd to last(top) stack frame */
    /* The top stack frame is actually from start() */
	argv = (char **)(stack_tmp2->frame->fr_savfp);
    argv += 100/sizeof(char **); /* 100 bytes */
    /* Search for the executable */
	pname = taskExecFile(argv[0]);
	// printf("Programname = %s\n", pname);
#if ! defined(SOLARIS2)
    readSymbols(pname);
#endif
#elif defined(VXWORKS)
    pname = taskName(taskIdSelf());
#else
    pname = 0;
#endif
    StackListing *btrace = new StackListing(pname);
	stack_tmp = stack_start;
	while (stack_tmp->next) {
        stack_tmp2 = lookupSym(stack_tmp);
		stack_tmp = stack_tmp->next;
        btrace->addLevel(stack_tmp2->funcname,
                         (unsigned long *)&stack_tmp->frame->fr_arg[0],
                         stack_tmp2->frame->fr_savpc - stack_tmp2->symValue,
                         stack_tmp2->line);
	}
	return(btrace);
}
void
StackTracer::printStack(ostream &os)
{
StackListing *traceb;
    os << "Backtrace:" << endl;
    traceb = traceStack();
#ifdef notdef
int i;
StackLevel *sp;
    for(i=0; i<traceb->depth(); i++) {
        sp = (*traceb)[i];
        /* This often results in UMR errors (uninitialized memory read)
         * This may result when there are fewer args than 5.
         * For now we ignore this warning. */
        os << sp->funcName << "("
           << sp->args[0]  << ", "
           << sp->args[1]  << ", "
           << sp->args[2]  << ", "
           << sp->args[3]  << ", "
           << sp->args[4]  << ", "
           << sp->args[5]  << ") + "
           << sp->offset  ;
#if ! defined(VXWORKS)
        if(sp->lineNo != 0)
           os << " at Line " << sp->lineNo ;
#endif
    }
#endif
        os << *traceb;
        os << endl;
    delete traceb;
}
StackType::StackType() : next(0), frame(0), found(0), filesymbol(0),
    funcsymbol(0), line(0), symValue(0)
{
}
StackType::~StackType()
{
    if(frame) {
        delete frame;
        frame = 0;
    }
}
SymbolList::~SymbolList()
{
int i;
    for(i=0; i<nSyms; i++) {
#if defined(SOLARIS2)
        if(symList[i].n_name) {
            delete [] symList[i].n_name;
            symList[i].n_name = 0;
#else
        if(symList[i].n_un.n_name) {
            delete [] symList[i].n_un.n_name;
            symList[i].n_un.n_name = 0;
#endif
        }
    }
    if(symList) {
        delete [] ((unsigned long *)symList);
        symList = 0;
    }
}
struct nlist &
SymbolList::operator[](int index)
{
struct nlist *newSyms;
    if(index < nSyms) {
        return(symList[index]);
    } else {
        if(!symList) {
            nSyms = index + 32;
            symList = (struct nlist *)new long[(nSyms)*(sizeof(struct nlist)/sizeof(long))];
            memset((char *)symList, 0, (nSyms) * sizeof(struct nlist));
        } else {
            newSyms = (struct nlist *)new long[(index+32)*(sizeof(struct nlist)/sizeof(long))];
            memcpy((char *)newSyms, (char *)symList,
                   nSyms * sizeof(struct nlist));
            memset((char *)&newSyms[nSyms], 0, (index-nSyms+32)*sizeof(struct
nlist));
            nSyms = index + 32;
            delete [] ((unsigned long *)symList);
            symList = newSyms;
        }
        return(symList[index]);
    }
}
--4eca_2da6-23b9_64bd-6721_59c
Content-Type: text/plain; charset=us-ascii; name=StackTracer.h
Content-Transfer-Encoding: 7bit
Content-MD5: INA69iUwZru5nWu3ukjiXQ==
Content-Description: StackTracer.h
Content-Disposition: attachment; filename=StackTracer.h
X-Sun-Data-Type: h-file
// Copyright (C) 1994 Associated Universities, Inc. Washington DC, USA.
//
// This program is free software; you can redistribute it and/or modify
// it under the terms of the GNU General Public License as published by
// the Free Software Foundation; either version 2 of the License, or
// (at your option) any later version.
//
// This program is distributed in the hope that it will be useful, but
// WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
// General Public License for more details.
//
// You should have received a copy of the GNU General Public License
// along with this program; if not, write to the Free Software
// Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
//
// Correspondence concerning GBT software should be addressed as follows:
//	GBT Operations
//	National Radio Astronomy Observatory
//	P. O. Box 2
//	Green Bank, WV 24944-0002 USA
#ifndef StackTracer_h
#define StackTracer_h
#if !defined(VXWORKS) && !defined(SOLARIS2)
#define SUNOS_4_BSD
#elif defined(SOLARIS2)
#define SUNOS_5_SVR4
// else VXWORKS
#endif
#include <iostream.h>
#include "StackListing.h"
/* Stack Frame definitions */
#ifdef CPU
#if CPU == MC68040 || CPU == MC68030
struct frame {
    struct frame *fr_savfp;  /* saved frame pointer */
    int fr_savpc;            /* saved program counter */
    int fr_arg[1];           /* array of arguments */
};
#endif
#elif defined(SUNOS_4_BSD)
#include <machine/frame.h>
#elif defined(SUNOS_5_SVR4)
#include <sys/frame.h>
#endif
#if defined(SUNOS_4_BSD)
    /* Sun Includes */
    /* For dynamically linked executables */
    extern unsigned long _DYNAMIC[];
#include <a.out.h>
#include <nlist.h>
#elif defined(SUNOS_5_SVR4)
#include<sys/types.h>
#include<sys/fcntl.h>
#include<fcntl.h>
#include <libelf.h>
#include <nlist.h>
// #include <sys/exec.h>
// #include <elf.h>
#else
    /* VXWORKS Includes */
#include <a_out.h>
#endif
extern char    *index();
struct xsym {
    char           *dat;
    int             lnum;
    int             lnum2;
    int             map;
    struct xsym    *nxt;
};
class StackType {
public:
    StackType();
   ~StackType();
    StackType *next;
    struct frame   *frame;
    char            funcname[256];  /* name of function */
    char            filename[256];  /* name of source file */
    int             found;  /* 0 if function not found */
    int             filesymbol; /* symbol # for start of source file */
    int             funcsymbol; /* symbol # for start of function */
    int             line;   /* line number in source file */
    unsigned long   symValue; /* address of found symbol */
};
class SymbolList {
public:
    SymbolList() : symList(0), nSyms(0) {}
   ~SymbolList();
    struct nlist &operator[](int index);
    struct nlist *list() { return symList; }
protected:
    struct nlist *symList;
    int nSyms;
};
class StackTracer {
public:
    StackTracer();
   ~StackTracer();
    // Trace the stack and send ostream
    void printStack(ostream &os = cout);
    // A ostream intelligent version. This performs a stack trace
    // where called.
    friend ostream &operator << (ostream&, StackTracer &);
    // Trace the stack and stuff in StackListing object
    // Note that it is the callers responsibility to delete the object
    // when completed
    StackListing *traceStack();
protected:
    int findSymIndex(unsigned long);
    static int compar(struct nlist *a, struct nlist *b);
    char *taskExecFile(char *pname);
    void processSymTbl(void);
    struct nlist * readSymbols(char *pname);
    StackType *lookupSym(StackType *);
    StackType *stack_start;
    StackType *stack_end;
    StackType *stack_tmp;
    StackType *stack_tmp2;
    char          **argv;
    char           *pname;
#if ! defined(SOLARIS2)
    struct exec     header, lheader;
#endif
    SymbolList      symb_list;
    int             no_of_symb;
    char           *progFileName;
};
#endif
--4eca_2da6-23b9_64bd-6721_59c
Content-Type: text/plain; charset=us-ascii; name=StackListing.cc
Content-Transfer-Encoding: 7bit
Content-MD5: SoHAUHUu8xS5n0Rv9yI7Ig==
Content-Description: StackListing.cc
Content-Disposition: attachment; filename=StackListing.cc
#include    <stdio.h>
#include    <stdlib.h>
#include    <string.h>
#include "StackListing.h"
StackLevel::StackLevel(char *name, unsigned long *argp, unsigned long delta,
                       int line) :
                 funcName(0), lineNo(line), offset(delta), next(0)
{
int i;
    if(name) {
        funcName = new char [strlen(name)+1];
        strcpy(funcName, name);
    }
    if(argp) {
        for(i=0; i<6; i++)
            args[i] = argp[i];
    } else {
        for(i=0; i<6; i++)
            args[i] = 0;
    }
    if(line != -1) {
        lineNo = line;
    }
}
StackLevel::StackLevel(const StackLevel &obj) :
lineNo(obj.lineNo),
offset(obj.offset),
next(0)
{
int i;
    if(obj.funcName) {
        funcName = new char [strlen(obj.funcName)+1];
        strcpy(funcName, obj.funcName);
    }
    for(i=0; i<6; i++)
        args[i] = obj.args[i];
}
StackLevel::~StackLevel()
{
    if(funcName) {
        delete [] funcName;
        funcName = 0;
    }
}
StackListing::StackListing(char *tskName) : level(0), nlevels(0), theTaskName(0)
{
    if(tskName) {
        theTaskName = new char [strlen(tskName) +1];
        strcpy(theTaskName, tskName);
    }
}
StackListing::StackListing(const StackListing &obj) :
level(0),
nlevels(obj.nlevels),
theTaskName(0)
{
int i;
StackLevel *ptr = 0;
    if(obj.theTaskName) {
        theTaskName = new char [strlen(obj.theTaskName) + 1];
        strcpy(theTaskName, obj.theTaskName);
    }
    for(i=0; i<nlevels; i++) {
        if(level) {
            ptr->next = new StackLevel(*obj[i]);
            ptr = ptr->next;
        } else {
            level = new StackLevel(*obj[i]);
            ptr = level;
        }
    }
}
void
StackListing::addLevel(char *name, unsigned long *args, unsigned long offset,
                    int lineNo)
{
StackLevel *ptr;
    if(level) {
        for(ptr=level; ptr->next; ptr = ptr->next);
        ptr->next = new StackLevel(name, args, offset, lineNo);
    } else {
        level = new StackLevel(name, args, offset, lineNo);
    }
    nlevels++;
}
StackListing::~StackListing()
{
StackLevel *dp, *ptr;
    nlevels = 0;
    for(ptr=level; ptr ;) {
        dp = ptr;
        ptr = ptr->next;
        delete dp;
    }
    if(theTaskName) {
        delete [] theTaskName;
        theTaskName = 0;
    }
}
StackLevel *
StackListing::operator[](int i) const
{
int k = 0;
StackLevel *ptr;
    for(ptr=level; ptr && k++ !=i; ptr = ptr->next);
    if(--k == i)
        return(ptr);
    else
        return(0);
}
ostream &
operator<<(ostream &os, StackListing &traceb)
{
int i;
StackLevel *sp;
    /* This often results in UMR errors (uninitialized memory read)
     * This may result when there are fewer args than 5.
     * For now we ignore this warning. */
    for(i=0; i<traceb.depth(); i++) {
        sp = traceb[i];
        os << sp->functionName() << "("
           << sp->arg(0)  << ", "
           << sp->arg(1)  << ", "
           << sp->arg(2)  << ", "
           << sp->arg(3)  << ", "
           << sp->arg(4)  << ", "
           << sp->arg(5)  << ") + "
           << sp->symOffset()  ;
#if ! defined(VXWORKS)
        if(sp->lineNumber() != 0)
           os << " at Line " << sp->lineNumber() ;
#endif
        os << endl;
    }
    return(os);
}
--4eca_2da6-23b9_64bd-6721_59c
Content-Type: text/plain; charset=us-ascii; name=StackListing.h
Content-Transfer-Encoding: 7bit
Content-MD5: 92f8zcDv2yDdoom1MN3UXA==
Content-Description: StackListing.h
Content-Disposition: attachment; filename=StackListing.h
X-Sun-Data-Type: h-file
// Copyright (C) 1994 Associated Universities, Inc. Washington DC, USA.
//
// This program is free software; you can redistribute it and/or modify
// it under the terms of the GNU General Public License as published by
// the Free Software Foundation; either version 2 of the License, or
// (at your option) any later version.
//
// This program is distributed in the hope that it will be useful, but
// WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
// General Public License for more details.
//
// You should have received a copy of the GNU General Public License
// along with this program; if not, write to the Free Software
// Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
//
// Correspondence concerning GBT software should be addressed as follows:
//  GBT Operations
//  National Radio Astronomy Observatory
//  P. O. Box 2
//  Green Bank, WV 24944-0002 USA
#ifndef StackListing_h
#define StackListing_h
#include <iostream.h>
class StackListing;
class XDR;
class StackLevel {
friend StackListing;
friend int xdr_StackLevel(XDR *, StackLevel *);
friend void stream_StackLevel(ostream &, StackLevel *);
public:
    StackLevel(char *name, unsigned long *args, unsigned long offset = 0,
               int lineNo = 0);
    StackLevel(const StackLevel &);
   ~StackLevel();
    char *functionName() { return(funcName); }
    unsigned long arg(int index) { return(args[index]); }
    unsigned long symOffset() { return(offset); }
    int lineNumber() { return(lineNo); }
    StackLevel *Next() { return(next); }
protected:
    char *funcName;
    unsigned long args[6];
    unsigned long offset;
    int lineNo;
    StackLevel *next;
};
class StackListing {
    friend int xdr_StackListing(XDR *, StackListing *);
    friend void stream_StackListing(ostream &, StackListing *);
public:
    StackListing(char *taskName);
    StackListing(const StackListing &);
   ~StackListing();
    StackLevel *operator[] (int ) const;
    int depth() { return(nlevels); }
    void addLevel(char *name, unsigned long *args, unsigned long offset,
                  int lineNo);
    friend ostream &operator << (ostream&, StackListing &);
    char *taskName() { return(theTaskName); }
protected:
    StackLevel *level;
    int nlevels;
    char *theTaskName;
};
#endif
--4eca_2da6-23b9_64bd-6721_59c
Content-Type: text/plain; charset=us-ascii; name=getStackPtr.s
Content-Transfer-Encoding: 7bit
Content-MD5: fwTAdbP0JP0GjVYRnEz2Vg==
Content-Description: getStackPtr.s
Content-Disposition: attachment; filename=getStackPtr.s
X-Sun-Data-Type: text
! Copyright (C) 1994 Associated Universities, Inc. Washington DC, USA.
!
! This program is free software; you can redistribute it and/or modify
! it under the terms of the GNU General Public License as published by
! the Free Software Foundation; either version 2 of the License, or
! (at your option) any later version.
!
! This program is distributed in the hope that it will be useful, but
! WITHOUT ANY WARRANTY; without even the implied warranty of
! MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
! General Public License for more details.
!
! You should have received a copy of the GNU General Public License
! along with this program; if not, write to the Free Software
! Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
!
! Correspondence concerning GBT software should be addressed as follows:
!	GBT Operations
!	National Radio Astronomy Observatory
!	P. O. Box 2
!	Green Bank, WV 24944-0002 USA
!
! $Id: getStackPtr.s,v 1.7 1995/04/26 21:28:16 jbrandt Exp $
!
	.ident	"hc2.4n -O1 -on GLOBALS_VOLATILE getStackPointer.s\n"
#if !defined(SOLARIS2)
	.common	_getStackPointer_V11,1,"data"
#endif
!
! This is for the SPARC Architecture
! Assembler function to flush register windows and return stack pointer
! Hardware: Specific to the sparc architecture (all versions)
!
!
! Note: This function usually can be written using straight C by
!       manipulating the address of the first arg passed in to get the
!       frame pointer. However, the sparc architecture when using windowed
!       registers, requires a trap to flush the registers into memory.
!       This must be done prior to attempting a stack trace.
!       Note the ta instruction (Trap). Trap 0x83 is defined in
!       /usr/kvm/sys/sun4c/trap.h (or /usr/include/machine/trap.h)
!       as T_FLUSH_WINDOWS.
!
!
.seg "text"
clcc_1_0.:
#if !defined(SOLARIS2)
.common ___cfront_version_302_xxxxxxxx,1,"data"
.common ___centerline_cfront,1,"data"
#endif
.seg    "data"
.align  8
_rcs_id: .ascii "$Id: getStackPtr.s,v 1.7 1995/04/26 21:28:16 jbrandt Exp $"
.seg "text"
#ifdef SOLARIS2
.global getStackPointer
getStackPointer:
#else
.global _getStackPointer
_getStackPointer:
#endif
#if defined(SOLARIS2)
#include <sys/trap.h>
  ta ST_FLUSH_WINDOWS
#else
  ta 0x83        ! Software Trap to flush windows to memory
#endif
  mov %sp,%o0    ! return to stack pointer
  retl           !
  nop            ! fill-in the delay slot
.seg "data"
    .align  4
    .align  8
!___link:    .word   0x0
!    .word   _getStackPointer
!
! Note that the extranious .common's and symbols appear only because of
! the ranlib(1) program. It couldn't deal with a .o file with out these
! extra symbols.
--4eca_2da6-23b9_64bd-6721_59c
Content-Type: text/plain; charset=us-ascii; name=stktrace.cc
Content-Transfer-Encoding: 7bit
Content-MD5: MFQw8WTxxqaPzFiBhsHNBA==
Content-Description: stktrace.cc
Content-Disposition: attachment; filename=stktrace.cc
#include "StackTracer.h"
void level1(int, int, int, int, int);
void level2(int, int, int, int, int);
StackTracer *trace = 0;
StackListing *t1(0), *t2(0), *t3(0);
#ifdef VXWORKS
void stktrace()
#else
int main(int argc, char **argv)
#endif
{
    trace = new StackTracer();
    t1 = trace->traceStack();
    // trace->printStack();
    level1(1,2,3,4,5);
    delete trace;
    cout << *t1 << endl << endl;
    cout << *t2 << endl << endl;
    cout << *t3 << endl << endl;
}
void level1(int a, int b, int c, int d, int e)
{
    // trace->printStack();
    t2 = trace->traceStack();
    level2(a,b,c,d,e);
}
void level2(int a, int b, int c, int d, int e)
{
    t3 = trace->traceStack();
}
--4eca_2da6-23b9_64bd-6721_59c--
From bob_anderson@void.mclean.mcd.mot.com  Mon Nov 10 09:58:07 1997
From: Bob Anderson <bob_anderson@void.mclean.mcd.mot.com>
Date: Mon Nov 10 09:58:10 PST 1997
Subject: RE: MVME162 STAT light failure
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
[Bob Anderson]  The stat light is the result of what's called a double
bus fault.  This occurs when the processor takes a bus or address error
exception and then encounters another bus or address error exception
when it tries to store the processor status and registers on the stack
before passing control to the exception routine.  Any thing that happens
that would disable the memory controller or would not let the processor
obtain the local bus could cause your problem.  See section 7.6.3 of the
69040 processor manual (P/NM68040UM/AD Rev. 1).
Bob Anderson
>
>Hello everyone,
>
>	I'm just about to start debugging a system using the MVME162
>and the 68040 processor.  A set of these boards receive serial data
>via Greenspring MP-IPSerial modules and a large amount of register
>and FIFO interrogation takes place to these IP modules.
>
>Under certain input signal conditions, the MVME162 fails with the
>STAT light illuminated.  This LED indicates that a halt condition
>exists in the MC68040 processor by decoding the status lines from
>that chip. No more interaction can take place with the processor
>until a reset occurs.
>
>Does anyone have any experience of the kind of software problem
>that could cause this result?
>
>Hope someone can give me a hint.
>
>
>Mark Armstrong
>Redifon MEL Ltd
>
--MimeMultipartBoundary--
From daemon@csg.lbl.gov  Tue Nov 11 04:01:12 1997
From: daemon@csg.lbl.gov
Date: Tue Nov 11 04:01:17 PST 1997
Subject: comp.os.vxworks newsdigest
Comp.Os.Vxworks Daily Digest    Tue Nov 11 04:01:09 PST 1997
        Subject: Re: 2000 problem
-------------------------------------------------------
Newsgroups: comp.os.vxworks,comp.realtime,comp.unix.programmer,comp.lang.c,comp.lang.c++
Subject: Re: 2000 problem
Date: 10 Nov 1997 15:04:38 GMT
From: gregw@microware.com (Greg Weeks)
Organization: Microware Systems Corp., Des Moines, Iowa
Message-ID: <6477q6$e38$1@newnews.microware.com>
References: <62fk8h$mjq@bcarh8ab.bnr.ca>     <34509979.60FFA516@absyss.fr> <1997Oct24.131957.19653@leeds.ac.uk> <345145DA.5EE9@ici.net> <63cq5e$cgp$1@bandit.cyberwar.com> <19971103.79A9C98.101EC@mojaveg.ridgecrest.ca.us> <345ED244.7432@msi.se> <346088AD.C90@ici.net> <Pine.A41.3.95.971105103948.59164B-100000@acis.mc.yu.edu> <34614382.1020@ici.net> <6458gc$o6i$1@plug.news.pipex.net>
Where the alot of the y2k problem is at (banks, insurance) the dates are stored
in packed decimal and there is no support to use binary without a conversion as
big as going to 4 digit years.
Greg Weeks
In article <6458gc$o6i$1@plug.news.pipex.net>, "Coal" <coal@dial.pipex.com> writes:
|> I would have thought that another 27/28 years could be bought quite easily.
|> Computers don't really think in decimal and where the date has been stored
|> as two figures, I would have thought it would have been rounded up to the
|> nearest "round" binary number i.e. 128.
|>
|> It should be noted at this stage that I don't know what I'm talking about...
|>
|> Coal
|>
|>
|>
|>
---------------------------
End of New-News digest
**********************
From sfakhour@nortel.ca  Tue Nov 11 19:21:14 1997
From: "Salim Fakhouri" <sfakhour@nortel.ca>
Date: Tue Nov 11 19:21:17 PST 1997
Subject: ioctl funccode #18
Hi all, I have implemented a device driver as explained
in the VxWorks 5.3.1 Programmer's guide ( i.e using the
iosDrvInstall(), iosDevAdd(), etc.) but I am seeing something
strange when I call the ioctl() function with function code 18:
In principle, a ioctl(fd, code, arg) call should be passed to the
driver's xxIoctl() function. I tried that and it works for all
values of code except 18. When I call the ioctl function with code
18, the xxIoctl() function is not called!
Are there some codes that are intercepted by VxWorks and not passed
to the driver? If yes, where is this documented?
Note: I am using a regular device not a block device.
Thanks.
From sfakhour@nortel.ca  Tue Nov 11 21:01:59 1997
From: "Salim Fakhouri" <sfakhour@nortel.ca>
Date: Tue Nov 11 21:02:02 PST 1997
Subject: ioctl funccode #18
Hi all, I have implemented a device driver as explained
in the VxWorks 5.3.1 Programmer's guide ( i.e using the
iosDrvInstall(), iosDevAdd(), etc.) but I am seeing something
strange when I call the ioctl() function with function code 18:
In principle, a ioctl(fd, code, arg) call should be passed to the
driver's xxIoctl() function. I tried that and it works for all
values of code except 18. When I call the ioctl function with code
18, the xxIoctl() function is not called!
Are there some codes that are intercepted by VxWorks and not passed
to the driver? If yes, where is this documented?
Note: I am using a regular device not a block device.
Thanks.
From daemon@csg.lbl.gov  Wed Nov 12 04:00:48 1997
From: daemon@csg.lbl.gov
Date: Wed Nov 12 04:00:52 PST 1997
Subject: comp.os.vxworks newsdigest
Comp.Os.Vxworks Daily Digest    Wed Nov 12 04:00:45 PST 1997
        Subject: Re: 2000 problem
-------------------------------------------------------
Newsgroups: comp.os.vxworks,comp.realtime,comp.unix.programmer,comp.lang.c,comp.lang.c++
Subject: Re: 2000 problem
Date: 6 Nov 1997 01:24:53 GMT
From: gah@u.washington.edu (G. Herrmannsfeldt)
Organization: University of Washington
Message-ID: <63r695$cb8$1@nntp6.u.washington.edu>
References: <62fk8h$mjq@bcarh8ab.bnr.ca> <62ijm7$qmu@bgtnsc02.worldnet.att.net> <344DCDF8.26351658@absyss.fr> <62lk9n$gqf@dg-rtp.dg.com> <01bcdf9c$71b5bfc0$daac2ac0@pub00005m> <62np2n$e4t@dg-rtp.dg.com> <345E1269.628F95FE@webvision.com>
I work in a building that has floors numbered
- -2, -1, 1, 2, 3, 4, 5
and I think it is strange that they lost floor 0.
- -- glen
---------------------------
End of New-News digest
**********************
From Phil_Watson@masirv.com  Wed Nov 12 09:01:47 1997
From: Phil_Watson@masirv.com (Phil Watson)
Date: Wed Nov 12 09:01:51 PST 1997
Subject: Re: ioctl funccode #18
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
> Submitted-by: "Salim Fakhouri" <sfakhour@nortel.ca>
>
>
> Hi all, I have implemented a device driver as explained
> in the VxWorks 5.3.1 Programmer's guide ( i.e using the
> iosDrvInstall(), iosDevAdd(), etc.) but I am seeing something
> strange when I call the ioctl() function with function code 18:
FIOGETNAME is handled at the "I/O interface level". This is documented in the
man page on ioctl. There are others that may be handled tyLib or other device
libraries.
/psw
Philip Watson, Phil_Watson@masirv.com
Manager, Embedded Software Development
Matsushita Avionics Systems Corp.
15253 Bake Parkway
Irvine, California, 92618  U.S.A.
--MimeMultipartBoundary--
From d.luck@ieee.org  Wed Nov 12 09:24:41 1997
From: Dale Luck <d.luck@ieee.org>
Date: Wed Nov 12 09:24:43 PST 1997
Subject: RE: comp.os.vxworks newsdigest
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Some hotels don't have a 13th floor, too! Well I suppose that would be true for all short hotels but
even some hotels with more than 12 floors.
Dale
--MimeMultipartBoundary--
From Sunita_Bhama_at_2-Troy-HITC@CCGATE.HAC.COM  Wed Nov 12 10:49:09 1997
From: Sunita_Bhama_at_2-Troy-HITC@CCGATE.HAC.COM
Date: Wed Nov 12 10:49:12 PST 1997
Subject: BOOTP server on VxWorks
     We are working on a project which require the use of BOOTP server on
     VxWorks OS. We do not have any file system on the PowerPC that we are
     using. We are using Tornado which does not support BOOTP server.
     We are hoping to find some one who has successfully used BOOTP server
     on VxWorks or any other platform, and would like to know which version
     was used and what kind of changes were required in the original source
     code.
From d.luck@ieee.org  Wed Nov 12 15:34:33 1997
From: Dale Luck <d.luck@ieee.org>
Date: Wed Nov 12 15:34:40 PST 1997
Subject: 64bit vs 32bit registers in mips vxworks
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
I just completed changing some very low level code to use 64bit lds and strs.
I'm sure I'm not using any registers that need to be preserved. (t0,a3,v1,v0).
After the routine finishes it leaves various 1's set in the upper 32bits of those registers.
Some other totally unrelated pieces of  code stopped working, until I zeroed out
those scratch registers before returning.
Has anyone else seen anything like this? Am I doing something I shouldn't be doing
by using double operations?
I'm suspecting a bug in the compiler, or quite possibly some other piece of asm
I've written. Which isn't very much.
Dale
--MimeMultipartBoundary--
From jhoang@dantel.com  Wed Nov 12 15:43:27 1997
From: James Hoang <jhoang@dantel.com>
Date: Wed Nov 12 15:43:30 PST 1997
Subject: FW: [URGENT!] Support Radio Free Asia
--MimeMultipartBoundary
Content-Type: text/plain
> ----------
> From: 	Dan Hoang[SMTP:dhoang@ix.netcom.com]
> Sent: 	Wednesday, November 12, 1997 3:00 PM
> Subject: 	[URGENT!] Support Radio Free Asia
>
> Dear friends,
>
> The House just passed HR 2232 which increases funding for Radio Free
> Asia.
> While no extra money is specifically allocated to Vietnam, we do
> benefit in
> two ways:
>
> (1)	With the construction of a modern & powerful transmitter at
> Tinian
> (Northern Mariana Islands), RFA's ability to avoid jamming will be
> boosted significantly. Right now, the Vietnamese government is jamming
> RFA
> broadcasts.
> (2)	Part of the existing $10 MM/year budget will be freed up for
> other
> sections (Vietnamese, Cambodian, Burmese...).  This is the
> trickle-down
> benefit.
>
> The Senate will take up the Bill on November 13 (Thursday) under a
> format
> known as "unanimous consent," which means just one senator in
> opposition
> can derail the whole bill. Right now, the MAJOR stumbling block is
> Senator
> Diane Feinstein. We need to fax/phone her office ASAP. Her phone is:
> (202)
> 224-3841, and her fax is (202)228-3954. District office: (310)
> 914-7300,
> (415) 536-6868. Please try to call the DC office if possible and get
> friends to help.
>
>
> Thanks!
>
> Duy Hoang
> dhoang@ix.netcom.com
>
--MimeMultipartBoundary--
From altan@venus.aselsan.com.tr  Wed Nov 12 22:12:09 1997
From: Cagatay ALTAN <altan@venus.aselsan.com.tr>
Date: Wed Nov 12 22:12:16 PST 1997
Subject: RE: comp.os.vxworks newsdigest
--MimeMultipartBoundary
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Wed, 12 Nov 1997, the vxWorks Users Group Exploder wrote:
> Submitted-by d.luck@ieee.org  Wed Nov 12 09:24:41 1997
> Submitted-by: Dale Luck <d.luck@ieee.org>
>
> --MimeMultipartBoundary
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: 7bit
>
> Some hotels don't have a 13th floor, too! Well I suppose that would be true for all short hotels but
> even some hotels with more than 12 floors.
> Dale
>
And did you know that there is no 4th floor in hotels, hospitals, etc. in
Japan, because that the number '4' in Japanese, which is 'shi', reminds
people the word 'death' which is 'shin' ?
                                              Cagatay Altan
--MimeMultipartBoundary--
From phil.quiney@gecm.com  Thu Nov 13 01:02:31 1997
From: Philip Quiney <phil.quiney@gecm.com>
Date: Thu Nov 13 01:02:35 PST 1997
Subject: Re: BOOTP server on VxWorks
Hi there,
We have been using BOOTP server compiled from the source code supplied by WRS
in the WIND_BASE/target/unsupported/bootp2.1. We did not modify the source code
at all and found it ran successfully on a PC running Solaris 2.5.
The 'default' bootptab required editing to suit ip addresses etc on our network
but the examples in the file are easy enough to modify.
>      We are working on a project which require the use of BOOTP server on
>      VxWorks OS. We do not have any file system on the PowerPC that we are
>      using. We are using Tornado which does not support BOOTP server.
>
>      We are hoping to find some one who has successfully used BOOTP server
>      on VxWorks or any other platform, and would like to know which version
>      was used and what kind of changes were required in the original source
>      code.
>
>
>
>
Regards
Phil Q
===============================================================================
Phil Quiney          _/_/_/_/        _/  _/_/_/_/  email : phil.quiney@gecm.com
GEC Marconi         _/    _/        _/  _/    _/     tel : +44 1245 353221x3914
Communications Ltd _/_/_/_/  _/    _/  _/  _/_/      fax : +44 1245 275448
Chelmsford        _/        _/_/_/_/  _/_/_/_/
England CM1 1PL                              _/
===============================================================================
From daemon@csg.lbl.gov  Thu Nov 13 04:00:31 1997
From: daemon@csg.lbl.gov
Date: Thu Nov 13 04:00:35 PST 1997
Subject: comp.os.vxworks newsdigest
Comp.Os.Vxworks Daily Digest    Thu Nov 13 04:00:26 PST 1997
        Subject: Cannot FTP and Telnet (CONSOLE_TTY related)
        Subject: Dos FS
-------------------------------------------------------
Newsgroups: comp.os.vxworks
Subject: Cannot FTP and Telnet (CONSOLE_TTY related)
Date: 12 Nov 1997 22:21:50 GMT
From: "Raymond K.S. Yeung" <ryeung@adicomw.com>
Organization: AdiCom Wireless
Message-ID: <01bcefb9$b303f320$df60a9ce@host.hooked.net>
We use MV162LC package which has 4 serial ports.
In usrConfig.c, one can find the following segment of code
within usrRoot ( ):
if (ix == CONSOLE_TTY)		/* init the tty console */
	{
	strcpy (consoleName, tyName);
	consoleFd = open (consoleName, O_RDWR, 0);
	(void) ioctl (consoleFd, FIOBAUDRATE, CONSOLE_BAUD_RATE);
	(void) ioctl (consoleFd, FIOSETOPTIONS, OPT_TERMINAL);
	}
I thought "#if FALSE" them would be the same as
setting CONSOLE_TTY to NONE (i.e. -1), since ix
runs from 0 to 3.  But when I did so, FTP and
Telnet functions are disabled (i.e. connection fails).
Anyone knows why?  Note: I've CONSOLE_TTY set to 0
for the boot ROM.
Thanks,
Raymond Yeung
---------------------------
Newsgroups: comp.os.vxworks
Subject: Dos FS
Date: Fri, 07 Nov 1997 10:29:41 +0000
From: "R.Pettipher" <ac253@dial.pipex.com>
Organization: UUNet UK server (post doesn't reflect views of UUNet UK)
Message-ID: <3462ED95.7F8C@dial.pipex.com>
We have upgraded from Vxworks 5.3 to 5.3.1, and are now having
major problems with the Dos FS, which manages to get into an
infinite loop while following pointers, one of which points to
itself.
The routine involved is sllPrevious, and it occurs when trying
to overwrite an erased directory entry.  For some reason Vxworks
uses the cluster number that it found in the erased entry and which
is now used by another file.
If anyone can throw some light on this problem, or indicate what
sllPrevious is trying to do we would be most grateful.
Rodney Pettipher
---------------------------
End of New-News digest
**********************
From lucard@tin.it  Thu Nov 13 05:01:59 1997
From: Luca Rodda <lucard@tin.it>
Date: Thu Nov 13 05:02:02 PST 1997
Subject: Interrupt Enable/disable on I486
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
We need to disable individually the interrupt sources  to  CPU.
We assume that  intLock(), intLevelSet(), intLevelGet(),  disable all
interrupt over a certain level  like in MC680X architecture.
Which function call can we use to disable a single interrupt ?
Thank You
Cristina Ostan
--MimeMultipartBoundary--
From Rahul.Chopra.choprar@nt.com  Thu Nov 13 10:06:46 1997
From: "Rahul Chopra" <Rahul.Chopra.choprar@nt.com>
Date: Thu Nov 13 10:06:49 PST 1997
Subject: VxWorks vs NT
--------------DA50567C88A93E00CDD1FF44
Content-type: text/plain; charset="us-ascii"
All,
I am working on the VoIP initiative here. Wanted to know if anyone had
done any comparative analysis between NT and VxWorks.
Please let me know.
Rahul.
--------------DA50567C88A93E00CDD1FF44
Content-type: text/x-vcard; charset="us-ascii"; name="vcard.vcf"
Content-transfer-encoding: 7bit
Content-Description: Card for Rahul Chopra
Content-Disposition: attachment; filename="vcard.vcf"
begin:          vcard
fn:             Rahul Chopra
n:              Chopra;Rahul
org:            New Business Opportunities
adr:            2305, Mission College Blvd;;M/S B2240;Santa Clara;CA;94054;USA
email;internet: choprar@nortel.com
title:          Sr. Advisor
tel;work:       408-565-8379
x-mozilla-cpt:  ;0
x-mozilla-html: FALSE
version:        2.1
end:            vcard
--------------DA50567C88A93E00CDD1FF44--
From Wynn.Rostek-1@kmail.ksc.nasa.gov  Thu Nov 13 10:10:52 1997
From: Rostek-1 Wynn <Wynn.Rostek-1@kmail.ksc.nasa.gov>
Date: Thu Nov 13 10:11:03 PST 1997
Subject: RE: Interrupt Enable/disable on I486
Howdy,
I've written three applications that open TCP/IP sockets and wait for
connections, then go off and do stuff.  If I run them from the shell by
invoking them, (-> jabber<cr>) they run just dandy.
If I spawn them as a task from the shell, (-> sp(jabber)) they go into
the accept call, and when you attempt to connect, the systems hangs.
Seriously.  (Power switch time.)
The same thing happens if you invoke them from the shell via telnet, and
then break the telnet connection.
I tried forcing stdin/stdout/stderr to /null using ioTaskStdSet() but it
didn't seem to help.
I'm sure this is a very common problem, but I have not run into it
before.
Any hints you can pass along would be really appreciated.
Wynn Rostek
Lead Engineer, Advanced Development Laboratory
DNX-20
Kennedy Space Center, FL 32899
wynn.rostek-1@ksc.nasa.gov
Voice: (407) 867-6770
Fax: (407) 867-7435
>
From YF.Siu@eng.efi.com  Thu Nov 13 10:39:36 1997
From: "Yuet Fung Siu" <YF.Siu@eng.efi.com>
Date: Thu Nov 13 10:39:39 PST 1997
Subject: Re: comp.os.vxworks newsdigest
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
On Nov 13,  4:00am, the vxWorks Users Group Exploder wrote:
> ---------------------------
>
> Newsgroups: comp.os.vxworks
> Subject: Dos FS
> Date: Fri, 07 Nov 1997 10:29:41 +0000
> From: "R.Pettipher" <ac253@dial.pipex.com>
> Organization: UUNet UK server (post doesn't reflect views of UUNet UK)
> Message-ID: <3462ED95.7F8C@dial.pipex.com>
>
> We have upgraded from Vxworks 5.3 to 5.3.1, and are now having
> major problems with the Dos FS, which manages to get into an
> infinite loop while following pointers, one of which points to
> itself.
> The routine involved is sllPrevious, and it occurs when trying
> to overwrite an erased directory entry.  For some reason Vxworks
> uses the cluster number that it found in the erased entry and which
> is now used by another file.
> If anyone can throw some light on this problem, or indicate what
> sllPrevious is trying to do we would be most grateful.
> Rodney Pettipher
>
This is a bug introduced in dosFsLib since 5.2. (Still there ??)
Ask for a patch for SPR 4418.
What's happening is that in one of the recursively called functions,
a special case of the root directory was ignored, causing the sll (for
hash tables) to be corrupted (with same node added twice). Later
reference to the sll will cause the task to loop infinitely because
sllPrevious of that node is itself.  I don't think this bug has a
work-around.
Hope this helps,
YF
--MimeMultipartBoundary--
From tkb@mclean.sparta.com  Thu Nov 13 11:18:31 1997
From: "Thomas K. Buchanan" <tkb@mclean.sparta.com>
Date: Thu Nov 13 11:18:34 PST 1997
Subject: Re: VxWorks vs NT
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
At 10:06 AM 11/13/97 PST, you wrote:
>I am working on the VoIP initiative here. Wanted to know if anyone had
>done any comparative analysis between NT and VxWorks.
VxWorks is suitable for hard real-time embedded applications.  Without the
use of some questionable third party products, NT is not.
VxWorks can run in an environment with minimal memory resources, no file
system etc.  I believe NT is a resource hog, requiring 32MB+ of memory,
hundreds of MB of disk storage etc.
VxWorks has one pretty nice development environment. NT has many excellent
choices of development environments and a horde of miscellaneous tool
vendors.
VxWorks is supported on more CPU architectures than NT including several
families of microcontrollers.  You can port VxWorks to custom hardware.
Withour spending millions, using NT confines your hardware selection to
platoforms supported by Microsoft.
You can do a user interface with VxWorks using some third party screen
libraries including ports of X-Windows.  You can produce a user interface
quicker with superior tools under NT.
The standard version of VxWorks does not include task-based memory
protection.  NT does though 4.0 compromised the advantages of this by
moving the display drivers into the kernel space.
.. and many more
Conclusion: You are trying to compare apples and oranges.  NT is a
desktop/server/office oriented operating system.  There are so many great
tools and programmers available that people are tempted to use it for
pseudo real-time purposes.  You can do so with limited success.  VxWorks is
a relatively simple high performance REAL-TIME EMBEDDED OS.  In my
experience, applications where either is suited to the task are rare.
Analogy:  You need to get to the top of a mountain in a fixed amount of
time.  Your horse and climbing gear (VxWorks) come in handy.  Your Mercedes
(NT) just looks good sitting at the bottom of the mountain.  When you come
down, either will take you back into town.  I'd take the Mercedes...
adios
--------------------------------------------
       /\       Thomas Keith Buchanan
      /##\      Principal Engineer
     /####\
    /####/--
   /####/----   SPARTA, Inc.
  -\####\__---  Computer Products Division
 ---\##\  /---- 7926 Jones Branch Drive
 ----\##\/\---- Suite 900
  ----\####\--  McLean, VA 22102
   ----\####/
    ---/###/    Voice: 703 448 0210
     -/###/     FAX:   703 893 5494
      \##/      WWW:   www.mclean.sparta.com
       \/
--MimeMultipartBoundary--
From tkb@mclean.sparta.com  Thu Nov 13 11:25:04 1997
From: "Thomas K. Buchanan" <tkb@mclean.sparta.com>
Date: Thu Nov 13 11:25:08 PST 1997
Subject: RE: Interrupt Enable/disable on I486
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
>I've written three applications that open TCP/IP sockets and wait for
>connections, then go off and do stuff.  If I run them from the shell by
>invoking them, (-> jabber<cr>) they run just dandy.
>
>If I spawn them as a task from the shell, (-> sp(jabber)) they go into
>the accept call, and when you attempt to connect, the systems hangs.
>Seriously.  (Power switch time.)
There is no reason the code should not work in either case.  I do it all
the time.  Try making the stack size larger for the spawned versions.  Any
task that uses the socket library or a file system should allocate a
generous stack space to begin with.  You can check the stack usage later
and make it smaller if necessary.
Did you change the priority of the network task?  Check its value relative
to the application task and the shell.
--------------------------------------------
       /\       Thomas Keith Buchanan
      /##\      Principal Engineer
     /####\
    /####/--
   /####/----   SPARTA, Inc.
  -\####\__---  Computer Products Division
 ---\##\  /---- 7926 Jones Branch Drive
 ----\##\/\---- Suite 900
  ----\####\--  McLean, VA 22102
   ----\####/
    ---/###/    Voice: 703 448 0210
     -/###/     FAX:   703 893 5494
      \##/      WWW:   www.mclean.sparta.com
       \/
--MimeMultipartBoundary--
From sfakhour@nortel.ca  Thu Nov 13 12:43:52 1997
From: "Salim Fakhouri" <sfakhour@nortel.ca>
Date: Thu Nov 13 12:43:56 PST 1997
Subject: Re: ioctl funccode #18
I don't understand the logic behind this ioctl() function code business:
I am writing my own device driver and want to use ioctl()
to access my own functions. Now I have not seen in the documentation
(I have Win95 Tornado 1.0.1) a list of reserved function codes.
In ioLib.h function codes from 1 to 46 are defined:
#define FIONREAD	1		/* get num chars available to read */
#define FIOFLUSH	2		/* flush any chars in buffers */
... <snip>
#define FIOGETNAME	18		/* return file name in arg */
... <snip>
#define FIOFSTATFSGET   46              /* get file system status info */
But I have tested codes from 1 to 40, they are all passed to my driver's
xxIoctl() function except code 18 that is intercepted by the I/O system.
Does this mean that I can safely use all codes except 18? or should I
use codes beyond 46 or another number?
Thanks,
From randy@opid.littondsd.com  Thu Nov 13 13:13:45 1997
From: randy@opid.littondsd.com (Randy Ryan)
Date: Thu Nov 13 13:13:49 PST 1997
Subject: Upgrade MVME167 to MVME177?
----- Begin Included Message -----
From Mailer-Daemon@mail1 Thu Nov 13 13:12:19 1997
From: Mailer-Daemon@mail1 (Mail Delivery Subsystem)
Subject: Returned mail: User unknown
To: <randy@opid.littondsd.com>
Content-Length: 1303
X-Lines: 38
The original message was received at Thu, 13 Nov 1997 12:54:20 -0800
from opid.littondsd.com [167.225.94.74]
   ----- The following addresses had delivery problems -----
<vxexplo@lbl.gov>  (unrecoverable error)
   ----- Transcript of session follows -----
... while talking to lbl.gov.:
>>> RCPT To:<vxexplo@lbl.gov>
<<< 550 <vxexplo@lbl.gov>... User unknown
550 <vxexplo@lbl.gov>... User unknown
   ----- Original message follows -----
Return-Path: <randy@opid.littondsd.com>
Received: from opid.littondsd.com by mail1 (SMI-8.6/SMI-SVR4)
	id MAA23423; Thu, 13 Nov 1997 12:54:20 -0800
Received: by opid.littondsd.com (4.1/SMI-4.1)
	id AA06309; Thu, 13 Nov 97 13:12:15 PST
Date: Thu, 13 Nov 97 13:12:15 PST
From: randy@opid.littondsd.com (Randy Ryan)
Message-Id: <9711132112.AA06309@opid.littondsd.com>
To: vxexplo@lbl.gov
Subject: MV167 or MV177
content-length: 432
Is the MV177 (68060) fairly transparant in running MV167 (68040) based
drivers/applications or are there inherent problems?
Most of the 3rd party software we run is support for the 68040 card and I
believe that theoretically the 68060 it is supposed to run the 68040 software,
but wanted to double check this with the experts here before committing to buy
one.
Thanks much,
Randy Ryan
Litton Data Systems
randy@opid.littondsd.com
----- End Included Message -----
From jshaw_shade@compuserve.com  Fri Nov 14 02:45:17 1997
From: John Shaw <jshaw_shade@compuserve.com>
Date: Fri Nov 14 02:45:21 PST 1997
Subject: Re: Upgrade MVME167 to MVME177?
--MimeMultipartBoundary
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
Regarding
>Is the MV177 (68060) fairly transparant in running MV167 (68040) based
>drivers/applications or are there inherent problems?
>Most of the 3rd party software we run is support for the 68040 card and =
I
>believe that theoretically the 68060 it is supposed to run the 68040
software,
>but wanted to double check this with the experts here before committing =
to
buy
>one.
>Thanks much,
>Randy Ryan
>Litton Data Systems
We have used 177 cards in place of 167 cards for a while. Usually 177 car=
ds
will
have more memory, 32 Mbs instead of 16 Mbs. There is a VxWorks 5.2 BSP fo=
r
the
177.
We have successfully run code compiled for to '040 processor on the '060 =
of
the 177
with no obvious hitches. We have, though, had problems with the BSP. We
have not
been able to run the 177 as a master in a chassis of many slave cards,
usually of the
MVME-162 variety, with an additional 167 slave too. The best we have been=
able to
achieve is a 177 as master, two x 167 slaves and one x 162 slave. We did
try a patch
for the 177 but without any success. We have never got to the bottom of t=
he
problem.
I know nothing about how reliable the 177 is under Tornado!
In summary, usage of the 177 as a replacement for the 167 is 'fairly
transparent' but
one does have to take care.
John Shaw,
Shade (Computer Services) Limited, Calne, Wiltshire, England, UK.
--MimeMultipartBoundary--
From daemon@csg.lbl.gov  Fri Nov 14 04:00:34 1997
From: daemon@csg.lbl.gov
Date: Fri Nov 14 04:00:50 PST 1997
Subject: comp.os.vxworks newsdigest
Comp.Os.Vxworks Daily Digest    Fri Nov 14 04:00:31 PST 1997
        Subject: Code for DMA engine on 2600/2300
-------------------------------------------------------
Newsgroups: comp.os.vxworks
Subject: Code for DMA engine on 2600/2300
Date: Thu, 13 Nov 1997 13:55:20 -0500
From: Steve Rejto <srejto@ll.mit.edu>
Organization: MIT Lincoln Laboratory
Message-ID: <346B4D18.748A880C@ll.mit.edu>
We have recently moved to Moto  POWER PC boards from MOTO 162/167
boards. We have a bunch of libraries taht we devloeped for teh 16x
boards which do DMA and other miscelaneous functions. Regretfully the
port is not a one day affair. Does someone have a DMA library or rouines
for the MVME 260x or 230x series boards. Any other utility routines  for
these boards would help
tahnk you
srejto@ll.mit.edu
---------------------------
End of New-News digest
**********************
From mjh@adv.sbc.sony.co.jp  Fri Nov 14 05:09:14 1997
From: Margaret J Harris <mjh@adv.sbc.sony.co.jp>
Date: Fri Nov 14 06:14:38 PST 1997
Subject: Re: ioctl funccode #18
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
>Hi all, I have implemented a device driver as explained
>in the VxWorks 5.3.1 Programmer's guide ( i.e using the
>iosDrvInstall(), iosDevAdd(), etc.) but I am seeing something
>strange when I call the ioctl() function with function code 18:
>
>In principle, a ioctl(fd, code, arg) call should be passed to the
>driver's xxIoctl() function. I tried that and it works for all
>values of code except 18. When I call the ioctl function with code
>18, the xxIoctl() function is not called!
>
>Are there some codes that are intercepted by VxWorks and not passed
>to the driver? If yes, where is this documented?
>
I too have seen something similar with our ouwn custom driver. For this
driver, passing function code=4 caused a problem.  Somehow, between the
ioctl call and being passed to xxIoctl this got changed to 4099 (decimal)
which happens to be the function code for SIO_BAUD_SET. Function code=5 gets
handled correctly.  Indeed function codes from 0-400, except 4, all got
passed correctly without translation to our xxIoctl.
I couldn't find any documentation about it either and worked round the
problem by defining the driver's range of codes from 0x1000+ checking each
code in the range got dealt with as expected.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Margaret J Harris
Engineer                              Tel: +44 (0) 1256 48 3722 (Direct)
New Technologies (D&D)                Tel: +44 (0) 1256 355 011
Advanced Technology Division          Fax: +44 (0) 1256 483591/811430
Sony Broadcast & Professional Europe
Jays Close, Viables, Basingstoke
Hampshire RG22 4SB UK                 E-mail: mjh@adv.sbc.sony.co.jp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--MimeMultipartBoundary--
From mea@mclean.sparta.com  Fri Nov 14 06:53:50 1997
From: "Mike Anderson" <mea@mclean.sparta.com>
Date: Fri Nov 14 06:53:53 PST 1997
Subject: Re: ioctl funccode #18
--MimeMultipartBoundary
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
>Submitted-by: "Salim Fakhouri" <sfakhour@nortel.ca>
>
>I don't understand the logic behind this ioctl() function code business:
>I am writing my own device driver and want to use ioctl()
>to access my own functions. Now I have not seen in the documentation
>(I have Win95 Tornado 1.0.1) a list of reserved function codes.
>
>In ioLib.h function codes from 1 to 46 are defined:
>
>#define FIONREAD 1 /* get num chars available to read */
>#define FIOFLUSH 2 /* flush any chars in buffers */
>... <snip>
>#define FIOGETNAME 18 /* return file name in arg */
>... <snip>
>#define FIOFSTATFSGET   46              /* get file system status info */
>
>
>But I have tested codes from 1 to 40, they are all passed to my driver's
>xxIoctl() function except code 18 that is intercepted by the I/O system.
>
>Does this mean that I can safely use all codes except 18? or should I
>use codes beyond 46 or another number?
>
Salim,
  The ioctl call for a given file descriptor (once you've opened/
created the fd) will always direct all of the ioctl requests to the
registered ioctl routine for the driver associated with the fd.
This association is made in the the iosDrvInstall call in your
driver.  This characteristic of sending all of the ioctl requests
(except 18 which goes to the I/O system itself to supply the
"name" of the "file device" associated with the descriptor (remember
that a socket also uses an fd, so the term "name" is a bit of a
misnomer )), is not a bug but a feature :-).  This allows your driver
to be the first line of defense, so to speak, to service all
ioctl requests internally.  Any requests you don't service in your
driver can then be forwarded on (by you in your xxIoctl function)
to one of the VxWorks support libraries if applicable.
An example of this is the tyCo driver supplied with your BSP
(actually in <target>/src/drv/serial ).  The tyIoctl call in
the serial driver only services the FIOBAUDRATE call and then
forwards everything else to the tyIoctl call in tyLib.
HTH,
---------------------------------------------------------------------
|Michael E. Anderson        | Voice -> 703 448 1683 x235            |
|Chief Engineer             | FAX   -> 703 893 5494                 |
|mea@mclean.sparta.com      | http://www.mclean.sparta.com          |
|___________________________|_______________________________________|
|             SPARTA, Inc.              |                           |
|     /\\     C4I Operation             |"Software Development is   |
|    ///\\    7926 Jones Branch Drive   | like making a baby...     |
|   /////\\   Suite 900                 | You can't make a baby in  |
|  /////  \\  McLean, VA 22102          | one month by impregnating |
| / \\\\\  \\ 703-448-0210              | nine women.               |
| \  \\\\\ //                           |                           |
|  \  //////                            | Some things just take     |
|   \//////   SPARTA                    | time."                    |
|    \////    Pride In Performance      |                           |
|     \//     --------------------      |                           |
---------------------------------------------------------------------
--MimeMultipartBoundary--
From mea@mclean.sparta.com  Fri Nov 14 07:25:23 1997
From: "Mike Anderson" <mea@mclean.sparta.com>
Date: Fri Nov 14 07:25:26 PST 1997
Subject: Discontinuation of support for VxWorks 5.2
--MimeMultipartBoundary
Content-Type: text/plain;
	charset="windows-1252"
Content-Transfer-Encoding: 7bit
Greetings!
Flame On...
  Well, I recieved my letter for WRS telling me they were
discontinuing support for VxWorks 5.2 in the mail the other day.
I must admit, I'm a bit surprised that it happened so soon.
Tornado's only been out since December of '95 and we just got the
first major bugfix release a couple of months ago (which itself had
several new bugs).  It took almost four years after the release of
VxWorks 5.0 before WRS discontinued support for VxWorks 4.0.2.  But,
I guess that WRS is trying to cut it's support costs and is willing
to make us pay for the priviledge of upgrading to VxWorks 5.3.1
aka Tornado.  Of course, this wouldn't have been such an issue if
WRS would have automatically upgraded the 5.2 users under maintenance
contracts to 5.3 when it came out.  But, they claimed that Tornado
was such a major advancement that the maintenance contract didn't
cover Tornado.  Sigh.
  Don't get me wrong, I've been using Tornado for some of my projects
and I have adapted to many of it's quirky characteristics (like
the windShell being able to still do an "ls" even though the target
it's "connected" to was shut off ;-).  In fact, I run a hybrid
environment that combines the best features of Tornado with the
"standard" features of VxWorks 5.2 (thank you WRS for the symbol
table sync task in 5.3.1).  However, there is no way I'm willing
to give up most of the features of VxWorks just for the priviledge
of running completely under the Tornado GUI.
  I guess my point is, OK, you want to cut your support costs by
forcing everyone to Tornado/VxWorks 5.3.1.  If your original
licensing policy had provided an automatic upgrade for the 5.2
users under maintenance, this would have been a fait acompli
(apologies to the native Frech speakers, I don't know where
the accent is supposed to go :-).  The windShell is a nice
attempt to duplicate the feature of the native shell, but it falls
woefully short of the mark.  So, I'll switch because I have to, but
WRS, don't *even* think of removing the INCLUDE_CONFIGURATION_5_2
capabilities of VxWorks 5.3.x or it'll be time to find another
kernel.
  As always, these represent my personal opinions and are not
necessarily representative of those held by my company or
co-workers.  But, I know from my private discussions with many
of the other VxWorks users, I am not alone in this sentiment.
Flame off,
---------------------------------------------------------------------
|Michael E. Anderson        | Voice -> 703 448 1683 x235            |
|Chief Engineer             | FAX   -> 703 893 5494                 |
|mea@mclean.sparta.com      | http://www.mclean.sparta.com          |
|___________________________|_______________________________________|
|             SPARTA, Inc.              |                           |
|     /\\     C4I Operation             |"Software Development is   |
|    ///\\    7926 Jones Branch Drive   | like making a baby...     |
|   /////\\   Suite 900                 | You can't make a baby in  |
|  /////  \\  McLean, VA 22102          | one month by impregnating |
| / \\\\\  \\ 703-448-0210              | nine women.               |
| \  \\\\\ //                           |                           |
|  \  //////                            | Some things just take     |
|   \//////   SPARTA                    | time."                    |
|    \////    Pride In Performance      |                           |
|     \//     --------------------      |                           |
---------------------------------------------------------------------
--MimeMultipartBoundary--
From Francis.Hallahan@gsfc.nasa.gov  Fri Nov 14 10:13:42 1997
From: Francis Hallahan <Francis.Hallahan@gsfc.nasa.gov>
Date: Fri Nov 14 10:13:46 PST 1997
Subject: Re: Upgrade MVME167 to MVME177?
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
>Submitted-by randy@opid.littondsd.com  Thu Nov 13 13:13:45 1997
>Is the MV177 (68060) fairly transparant in running MV167 (68040) based
>drivers/applications or are there inherent problems?
>
>Most of the 3rd party software we run is support for the 68040 card and I
>believe that theoretically the 68060 it is supposed to run the 68040 software,
>but wanted to double check this with the experts here before committing to buy
>one.
>
>Thanks much,
>Randy Ryan
>Litton Data Systems
>randy@opid.littondsd.com
Randy,
We have tested a few MV177s. For the most part our 68040 code all runs on
the mv177. The 68060 runs the 68040 instruction set and is able to run some
instructions in parallel. This may give a performance improvement,
especially if you use a compiler that optimizes for the 68060.
However we have had some reliability and configuration problems with the
MV177 board. Our BSP target.nr lists limits for some vxWorks features
because of hardware problems with the MV177, particularly with the data
cache. These problems may be solved now, but I don't know.
Also, our projects make heavy use of the VME bus. A 33Mhz MV167 accesses
the bus at 33Mhz. While our MV177 is a 50Mhz model, it accesses the bus at
25Mhz.
These limitations have caused us to stay with the MV167. If you really need
the CPU power a MV177 may be worth dealing with the problems. Otherwise,
until the MV177 board problems are fixed, I recommend the MV167.
But back to your real question. The MV167 BSP does not run on a MV177, but
all other software we built for our MV167 does run on the MV177. I would
expect that all of your third party software to run fine.
Hope this helps,
Frank Hallahan
PS:  All opinions are my own and don't necessarily represent
CSC's or NASA's.
/-------------------------------------------------------------------------\
| Frank Hallahan                            |  Hallahan@gsfc.nasa.gov     |
|   Software Environment Leader - Code 521  |  fbh@vlsi.gsfc.nasa.gov     |
| Computer Sciences Corporation             |                             |
| at Nasa Goddard Space Flight Center       |  Phone (301) 286 7064       |
\-------------------------------------------------------------------------/
--MimeMultipartBoundary--
From mblack@synaptyx.com  Fri Nov 14 10:20:53 1997
From: Mitch Black <mblack@synaptyx.com>
Date: Fri Nov 14 10:20:56 PST 1997
Subject: Customizing target shell
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Has anyone attempted to add customized commands to the target shell?  We =
want to use the shell as a rudimentary system config interface.  With =
only a few available commands.  I would customize help and probably edit =
symtbl.c so the whole thing isn't included in the app image.  Has anyone =
done anything like this?
Thanks!
Mitchell Black
Synaptyx Corporation
12850 Middlebrook Road, #209
Germantown, MD  20874
Email:  mblack@synaptyx.com
Web:  www.synaptyx.com
--MimeMultipartBoundary--
From jford@sadira.gb.nrao.edu  Fri Nov 14 10:59:52 1997
From: John Ford <jford@bara.gb.nrao.edu>
Date: Fri Nov 14 10:59:59 PST 1997
Subject: Re: Discontinuation of support for VxWorks 5.2
>   Well, I recieved my letter for WRS telling me they were
> discontinuing support for VxWorks 5.2 in the mail the other day.
> I must admit, I'm a bit surprised that it happened so soon.
> Tornado's only been out since December of '95 and we just got the
> first major bugfix release a couple of months ago (which itself had
> several new bugs).
Obviously,in their short-sighted money-grubbing marketing eyes, 5.3.1
is *not* a bugfix, rather a new release.  That`s why they can claim to
support the last 2 "releases".  They should be ashamed.  At least they
threw in the iostreams support for which they made the Tornado 1.0
users pay for. :/
From the WRS web page: (http://www.wrs.com/html/98-q2.html)
This has been a very exciting and productive
quarter for Wind River, one in which we again met our key
revenue and profitability objectives.
Financial Performance
Revenues for the second quarter were $22,000,000,
an increase of 47% from the $15,000,000 reported
in the second quarter of the previous year. Net
income for the quarter was $3,870,000 compared
to net income of $2,090,000 for the corresponding
quarter of the previous year, an increase of 85%.
Earnings per share grew from $0.08 in the second
quarter of last year to $0.14 this year, an increase
of 75%.
See a pattern?  This is nothing but sheer profiteering.  I do not like
it.  But I am stuck with it.  Luckily, I just spent a week upgrading
from 5.2 to 5.3.1, using the 5.2 configuration.  I have no use for
micro-size kernels and host-based shells.
> I guess that WRS is trying to cut it's support costs and is willing
> to make us pay for the priviledge of upgrading to VxWorks 5.3.1
> aka Tornado.  Of course, this wouldn't have been such an issue if
> WRS would have automatically upgraded the 5.2 users under maintenance
> contracts to 5.3 when it came out.  But, they claimed that Tornado
> was such a major advancement that the maintenance contract didn't
> cover Tornado.  Sigh.
Well, financial performance figures say that WRS management is
"right".
<snip>
>
>   Don't get me wrong, I've been using Tornado for some of my projects
> and I have adapted to many of it's quirky characteristics (like
> the windShell being able to still do an "ls" even though the target
> it's "connected" to was shut off ;-).  In fact, I run a hybrid
> environment that combines the best features of Tornado with the
> "standard" features of VxWorks 5.2 (thank you WRS for the symbol
> table sync task in 5.3.1).  However, there is no way I'm willing
> to give up most of the features of VxWorks just for the priviledge
> of running completely under the Tornado GUI.
I`ve not yet started up the tornado GUI.  I may never.
>
>   I guess my point is, OK, you want to cut your support costs by
> forcing everyone to Tornado/VxWorks 5.3.1.  If your original
> licensing policy had provided an automatic upgrade for the 5.2
> users under maintenance, this would have been a fait acompli
> (apologies to the native Frech speakers, I don't know where
> the accent is supposed to go :-).  The windShell is a nice
> attempt to duplicate the feature of the native shell, but it falls
> woefully short of the mark.  So, I'll switch because I have to, but
> WRS, don't *even* think of removing the INCLUDE_CONFIGURATION_5_2
> capabilities of VxWorks 5.3.x or it'll be time to find another
> kernel.
Indeed.
>   As always, these represent my personal opinions and are not
> necessarily representative of those held by my company or
> co-workers.  But, I know from my private discussions with many
> of the other VxWorks users, I am not alone in this sentiment.
>
Me too.
The NRAO is not responsible for my opinions, etc.
--
John Ford
National Radio Astronomy Observatory
Green Bank, WV 24944-0002
jford@nrao.edu
From claire.chaplais@wrs.com  Fri Nov 14 13:07:25 1997
From: Claire Chaplais <claire.chaplais@wrs.com>
Date: Fri Nov 14 13:07:29 PST 1997
Subject: Wind River Developers Conference
--=====================_879570122==_
Content-Type: text/plain; charset="us-ascii"
Dear Solutions Provider:
Don't miss out on your LAST CHANCE to submit an abstract and be part of the
Wind River Systems 1998 Developers Conference, entitled "IQ 1998: Smart
Solutions for
Smarter Products," to be held in San Francisco at the Fairmont Hotel, May
11-13,1998.
Developers, industry and technology experts in the embedded software
applications community are encouraged to submit papers for presentation at
the conference.  Topics may include, but are not limited to: Industry
Trends, Peripherals/Computing, Intelligent I/O, Development Tools, and
Communications (telecomm/datacomm).
**This is your last chance to submit your 100 word abstract for consideration!**
** Submission deadline is November 28, 1997 **
Please find attached the Call for Papers form -or- if you're digital, the
form can be found at http://www.wrs.com/dev-con
If you have any questions please contact Kellie Beakey, LKE Productions,
(415) 544-9300 or email at kellie@lke.com.
All forms should be submitted to Wind River Systems c/o LKE Productions,
1620 Montgomery St., Suite 120, San Francisco, CA  94111 or fax to (415)
544-9306.
Thank you and we look forward to your participation in the Wind River
Systems 1998 Developers Conference.
--=====================_879570122==_
Content-Type: application/rtf; charset="us-ascii"
Content-Disposition: attachment; filename="WRS~CFP.rtf"
{\rtf1\ansi \deff4\deflang1033{\fonttbl{\f1\froman\fcharset2\fprq2 Symbol;}{\f4\froman\fcharset0\fprq2 Times New Roman;}{\f5\fswiss\fcharset0\fprq2 Arial;}}{\colortbl;\red0\green0\blue0;\red0\green0\blue255;
\red0\green255\blue255;\red0\green255\blue0;\red255\green0\blue255;\red255\green0\blue0;\red255\green255\blue0;\red255\green255\blue255;\red0\green0\blue128;\red0\green128\blue128;\red0\green128\blue0;\red128\green0\blue128;\red128\green0\blue0;
\red128\green128\blue0;\red128\green128\blue128;\red192\green192\blue192;}{\stylesheet{\widctlpar \f4\fs20 \snext0 Normal;}{\s1\keepn\widctlpar \b\f5\fs20 \sbasedon0\snext0 heading 1;}{\*\cs10 \additive Default Paragraph Font;}{\*\cs15 \additive\ul\cf2
\sbasedon10 Hyperlink;}}{\info{\title The 1998 RSA Data Security Conference }{\author Preferred Customer}{\operator Layne Kaplan}{\creatim\yr1997\mo6\dy11\hr20\min16}{\revtim\yr1997\mo10\dy15\hr19\min3}{\printim\yr1997\mo10\dy7\hr19\min17}{\version2}
{\edmins2}{\nofpages2}{\nofwords462}{\nofchars2635}{\*\company  }{\vern57431}}\margt720\margb720 \widowctrl\ftnbj\aenddoc\hyphcaps0\formshade \fet0\sectd \linex0\endnhere {\*\pnseclvl1\pnucrm\pnstart1\pnindent720\pnhang{\pntxta .}}{\*\pnseclvl2
\pnucltr\pnstart1\pnindent720\pnhang{\pntxta .}}{\*\pnseclvl3\pndec\pnstart1\pnindent720\pnhang{\pntxta .}}{\*\pnseclvl4\pnlcltr\pnstart1\pnindent720\pnhang{\pntxta )}}{\*\pnseclvl5\pndec\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta )}}{\*\pnseclvl6
\pnlcltr\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta )}}{\*\pnseclvl7\pnlcrm\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta )}}{\*\pnseclvl8\pnlcltr\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta )}}{\*\pnseclvl9\pnlcrm\pnstart1\pnindent720\pnhang
{\pntxtb (}{\pntxta )}}\pard\plain \widctlpar \f4\fs20 {\b WIND RIVER SYSTEMS DEVELOPERS CONFERENCE
\par }{\b\i IQ 1998: Smart Solutions for Smarter Products
\par }{\b CALL-FOR-PAPERS FORM
\par }
\par
\par The Wind River Systems 1998 Developers Conference, {\b IQ 1998: Smart Solutions for Smarter Products,} will be held May 11-13, 1998, at The Fairmont Hotel in San Francisco, California.  Developers
 will be given the opportunity to give presentations on their applic
ations, products and/or research.  Proposals should address some aspect of embedded development or issues and product demonstration proposals should focus on the features and benefits of that product.
\par
\par {\b **  Due to the educational focus of this conference, product sales presentations will not be accepted.
\par }
\par You are encouraged to submit multiple proposals.  Please duplicate this form as necessary.
\par
\par \pard \qc\widctlpar {\b ** SUBMISSION DEADLINE:} {\b\ul  Friday, November 28, 1997}{\b  **}
\par \pard \widctlpar
\par \pard\plain \s1\keepn\widctlpar \b\f5\fs20 Please note: if you\rquote re digital, you can fill this form out online at http://www.wrs.com
\par \pard\plain \widctlpar \f4\fs20
\par Name:\tab ____________________________________________ Title:   ____________________________
\par
\par Organization: ___________________________________________________{\ul
\par }
\par Address 1: ______________________________________________________
\par
\par Address 2: ______________________________________________________
\par
\par City: ________________________________  State: ________ Zip: ___________  Country: ___________
\par
\par Phone:\tab _____________________________    Fax: ___________________________
\par
\par E-mail (required):  ___________________________________ URL:  _____________________________
\par
\par {\b *Conference topics to include, but are not limited to:  }{\b\i Industry Trends, Peripherals/Computing,
\par }\pard \fi720\li3600\widctlpar {\b\i     Development Tools and Communications}{\i
\par }\pard \widctlpar
\par Proposed title for your talk:
\par
\par ____________________________________________________________
\par
\par Is it an individual or panel presentation?:
\par
\par ___________________________________________________
\par
\par If the proposed talk is a panel, please list other speakers and organizations on a separate sheet.
\par
\par
\par \pard \widctlpar \shading1000\cbpat8 ON A SCALE OF 1 TO 5...how technical is your talk? (circle one)
\par
\par 1. \tab Suitable for consumption by anyone
\par 2. \tab Meatier technology introductions, legal discussions
\par 3. \tab Not for the faint of heart, but not just for engineers
\par 4. \tab Definitely geared towards developers, engineers & scientists
\par 5. \tab Recommended for interested specialists only
\par \pard \widctlpar
\par
\par (OVER)\page
\par Please also include the following or attach on a separate piece of paper:
\par
\par 100 word abstract of your presentation
\par
\par {\ul \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab
\par
\par \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab
\par
\par \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab
\par
\par \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab
\par
\par \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab
\par
\par \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab }
\par
\par 40 word brief distillation of your talk (for the brochure)
\par
\par {\ul \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab
\par
\par \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab
\par
\par \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab }
\par
\par 40 word personal biography
\par
\par {\ul \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab
\par
\par \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab
\par
\par \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab }
\par
\par 40 word organizational profile
\par
\par {\ul \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab
\par
\par \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab
\par
\par \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab \tab }
\par
\par Your classes will look much nicer on our website if you include:
\par
\par {\pntext\pard\plain\f1\fs20 \'b7\tab}\pard \fi-360\li360\widctlpar\tx360{\*\pn \pnlvlblt\pnf1\pnstart1\pnindent360\pnhang{\pntxtb \'b7}}A personal photo in electronic form (optional)
\par {\pntext\pard\plain\f1\fs20 \'b7\tab}A company or organizational logo in electronic form (optional)
\par \pard \fi1260\widctlpar
\par \pard \widctlpar E-mail graphics files separately to: {\b\i info@lke.com}
\par
\par Please mail your completed form to{\i
\par }{\b\f5
\par }\pard \li1440\widctlpar {\b\f5 Wind River Systems - IQ 1998: Smart Solutions for Smarter Products
\par c/o LKE Productions
\par 1620 Montgomery Street, Suite 120
\par San Francisco, CA 94111\tab \tab \tab \'85.or fax this to 415/544-9306.
\par }\pard \widctlpar
\par
\par Thank you for your submission!
\par }
--=====================_879570122==_--
From Wynn.Rostek-1@kmail.ksc.nasa.gov  Fri Nov 14 13:14:45 1997
From: Rostek-1 Wynn <Wynn.Rostek-1@kmail.ksc.nasa.gov>
Date: Fri Nov 14 13:14:48 PST 1997
Subject: Flaming debris from TCP/IP socket
To everyone that helped:
Thanks for all the hints and tips.  The program died in the accept call
when you sp(program) or broke the telnet connection after directly
invoking it from the shell.  Of course the program ran just dandy when
invoked from the shell.
This is just another example of how sneaky operating systems have
become.  The shell/nonshell was a red herring.  The problem was I had
deleted the line that initialized the size of the client sockaddr
during an edit.  Since I tend to cut and paste, the other two programs
had the same error.
Depending on what was left on the stack, accept would either work fine,
or totally trash the system.  (Even the shell on the serial port was
down.) Looks like the system didn't have time to complain on the way
down.  I miss my MMU.
Thanks!
Wynn
Wynn Rostek
Lead Engineer, Advanced Development Laboratory
DNX-20
Kennedy Space Center, FL 32899
wynn.rostek-1@ksc.nasa.gov
Voice: (407) 867-6770
Fax: (407) 867-7435
>
From cgrames@mdc.com  Fri Nov 14 14:17:22 1997
From: Charlie Grames <cgrames@mdc.com>
Date: Fri Nov 14 14:17:25 PST 1997
Subject: Discontinuation of support for VxWorks 5.2 -Reply
--MimeMultipartBoundary
Content-Type: text/plain
Content-Disposition: inline
To Mike Anderson and other interested parties:
I agree that dumping support for 5.2 so soon after introducing 5.3 is pretty crappy if 5.3 was not an
automatic upgrade, but I was not aware this was the case.  Obviously, I cannot speak for
everyone, but I do not recall paying a premium to upgrade to 5.3.
Also, forgive me if I sound naive, but what features did 5.2 provide that are not provided in the
current 5.3.1?  Am I missing the boat on some wonderful capabilities?  If so, not only would I be
interested in using them, but I would also want to lobby Wind River to ensure they remain in future
releases.
Charlie Grames
The Boeing Company
(314) 233-1956
Charles.R.Grames@boeing.com
--MimeMultipartBoundary--
From currie@ghg.net  Fri Nov 14 19:40:48 1997
From: currie@ghg.net (Alan Currie)
Date: Fri Nov 14 19:40:51 PST 1997
Subject: Re: Discontinuation of support for VxWorks 5.2 -Reply
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Not everyone has the luxury of the availability of a 5.3 BSP without a
considerable amount of effort.  That would be my issue.
--MimeMultipartBoundary--
From daemon@csg.lbl.gov  Sat Nov 15 04:00:50 1997
From: daemon@csg.lbl.gov
Date: Sat Nov 15 04:00:54 PST 1997
Subject: comp.os.vxworks newsdigest
Comp.Os.Vxworks Daily Digest    Sat Nov 15 04:00:46 PST 1997
        Subject: Gnu and STL
        Subject: Re: Gnu and STL
        Subject: MPC860 early device errata?
        Subject: Re: Skeleton or example device driver?
-------------------------------------------------------
Newsgroups: comp.os.vxworks
Subject: Gnu and STL
Date: Fri, 14 Nov 1997 17:27:29 -0500
From: Dzung Nguyen <nguyend2@ttc.com>
Organization: T.T.C.
Message-ID: <346CD051.A3DF8A22@ttc.com>
Hi,
I am wondering if anyone is successful in compiling either the HP or the
Silicon Graphic implementation of STL using the GNU compiler which comes
with Tornado?  If so, could you be so kind to give me some pointers on
how to configure the GNU to compile the STL?
Thank you very much in advance,
Dzung
---------------------------
Newsgroups: comp.os.vxworks
Subject: Re: Gnu and STL
Date: 14 Nov 1997 15:35:11 -0800
From: rkk@euphonix.com
Organization: Aimnet Information Services
Message-ID: <uen4jvykw.fsf@euphonix.com>
References: <346CD051.A3DF8A22@ttc.com>
Dzung Nguyen <nguyend2@ttc.com> writes:
>
> Hi,
>
> I am wondering if anyone is successful in compiling either the HP or the
> Silicon Graphic implementation of STL using the GNU compiler which comes
> with Tornado?  If so, could you be so kind to give me some pointers on
> how to configure the GNU to compile the STL?
>
> Thank you very much in advance,
>
> Dzung
>
I grabbed the SGI STL from Boris Fomitchev's page:
		(http://www.metabyte.com/~fbp/stl/index.html)
and made the following changes to stlcomp.h in the
section "gcc 2.7.2 settings" :
	commented out :
		#define __STL_DEFAULT_TYPE_PARAM 1
	and
		#undef __STL_CONST_CONSTRUCTOR_BUG
	and added:
		#undef __STL_DEFAULT_TEMPLATE_PARAM
With these changes, some old code I was trying to port
now compiles.  I haven't exhaustively tested it yet, just
run some small toy programs to test vectors, etc.
Good luck...
Russ
---------------------------
Newsgroups: comp.os.vxworks,comp.sys.powerpc.tech
Subject: MPC860 early device errata?
Date: Fri, 14 Nov 1997 22:00:31 -0800
From: "John Finley" <john@finley.com>
Organization: Netcom
Message-ID: <64jdrd$6rn@sjx-ixn2.ix.netcom.com>
Hello all,
I'm having cache problems with my MPC860 rev 0.2 chips,
and would like to somewhat-deterministically determine
if it is a problem with the ancientness of the chip, or
if it is something else I'm doing.  My guess says 80%
chance it's the chip, 20% chance something else, but I
don't want to just "hope it goes away" with the next
batch of boards....
Do any of you packrats out there have device errata for
any rev 0.x MPC860s?  The moto web site has it for
rev A.2 and rev A.3, but no rev 0.x.  Or know for SURE
of cache problems with 0.x chips?
Thanks,
John
P.S. This is cross-posted to comp.os.vxworks since
     VxWorks people are so darn smart.
- --------------------------------------------------
John Finley                 Engineering Consultant
john@finley.com                  Real Time Systems
(619) 689-0032                Networking Protocols
- --------------------------------------------------
---------------------------
Newsgroups: comp.os.vxworks
Subject: Re: Skeleton or example device driver?
Date: Mon, 10 Nov 1997 22:32:56 -0600
From: krishna@ttl.nectec.or.th
Organization: Deja News Posting Service
Message-ID: <879220005.31682@dejanews.com>
Reply-To: krishna@ttl.nectec.or.th
>In article <345E4C0B.529D@llnl.gov>, Doug Owens  <owens2@llnl.gov> wrote:
>>We got an App Note with Tornado 1.0 called
>>"Upgrading a vxWorks BSP for Tornado 1.0" that
>>has skeleton code for serial drivers.  I think there
>>are files in the distribution also.
>
>Yes, I saw these (at least, I saw the code in the distribution, which
>I assume is the same as you are talking about).  Part of the problem
>is terminology (I've run into that here over the last couple of days).
>The term "driver" covers at least 2 separate concepts related to this:
>
>    the "driver" is the code that diddles the I/O chips to get them to
>    do good stuff (I'll call this the "device side")
>
>    the "driver" is the code that implements the open/close/read/write
>    abstraction visible to users of the driver (the "VxWorks side")
>
>Both of these are normally needed to create a functional driver.  The
>former is basically what is encompassed by the code in the Tornado
>target/src/drv directory (e.g., the templateSio.c file that I assume
>you are referring to).  The latter is discussed in section 3.9 of the
>VxWorks Programmer's Guide, and a couple of hypothetical generic
>drivers (xxDrv and arkDrv) are outlined.  What I was looking for was a
>complete driver (merging the items talked about with the xxDrv and
>arkDrv examples) that stubbed the "device side", but fleshed out the
>"VxWorks side".
>
>ted
>
>
I am not sure what you are looking for. Probably you are interested in
xxioctl() function, which is used for device specific operations. This
should be the function that diddles the I/O chips. You can find this in
VxWorks Programmer's Guide, section 3.3.7.
Krishna
- --------------------------------
Krishna Rao
Telecom Technology Lab., NECTEC
Bangkok, Thailand
Fax: (66-2)9550284
Ph.: (66-2)9550285 x 704
- --------------------------------
- -------------------==== Posted via Deja News ====-----------------------
      http://www.dejanews.com/     Search, Read, Post to Usenet
---------------------------
End of New-News digest
**********************
From mam@pluto.dspt.com  Sat Nov 15 11:22:11 1997
From: "Mark Menge" <mam@pluto.dspt.com>
Date: Sat Nov 15 11:22:15 PST 1997
Subject: Does your board crash and burn with a few serial interrupts?
Since I have been burned by lousy firmware programmers in the past,
I decided to write some simple diagnostics for serial, scsi and
ethernet so our production people could run them before shipping bad boards.
This test passed OK on a GMSV46 board and a MVME147 board.
We are in the process of evaluating a MVME2604e board, to see if it
is a reliable board. Unfortunately this test craps out on the 2604 in about
300 milliseconds.
Can someone run this code to see if their boards do the same thing?
Does anyone know if there is a suite of diagnostic code already
available?
Instructions:
1. Compile & download
2. Strart spray_serial
    ->sp spray_serial
3. If it is still alive, crank up the output:
    ->sprayDelay = 0
4. Set sprayStopFlag to stop
    -> sprayStopFlag = 1
My 2604e will output on the other serial ports for a half second and
then stop in the io system in the semTake routine.
#include	<vxWorks.h>
#include 	<config.h>
#include	<ioLib.h>
#include	<iosLib.h>
#include	<stdioLib.h>
#include	<semLib.h>
#define MAX_SERIAL 4
int sprayStopFlag;
int sprayDelay = 1;
int spray_serial()
{
 int i;
 int fd[MAX_SERIAL];
 char dev[40];
 for (i = 1; i <  MAX_SERIAL; i++) {
  sprintf(dev, "/tyCo/%d", i);
  fd[i] = open(dev, O_RDWR, 0);
  if (fd[i] > 0) {
   printf("Opened %s \n", dev);
   ioctl (fd[i], FIOBAUDRATE, 9600);
  }
 }
 while (!sprayStopFlag) {
  for (i = 1; i < MAX_SERIAL; i++) {
   if (fd[i] > 0)
    write(fd[i], "This port is OK", 5);
  }
  if (sprayDelay)
   taskDelay(sprayDelay);
 }
 for (i = 1; i <  MAX_SERIAL; i++) {
  if (fd[i] > 0)
   close(fd[i]);
 }
 return OK;
}
From mmcquade@aa.net  Sat Nov 15 21:29:57 1997
From: Mike McQuade <mmcquade@aa.net>
Date: Sat Nov 15 21:30:00 PST 1997
Subject: Re: Does your board crash and burn with a few serial
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
At 11:22 AM 11/15/97 PST, you wrote:
>Submitted-by mam@pluto.dspt.com  Sat Nov 15 11:22:11 1997
>Submitted-by: "Mark Menge" <mam@pluto.dspt.com>
>
>
>This test passed OK on a GMSV46 board and a MVME147 board.
>We are in the process of evaluating a MVME2604e board, to see if it
>is a reliable board. Unfortunately this test craps out on the 2604 in about
>300 milliseconds.
>
Mark,
How is your interrupt priority set in config.h ?
The default WRS way is to have ALL on the external interrupts set to
the same priority (15), we have found that the 2603 in our application
needs the external interrupts prioritized.
You might try setting SRC0, to 15, and droping the other
rups down to 14. (see config.h)
Just a shot in the dark.
Are you running Jumbo patch #3, with the 604 ARCH patch ?
If you answer yes to the Jumbo #3 question, then call WRS,
and get the latest RavenMpic.c file, this just got changed
about a week ago, with the previous RavenMpic.c file, we were
having bad lockups with SCSI on Jumbo #3, I know the new file
fixed some interrupt stuff.
I hope there isn't a big bug in the Serial stuff, Im going
to be using it for an external Voice Recognition box.
Mike.
--MimeMultipartBoundary--
From daemon@csg.lbl.gov  Sun Nov 16 04:00:51 1997
From: daemon@csg.lbl.gov
Date: Sun Nov 16 04:00:56 PST 1997
Subject: comp.os.vxworks newsdigest
Comp.Os.Vxworks Daily Digest    Sun Nov 16 04:00:48 PST 1997
        Subject: Re: Startup file
-------------------------------------------------------
Newsgroups: comp.os.vxworks
Subject: Re: Startup file
Date: 11 Nov 1997 11:47:19 GMT
From: gj@mail.ast.cam.ac.uk (Gareth Jones)
Organization: Royal Greenwich Observatory, Cambridge (UK)
Message-ID: <649gk7$9p7$1@lyra.csx.cam.ac.uk>
References: <3467869B.1738@radonc.washington.edu>
Hi,
The following code illustrates a basic startup script showing
a few of things that can be added:
- ----------------------------------------------------
#
# VxWorks startup script
#
# Add user login names and passwords
loginUserAdd "user1", "rQrTEzeRze"
# Set the shell prompt and the login text
shellPromptSet "vxWorks ->"
loginStringSet "MVME147 vxWorks\n\nlogin: "
# Add a machine to the host table
hostAdd ("lws1", "172.71.4.4")
# Define the backspace as the delete key
tyBackspaceSet 0177
# Change directory to the application and load it
cd "/system_code/v1.1"
ld < syscode
# Run the application
sp maintask
- -----------------------------------------------------
Things to note are:
1.	You need to put the location of the startup script
	in the boot parameters, for example:
boot device            : ln
processor number       : 0
host name              : Mars
file name              : /system_code/vxWorks
inet on ethernet (e)   : 172.71.9.222:ffff0000
inet on backplane      :
host inet (h)          : 172.71.9.70
gateway inet (g)       :
user (u)               : user1
ftp password (pw)      :
flags                  : 0x08
target name (tn)       : Phobos
startup script         : /system_code/sc.stp    <<<<<
other (o)              :
2.	The user name (u) above should be the name of a user
	that has access to files in the /system-code directory
	since VxWorks uses the username to 'login' and get the
	file (see the manual).
3.	The user has a '.rhosts' file in their root directory
	containing the target name of the VxWorks rack (again
	see the manual).
Hope that helps. :)
Gareth Jones
RGO Technology Division
---------------------------
End of New-News digest
**********************
From jean-charles.chassot@broadnet.ascom.ch  Mon Nov 17 00:36:22 1997
From: "Jean-Charles Chassot" <jean-charles.chassot@broadnet.ascom.ch>
Date: Mon Nov 17 00:36:29 PST 1997
Subject: RE: Template class instantiation fails on the GNU2.7.2.
This is a multi-part message in MIME format.
------=_NextPart_000_0015_01BCF33C.382C35A0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi,
last week I faced the trouble you had in recompiling your templates with =
the new compiler of Tornado 1.0.1 on PC.
Trying different configurations, I finally discovered that the compiler =
exports (T) the symbols declared below the declaration of the =
destructor, and keep internal (t) the symbols declared above the =
destructor. I've no logical explanation for this behaviour, but moving =
the declaration of the destructor on top of the declarations solved our =
troubles.
Please let me know if you got another way to workaround.
Here after comes a small demonstration of this 'internal/external' game.
// start of demo : start of demo : start of demo : start of demo : start =
of demo : start of demo :=20
// COMPILATION'S COMMAND
// t:\tornado.1.0.1\host\x86-win32\bin\cc68k \
//    -BT:\Tornado.1.0.1\host\x86-win32\lib\gcc-lib\ -I. -c test.cc
// EXAMINE THE OUTPUT FILE
// >nm68k test.o
// 00000010 T __$_t7Message1Z14TypicalMessage
//          U ___builtin_delete
// 00000000 t ___gnu_compiled_cplusplus
// 00000000 t ___t7Message1Z14TypicalMessage
// 00000040 T _msgBody__Ct7Message1Z14TypicalMessage    <-- EXTERNAL =
SYMBOL
// 00000032 t _sizeOfBody__Ct7Message1Z14TypicalMessage <-- INTERNAL =
SYMBOL ??????
// 00000000 t gcc2_compiled.
// COMILER VERSION
// gcc version cygnus-2.7.2-960126
// xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
//         TEST PROGRAM
// xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
// template class declaration
template <class MsgType>
class Message=20
{
public:
  Message();
  unsigned long sizeOfBody () const;
  ~Message(); =20
=20
  const void* msgBody () const;
private:
  MsgType body;
};
// members implemenation
template <class MsgType>
Message<MsgType>::Message()
{}
template <class MsgType>
Message<MsgType>::~Message()
{}
template <class MsgType>
unsigned long Message<MsgType>::sizeOfBody () const=20
{ return sizeof(MsgType); }
template <class MsgType>
const void* Message<MsgType>::msgBody() const
{ return (const void*) &body; }
typedef struct TypicalMessage
{=20
  int p1;
  int p2;
} TypicalMessage;
template class Message<TypicalMessage>;
// end of demo : end of demo : end of demo : end of demo : end of demo : =
end of demo :=20
.........////////////////////////////// Chassot Jean-Charles
........////.......///..////.......///
.......///....///////..///..../////// Public Networks
......///....///////..///..../////// Ascom Hasler Ltd
.....///....///////..///..../////// Morgenstrasse 129
....///....///////..///..../////// CH-3018 Berne
...////.......///..////.......///
..//////////////..////////////// Tel +41 31 999 19 41
./////////....../////////////// Fax +41 31 999 30 57
////////////////////////////// jean-charles.chassot@broadnet.ascom.ch
------=_NextPart_000_0015_01BCF33C.382C35A0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.71.1712.3"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 size=3D2>Hi,</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2>last week I faced the trouble you =
had in=20
recompiling your templates with the new compiler of Tornado 1.0.1 on=20
PC.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2>Trying different configurations, I =
finally=20
discovered that the compiler exports (T) the symbols declared below the=20
declaration of the destructor, and keep internal (t) the symbols =
declared above=20
the destructor. I've no logical explanation for this behaviour, but =
moving the=20
declaration of the destructor on top of the declarations solved our=20
troubles.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2></FONT><FONT color=3D#000000 size=3D2>Please let me =
know if you=20
got another way to workaround.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Here after comes a small demonstration of this=20
'internal/external' game.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2>// start of demo : start of demo : =
start of demo=20
: start of demo : start of demo : start of demo : </FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>// COMPILATION'S COMMAND<BR>//=20
t:\tornado.1.0.1\host\x86-win32\bin\cc68k \<BR>//&nbsp;&nbsp;&nbsp;=20
-BT:\Tornado.1.0.1\host\x86-win32\lib\gcc-lib\ -I. -c =
test.cc</FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>// EXAMINE THE OUTPUT FILE<BR>// &gt;nm68k =
test.o<BR>//=20
00000010 T=20
__$_t7Message1Z14TypicalMessage<BR>//&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;=20
U ___builtin_delete<BR>// 00000000 t ___gnu_compiled_cplusplus<BR>// =
00000000 t=20
___t7Message1Z14TypicalMessage<BR>// 00000040 T=20
_msgBody__Ct7Message1Z14TypicalMessage&nbsp;&nbsp;&nbsp; &lt;-- EXTERNAL =
SYMBOL<BR>// 00000032 t _sizeOfBody__Ct7Message1Z14TypicalMessage &lt;-- =
INTERNAL SYMBOL ??????<BR>// 00000000 t =
gcc2_compiled.</FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>// COMILER VERSION<BR>// gcc version=20
cygnus-2.7.2-960126</FONT>&nbsp;</DIV>
<DIV><FONT size=3D2><BR>//=20
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx<BR>//&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;=20
TEST PROGRAM<BR>// xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx</FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>// template class declaration<BR>template &lt;class=20
MsgType&gt;<BR>class Message <BR>{<BR>public:<BR>&nbsp; =
Message();<BR>&nbsp;=20
unsigned long sizeOfBody () const;<BR>&nbsp; ~Message();&nbsp; <BR> =
<BR>&nbsp;=20
const void* msgBody () const;</FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>private:<BR>&nbsp; MsgType =
body;<BR>};</FONT>&nbsp;</DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>// members implemenation<BR>template &lt;class=20
MsgType&gt;<BR>Message&lt;MsgType&gt;::Message()<BR>{}</FONT>&nbsp;</DIV>=
<DIV><FONT size=3D2>template &lt;class=20
MsgType&gt;<BR>Message&lt;MsgType&gt;::~Message()<BR>{}</FONT>&nbsp;</DIV=
>
<DIV><FONT size=3D2>template &lt;class MsgType&gt;<BR>unsigned long=20
Message&lt;MsgType&gt;::sizeOfBody () const <BR>{ return =
sizeof(MsgType);=20
}</FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>template &lt;class MsgType&gt;<BR>const void*=20
Message&lt;MsgType&gt;::msgBody() const<BR>{ return (const void*) =
&amp;body;=20
}</FONT>&nbsp;</DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>typedef struct TypicalMessage<BR>{ <BR>&nbsp; int=20
p1;<BR>&nbsp; int p2;<BR>} TypicalMessage;</FONT>&nbsp;</DIV>
<DIV><FONT size=3D2><BR>template class=20
Message&lt;TypicalMessage&gt;;</FONT>&nbsp;</DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2>// end of demo : end of demo : end =
of demo : end=20
of demo : end of demo : end of demo : </FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#000000 =
size=3D2>.........////////////////////////////// Chassot=20
Jean-Charles<BR>........////.......///..////.......///<BR>.......///..../=
//////..///....///////=20
Public Networks<BR>......///....///////..///..../////// Ascom Hasler=20
Ltd<BR>.....///....///////..///..../////// Morgenstrasse=20
129<BR>....///....///////..///..../////// CH-3018=20
Berne<BR>...////.......///..////.......///<BR>..//////////////../////////=
/////=20
Tel +41 31 999 19 41<BR>./////////....../////////////// Fax +41 31 999 =
30=20
57<BR>////////////////////////////// <A=20
href=3D"mailto:jean-charles.chassot@broadnet.ascom.ch">jean-charles.chass=
ot@broadnet.ascom.ch</A></FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV></BODY></HTML>
------=_NextPart_000_0015_01BCF33C.382C35A0--
From mmcquade@pop.aa.net  Mon Nov 17 09:08:17 1997
From: Mike McQuade <mmcquade@pop.aa.net>
Date: Mon Nov 17 09:08:20 PST 1997
Subject: Tornado on Windows NT
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
All,
We are strongly considering moving from HP-UX to Win NT 4.0 for
our development environment. I have a few questions for those
folks who are using NT.
1. What Source Control system do you use ?
 - how do you like it ?
2. What is your biggest complaint about Tornado on NT ?
3. If you have a multi developer environment, where do you keep
the Tornado tree ?
ie:
on one machine ?
on a seperate server ?
everyone keeps a copy on their local hard drive ?
Thanks.
Mike.
--MimeMultipartBoundary--
From uchenick@tis4000.com  Mon Nov 17 13:22:21 1997
From: Gordon Uchenick <uchenick@tis4000.com>
Date: Mon Nov 17 13:22:28 PST 1997
Subject: MVME162-532 under vxWorks 5.1
Has anyone out there tried (and been able!) to get the MVME162-532 to work
under vxWorks 5.1? WRS sent me the BSP from 5.2 and I built vxWorks using
the libraries that came with that BSP instead of the ones that I had for
5.1, but that doesn't work. System hangs just after "Starting at 0x20000". Any solutions or a definite "No Way!" would be appreciated.
TIA,
Gordon Uchenick
410-771-0022
uchenick@tis4000.com
From mea@mclean.sparta.com  Mon Nov 17 14:10:35 1997
From: "Mike Anderson" <mea@mclean.sparta.com>
Date: Mon Nov 17 14:10:42 PST 1997
Subject: Re: Discontinuation of support for VxWorks 5.2 -Reply
--MimeMultipartBoundary
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
>Submitted-by: Charlie Grames <cgrames@mdc.com>
>
>To Mike Anderson and other interested parties:
>
>I agree that dumping support for 5.2 so soon after introducing 5.3 is pretty
crappy if 5.3 was not an
>automatic upgrade, but I was not aware this was the case.  Obviously, I cannot
speak for
>everyone, but I do not recall paying a premium to upgrade to 5.3.
>
>Also, forgive me if I sound naive, but what features did 5.2 provide that are
not provided in the
>current 5.3.1?  Am I missing the boat on some wonderful capabilities?  If so,
not only would I be
>interested in using them, but I would also want to lobby Wind River to ensure
they remain in future
>releases.
>
Greetings!
  Well, there are several issues.  First, when Tornado came out,
there was not an automatic upgrade policy.  So those of us with 5.2
either had to pay extra money (over and above our yearly maintenance
fees) to get Tornado.  Also, as pointed out by one of the other
posters, there are some older/custom hardware sets out there that
don't have 5.3.x BSPs.  This means either you continue running 5.2
with an "unsupported" O/S or you port/pay to port your 5.2 BSP to
5.3.x.  This is an annoyance at the least, and potentially a major
expense.
  As for the features of 5.2 vs. 5.3.x, there is no questions that
5.3.x has more pure "features" (or is that bugs? ;-) than 5.2.
It's really not an issue of features, but rather, the way you access
them.  Remember that Tornado was architected for the "skinny" client.
That is, it was targeted to remove major sources of "RAM-cram" off
of the target like the symbol table and the target shell and move
them to the host.  For the "deeply embedded" targets like I20 and
truck transmissions, etc., this is a laudable goal.  In order
to support this, WRS introduced the WindShell, launcher, target
server, etc. and then host-locked these suckers with a licensing
manager that has proven itself to be problematic at best for most
users.  Some folks love the launcher, I view it as just a GUI that
actually executes TCL scripts or other applications.  Evidence
what happens when you configure a target server, the launcher
simply builds the command line based on your entries and execls
the command to the O/S to see what I mean.
  However, by moving so much of the target code over to the host, we
have increased the reliance of the target on the "network" connection.
In the case of Ethernet, this introduces increased traffic, and
since Ethernet is really a stochastic process, it also introduces
increased latency into our real-time systems.  Approaches like the
WindShell try to reduce that latency by doing many of the commands
locally, e.g., the "ls" command.  However, the WindShell won't allow
you access to local file systems like RAM disks without custom hacks
to include usrLib onto the target load image.  Also, do you believe
that the browser and all of those graphical representations of
memory usage, spy output, loaded programs and system vs. user tasks
come for free?  There is a networking price to be paid for all of
that stuff.  Increased traffic means more interrupts, more CPU
time eaten up by the WDB task to format those messages, more
handshaking with non-real-time hosts to display it, etc.
  Another example, would be on an "out-of-the-box" version of Tornado
running on the target, try to load a piece of code that calls
"printErrno".  From the WindShell, printErrno works, but when you
try to load the code you'll get an unknown symbol failure for
printErrno.  It's there, but it's not.  This same code loads and runs
like a champ in a native target shell environment (even an
out-of-the-box flavor).
  This is not to say that Tornado is a bad thing altogether.  There
are some environments in which having multiple WindShells attached
to the same target is a useful thing.  Of course, I can also get that
with RTI's re-entrant native shell tool.  Also, there have been
many improvements in the target-resident O/S.  New capabilities
such as bootp, RIP, IP-Multicast, PPP etc. (just to name a few)
are welcome additions.
  The point is, there are things that work in the native target shell
that just don't work the same way (or don't work at all) in the
Tornado/Windshell approach.  My concern is that in doing away with
the "old" 5.2 way of thinking (by eliminating 5.2), that WRS will
soon decide that Tornado is the only way of doing things.  They
can therefore further cut their support costs by eliminating the old
5.2-style tools as well.  Very Orwellian of me to be sure, but it
wouldn't be the first time I've seen this kind of thing happen.
Regards,
---------------------------------------------------------------------
|Michael E. Anderson        | Voice -> 703 448 1683 x235            |
|Chief Engineer             | FAX   -> 703 893 5494                 |
|mea@mclean.sparta.com      | http://www.mclean.sparta.com          |
|___________________________|_______________________________________|
|             SPARTA, Inc.              |                           |
|     /\\     C4I Operation             |"Software Development is   |
|    ///\\    7926 Jones Branch Drive   | like making a baby...     |
|   /////\\   Suite 900                 | You can't make a baby in  |
|  /////  \\  McLean, VA 22102          | one month by impregnating |
| / \\\\\  \\ 703-448-0210              | nine women.               |
| \  \\\\\ //                           |                           |
|  \  //////                            | Some things just take     |
|   \//////   SPARTA                    | time."                    |
|    \////    Pride In Performance      |                           |
|     \//     --------------------      |                           |
---------------------------------------------------------------------
--MimeMultipartBoundary--
From thomas.arand@oen.siemens.de  Tue Nov 18 03:01:25 1997
From: thomas.arand@oen.siemens.de (Arand, Thomas)
Date: Tue Nov 18 03:01:29 PST 1997
Subject: Galileo-4 evaluation board and vxWorks B
--MimeMultipartBoundary
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi all,
Did anyone port vxWorks to the Galileo-4 evaluation board. I would   =
appreciate some hints:
1) My board was switched to little Endian support by anyone before=21 What =
  =
must I do resetting it? (I already know about Jumper J28 and Jumper   =
Resistor JR 13/14.)
2) Is there an easy way to add an ethernet PCI board?
Thanks in advance,
 Thomas Arand
 ----------------------------------------------------------------------
Thomas Arand                              Siemens AG
Tel.  +49 - 89 - 722 42296
Fax. +49 - 89 - 722 26572
thomas.arand=40oen.siemens.de
--MimeMultipartBoundary--
From josipdi@gemse.fr  Tue Nov 18 03:34:24 1997
From: Diane JOSIPOVICI <josipdi@gemse.fr>
Date: Tue Nov 18 03:34:28 PST 1997
Subject: Relocatable code
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi all !
I am working on custom 68360 target, with a custom BSP (vxworks 5.3),
where boot and application are running in Flash memory.
In order to download code into Flash memory, we have some piece of code
that can run in RAM, and write code in Flash.
To do that we use a method that works, but is not very "elegant" : in C
source file, we use a pragma command (#pragma -Mcp) used before we
ported our application on vxworks !
One problem with this method is that this piece of code can't be used to
run in flash, then we have some code duplicated. And this method seems
to be not supproted... at least, not documented (like other pragma
options).
I tried to use -fpic or -fPIC cc68k compiler option. But It doesn't
work.
Is there any other method to make code relocatable ?
Any help will be welcome !
regards,
Diane JOSIPOVICI -  Software Engineer  -      GE Medical System
                                                283, rue de la Miniere
email : josipdi@gemse.fr                        78533 BUC
Tel   : (33) - 1.30.70.98.29                    FRANCE
Fax   : (33) - 1.30.70.46.70

--MimeMultipartBoundary--
From daemon@csg.lbl.gov  Tue Nov 18 04:01:09 1997
From: daemon@csg.lbl.gov
Date: Tue Nov 18 04:01:13 PST 1997
Subject: comp.os.vxworks newsdigest
Comp.Os.Vxworks Daily Digest    Tue Nov 18 04:01:06 PST 1997
        Subject: Re: POSIX message queue basics
        Subject: Compact PCI Operating systems
        Subject: load vxWorks on a PC
-------------------------------------------------------
Newsgroups: comp.os.vxworks
Subject: Re: POSIX message queue basics
Date: Thu, 13 Nov 1997 14:49:59 -0500
From: Alexander Karstens <karstens@wg.com>
Organization: Wandel & Goltermann Technologies
Message-ID: <346B59E7.769BD981@wg.com>
References: <01bcf061$4222c480$790000a0@smccurdy.comsatrsibb.com>
 Did you configure and rebuilt the kernel with the INCLUDE_POSIX_ALL
option?
Hope that helps.
Alexander Karstens
---------------------------
Newsgroups: comp.os.qnx,comp.os.vxworks
Subject: Compact PCI Operating systems
Date: Mon, 17 Nov 1997 16:38:25 +0000
From: Murray Elliot <murray@sunny.demon.co.uk>
Organization: Sunnyside Systems Ltd.
Message-ID: <HcHtwCABMHc0EAJ+@sunny.demon.co.uk>
I am currently evaluating the options for the design of a new embeded
system based around compact PCI. The requirements are as follows:
1. Reliable!
2. Able to communicate with Windows'95 control system via 10base2
interface.
3. Able to receive data from PCI bus-master and store to disk (probably
SCSI) at 1.6MBytes/second.
I've noticed that a few PCI systems vendors advertise support for QNX,
VxWorks and Windows '95/NT. I know enough about Windoze, but nothing
about QNX or VxWorks. I am seeking opinions on which operating system
would be the preferred choice for this kind of application, and where I
should start looking for comparative reviews, benchmarks, etc.
Sorry if this has already been done to death! I don't want to start a
flame-war or create rambling threads, but I'd much appreciate any advice
from experts out there.
Thanks in advance.
- --
Murray Elliot
---------------------------
Newsgroups: comp.os.vxworks
Subject: load vxWorks on a PC
Date: Thu, 13 Nov 1997 14:20:08 -0800
From: Joydeep Roy <joydeep.roy@tek.com>
Organization: tektronix,Inc, Wilsonville, OR
Message-ID: <346B7D18.6D43@tek.com>
I would like to know how easy or difficult it is to
load vxWorks on a PC. What are the basic steps
thanks
- --
_____________________________________________________________________
joydeep roy                                            Tektronix, Inc
joydeep.roy@tek.com                                   Wilsonville, OR
(503)685-2486                                      http://www.tek.com
---------------------------
End of New-News digest
**********************
From brett.smith@wg.com  Tue Nov 18 07:58:48 1997
From: "Brett Smith"<brett.smith@wg.com>
Date: Tue Nov 18 07:58:51 PST 1997
Subject: internet checksum
--MimeMultipartBoundary
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
     Does vxWorks contain (via #include, or with the TCP/IP stack) an
     internet checksum that can be used for IP headers, and ICMP messages?
     I can easily add the checksum code if necessary, but I wish to avoid
     adding redundant code to the image.
     Thanks,
     BWS
--MimeMultipartBoundary--
From prb@neon.jhuapl.edu  Tue Nov 18 08:35:57 1997
From: prb@neon.jhuapl.edu (Paul R. Bade)
Date: Tue Nov 18 08:36:00 PST 1997
Subject: Re: internet checksum
"Brett Smith"<brett.smith@wg.com> writes:
>
>
>      Does vxWorks contain (via #include, or with the TCP/IP stack) an
>      internet checksum that can be used for IP headers, and ICMP messages?
>
>      I can easily add the checksum code if necessary, but I wish to avoid
>      adding redundant code to the image.
>
The IP checksum utility is in Wind's kernel.
You can demonstrate this via the shell.   -> lkup "checksum"
However, Wind does not provide an include ".h" file for the prototype.
So you will need to declare it yourself.
unsigned short checksum(unsigned short *addr, int len);
I have done this in the past and it works fine.
+====================================================================+
|       __     ____         __     __                                |
|      /\ \   /  \ \       /\_\__ /\ \      Johns Hopkins University |
|     /  \_\ | /\ \ \     / / /\_\\ \ \     Applied Physics Lab.     |
|    / /\ | |\ \/  \ \   / / / / / \ \ \                             |
|   /  \/ |_| \  /\ \_\ / / / / /   \ \ \   Paul R. Bade             |
|  / /\__/_/   \ \ \/_// / / / /    / / /   (301)-953-6000 x8681     |
| / / /         \ \_\  \ \/ / /    / / /    bade@jhuapl.edu          |
| \/_/           \/_/   \__/_/     \/_/                              |
|               __     ____         __       __                      |
|              /\ \   /  \ \       /\ \     /\ \                     |
|             /  \_\ | /\ \ \     /  \_\   /  \ \                    |
|            / /\ | |\ \/  \ \   / /\ |_| / /\ \ \                   |
|           /  \/ |_| \  /\ \_\ / / / | | \/ /  \ \                  |
|          / /\  / /   \ \ \/_// / / / /    / /\ \_\                 |
|          \ \/ / /     \ \_\  \ \/ / /     \/ / / /                 |
|           \__/_/       \/_/   \__/_/        /_/_/                  |
|                                                                    |
+====================================================================+
From espin@idiom.com  Tue Nov 18 09:05:34 1997
From: Geoffrey Espin <espin@idiom.com>
Date: Tue Nov 18 09:05:37 PST 1997
Subject: Re: Relocatable code
--MimeMultipartBoundary
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Diane,
> In order to download code into Flash memory, we have some piece of code
> that can run in RAM, and write code in Flash.
> To do that we use a method that works, but is not very "elegant" : in C
> source file, we use a pragma command (#pragma -Mcp) used before we
> ported our application on vxworks !
>
> One problem with this method is that this piece of code can't be used to
> run in flash, then we have some code duplicated. And this method seems
> to be not supproted... at least, not documented (like other pragma
> options).
Here is a solution which I've implemented in the past on GNU/68k.
I am assuming you are running out of the same FLASH you want to update.
1. load the FLASH image into DRAM.
2. write a self-contained sysFlashUpdate()
   routine (e.g. does not call any subroutines even bcopy()),
   does erase and write cycle in same routine.  At end of
   routine jump to same location sysToMonitor() would calculate
   (you have to reboot).
3. bcopy() this routine into some malloc()'d memory; use an
    initialized const symbol to denote end of routine to calculate length.
4. intLock() and call pFunc(buf,len,offset) -- where pFunc is the malloc'd
and "relocated" copy of your standalone sysFlashUpdate() function.
When developing this code, first see if you can just write
a standalone routine copy it to DRAM and run it and come back
normally to your running OS.  Then gradually add the features.
The toughest thing is writing a tight bullet-proof Erase/Write
routine.  Obviously, error handling for bad sectors is not possible...
you've got one bad board.  :-)  Also, when debugging you don't need
to update thoe whole FLASH try just modifying the last sector
and then being able to return normally.
Geoff
--
Geoffrey Espin espin@idiom.com
--MimeMultipartBoundary--
From biberdot@wpg.lmcda.lmco.com  Tue Nov 18 12:03:51 1997
From: "Biberdorf, Terry @ WIN" <biberdot@wpg.lmcda.lmco.com>
Date: Tue Nov 18 12:03:56 PST 1997
Subject: Problem booting mv3604
I have installed tor101_mv2600_collection3.tar patch for the mv2600 BSP.
I edited the config.h to specify the new memory size and the
DEFAULT_BOOT_LINE
to specify my boot host ip,client ip, and a full path to find vxWorks
boot file.
then on my sun workstation:
(1) make clean
(2) make bootrom_uncmp
(3) make vxWorks
(4) elfToBin <bootrom_uncmp >boot.bin
(5) chmod 666 boot.bin
(6) cp boot.bin /tftpboot/boot.bin
from the powerpc default boot page booting with jumper J2 set on pins 2-3
through the gui menu I have set various boot variables
boot-device - net
boot file - <blank>
boot command - boot
client ip -  PowerPC ip address
host ip - Sun ip address
net-cfg-nethod - tftp
then I open the ok prompt and enter
(1) load-base h# 100 + to load-base
(2) load /pci/ethernet@e:<host ip>,boot.bin,<powerPC ip>
(3) load-base h# 100 - to load-base
(4) load-base 100000 ff000000 (gflash)
then when I power down the PowerPC and move jumper J2 to pins 1-2
and power the card back up, I get what starts to look like vxWorks
booting
and then a fail message
"network interface lse unknown"
"can't load boot file!! "
I was expecting the device network to be dc not lse.  As from the
config.h file.
Thanks in advance
Terry Biberdorf
Firmware Engineer
Lockheed Martin
terry.biberdorf@lmco.com
From npr@jach.hawaii.edu  Tue Nov 18 16:20:36 1997
From: Nick Rees <npr@jach.hawaii.edu>
Date: Tue Nov 18 16:20:39 PST 1997
Subject: Tornado configuirations that are compatible with 5.2 tools
I am running an application (EPICS) that needs many of the 5.2 features
(startup script, login shell etc) and I am trying to work out a
suitable VxWorks 5.3 configuration that attempts to get the best of
both worlds. All my symbols are loaded via the startup script.
So far:
1. If I have INCLUDE_CONFIGURATION_5_2 and INCLUDE_WDB the symbol table
   synching doesn't seem to work - at least the host shell doesn't seem to
   see the target symbols, and the debugger doesn't work.
2. The only way I have been able to get debugging is to INCLUDE_RDB and
   comment out INCLUDE_WDB, and then connect with the RDB debugging mode
   - this, of course, turns off all the features of the Tornado tools.
What I would like to have is to be able to see the symbol table from
both host and target, and be able to have both the Tornado tools and
the debugger working with the same configuration.
So, before I spend too much more time, does anyone have a neat solution
or know what am I doing wrong? I am a bit confused that in option (1)
above, INCLUDE_WDB is defined for the duration of configAll.h (and this
pulls in a number of other defines), but is then turned off in
usrConfig.c by the INCLUDE_CONFIGURATION_5_2. I am guessing that this
may be why the symbol table synching doesn't work since the
configuration may not be well defined.
Nick Rees
Joint Astronomy Centre                    Ph:       +1 (808) 961-3756
660 N. Aohoku Place                       Fax:      +1 (808) 961-6516
Hilo, HI.  96720                          Internet: npr@jach.hawaii.edu
From daemon@csg.lbl.gov  Wed Nov 19 04:00:45 1997
From: daemon@csg.lbl.gov
Date: Wed Nov 19 04:00:49 PST 1997
Subject: comp.os.vxworks newsdigest
Comp.Os.Vxworks Daily Digest    Wed Nov 19 04:00:40 PST 1997
        Subject: Re: load vxWorks on a PC
        Subject: Re: Compact PCI Operating systems
-------------------------------------------------------
Newsgroups: comp.os.vxworks
Subject: Re: load vxWorks on a PC
Date: Thu, 13 Nov 1997 19:42:17 -0500
From: Kevin Bradley <kb+@andrew.cmu.edu>
Organization: Doctoral student, Electrical and Computer Engineering, Carnegie Mellon, Pittsburgh, PA
Message-ID: <UoOttdK00iWP0=1400@andrew.cmu.edu>
References: <346B7D18.6D43@tek.com>
Excerpts from netnews.comp.os.vxworks: 13-Nov-97 load vxWorks on a PC by
Joydeep Roy@tek.com
> I would like to know how easy or difficult it is to
> load vxWorks on a PC. What are the basic steps
I can answer this, as I've loaded it onto three PCs by now.
The documentation is pretty good; it explained enough for me
to get started, and then some help from the newsgroup rounded
out whatever I couldn't ponder myself.
The basic issues are:
    1)  Make sure you have compatible networking.  If you're
        using a serial port, no problem.  If it's a network
        card, be sure to find out the IRQ and ports used.
    2)  Configure the kernel (config.h, configAll.h).  Set
        IP address, netmask, name, how it gets its kernel
        image.
        Usable options are:   from floppy, from hard drive, from
        network via FTP.  I've done all three; I prefer the last
        for flexibilty.  Once the system loader boots, I can change
        the kernel image as much as I want 'cause it'll always
        be downloaded on each boot.
    3)  Make a bootloader program  (bootrom.sys from the
        compiler menu).
    4)  Configure the system to boot.  This can either be from
        a floppy (a program is provided to construct the boot
        floppy) or from a DOS system with a loader program
        (vxload.com).  I've tried both; the DOS system can
        be a smidge faster to boot since it loads from the
        hard drive rather than the floppy.  This is especially
        true if you're loading your kernel image from floppy...
The hardest part is getting the networking correct, but this
is usually the case with PCs.  The standard keyboard and
console work properly.  The IDE hard disk and floppy disk
controllers also work.  Can't speak for SCSI, don't have
any SCSI in my system (lucky me!).
If you have specific issues, I'd be glad to help out.
                                                -- Kevin
---------------------------
Newsgroups: comp.os.qnx,comp.os.vxworks
Subject: Re: Compact PCI Operating systems
Date: Wed, 19 Nov 1997 10:59:34 +0100
From: Peter Arkhed <Peter.Arkhed@mbox300.swipnet.se>
Organization: A customer of Tele2
Message-ID: <3472B886.1EF4E6F4@mbox300.swipnet.se>
References: <HcHtwCABMHc0EAJ+@sunny.demon.co.uk>
Hi!
I'd just like to say that I'm using a Compact PCI system from Ziatech and
having QNX 4.23A running on it with great success. We are transferring data
in the speed you mention to SCSI-disk and communicating with Windoze over
10base2.
Choose QNX, you won4t regret it.
- -Peter
Murray Elliot wrote:
> I am currently evaluating the options for the design of a new embeded
> system based around compact PCI. The requirements are as follows:
>
> 1. Reliable!
> 2. Able to communicate with Windows'95 control system via 10base2
> interface.
> 3. Able to receive data from PCI bus-master and store to disk (probably
> SCSI) at 1.6MBytes/second.
>
> I've noticed that a few PCI systems vendors advertise support for QNX,
> VxWorks and Windows '95/NT. I know enough about Windoze, but nothing
> about QNX or VxWorks. I am seeking opinions on which operating system
> would be the preferred choice for this kind of application, and where I
> should start looking for comparative reviews, benchmarks, etc.
>
> Sorry if this has already been done to death! I don't want to start a
> flame-war or create rambling threads, but I'd much appreciate any advice
> from experts out there.
>
> Thanks in advance.
>
> --
> Murray Elliot
---------------------------
End of New-News digest
**********************
From mea@mclean.sparta.com  Wed Nov 19 06:35:47 1997
From: "Mike Anderson" <mea@mclean.sparta.com>
Date: Wed Nov 19 06:35:50 PST 1997
Subject: Re: Tornado configuirations that are compatible with 5.2 tools
--MimeMultipartBoundary
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
-----Original Message-----
From: the vxWorks Users Group Exploder <vxwexplo@lbl.gov>
To: vxworks_users@csg.lbl.gov <vxworks_users@csg.lbl.gov>
Date: Tuesday, November 18, 1997 7:49 PM
Subject: Tornado configuirations that are compatible with 5.2 tools
>Submitted-by npr@jach.hawaii.edu  Tue Nov 18 16:20:36 1997
>Submitted-by: Nick Rees <npr@jach.hawaii.edu>
>
>I am running an application (EPICS) that needs many of the 5.2 features
>(startup script, login shell etc) and I am trying to work out a
>suitable VxWorks 5.3 configuration that attempts to get the best of
>both worlds. All my symbols are loaded via the startup script.
>
>So far:
>
>1. If I have INCLUDE_CONFIGURATION_5_2 and INCLUDE_WDB the symbol table
>   synching doesn't seem to work - at least the host shell doesn't seem to
>   see the target symbols, and the debugger doesn't work.
>
>2. The only way I have been able to get debugging is to INCLUDE_RDB and
>   comment out INCLUDE_WDB, and then connect with the RDB debugging mode
>   - this, of course, turns off all the features of the Tornado tools.
>
>What I would like to have is to be able to see the symbol table from
>both host and target, and be able to have both the Tornado tools and
>the debugger working with the same configuration.
>
>So, before I spend too much more time, does anyone have a neat solution
>or know what am I doing wrong? I am a bit confused that in option (1)
>above, INCLUDE_WDB is defined for the duration of configAll.h (and this
>pulls in a number of other defines), but is then turned off in
>usrConfig.c by the INCLUDE_CONFIGURATION_5_2. I am guessing that this
>may be why the symbol table synching doesn't work since the
>configuration may not be well defined.
>
All of what you wish to be done can be accomplished using the 5.3.1
release of VxWorks.  They now have a host <-> target symbol table
synchronization task that allows both the WindShell and the target
shell to coexist.  For debugging, I tend to prefer the RDB flavor
(you still invoke the crossWind debugger, but you then have to
issue a  couple of extra commands to connect to the target).  The rest
of the Tornado tools (although I'm not quite sure what else there
is that isn't available via the target shell) continue to work. If
you're interested, I'll try to scrounge up my configdb.h that shows
how it's all set up.
HTH,
---------------------------------------------------------------------
|Michael E. Anderson        | Voice -> 703 448 1683 x235            |
|Chief Engineer             | FAX   -> 703 893 5494                 |
|mea@mclean.sparta.com      | http://www.mclean.sparta.com          |
|___________________________|_______________________________________|
|             SPARTA, Inc.              |                           |
|     /\\     C4I Operation             |"Software Development is   |
|    ///\\    7926 Jones Branch Drive   | like making a baby...     |
|   /////\\   Suite 900                 | You can't make a baby in  |
|  /////  \\  McLean, VA 22102          | one month by impregnating |
| / \\\\\  \\ 703-448-0210              | nine women.               |
| \  \\\\\ //                           |                           |
|  \  //////                            | Some things just take     |
|   \//////   SPARTA                    | time."                    |
|    \////    Pride In Performance      |                           |
|     \//     --------------------      |                           |
---------------------------------------------------------------------
--MimeMultipartBoundary--
From 20358028@money.com  Wed Nov 19 06:48:54 1997
From: 20358028@money.com
Date: Wed Nov 19 06:48:57 PST 1997
Subject: HOW TO MAKE US$10,000 IN 60 DAYS
IMPOSSIBLE! you say?  BELEIVE ME IT'S TRUE!!
       Please don't make the same mistake I made!  I THREW this
letter away at least twice before I took the time to read it. When I
did, it dawned on me that this could work! Take a look for yourself! A
copy of the letter I received is below.
Steve
********************************************************************
My name is Christopher Erickson.  Two years ago, the corporation I
worked at for the past twelve years down-sized and my position was
eliminated.  After unproductive job interviews,  I decided to start my
own business.  In short order, however, I encountered many unforseen
financial problems.  I owed my family, friends, and creditors over
us$35,000.  The economy was taking a toll on my business and I just
couldn't seem to make ends meet.  I had to refinance and borrow
against my home to support my family and struggling business.  I truly
believed it was wrong for me to be in debt like this.  AT THAT MOMENT
something significant happened in my life and I am writing to share my
experience in hopes that this will change your life
FOREVER....FINANCIALLY!!!        In mid December, I received this
program via e-mail.  Six months prior to receiving this program I had
been sending away for information on various business opportunities.
All of the programs I received, in my opinion, were not cost
effective.  They were either too difficult for me to comprehend or the
initial investment was too much for me to risk to see if they worked
or not.  One claimed I'd make a million dollars in one year...it
didn't tell me I'd have to write a book to make it.        But like I
was saying, in December of '95 I received this program.  I didn't send
for it, or ask for it, they just got my name off a mailing list. THANK
GOODNESS FOR THAT!!!  After reading it several times, to make sure I
was reading it correctly, I couldn't believe my eyes.  Here was a
MONEY-MAKING PHENOMENON.  I could invest as much as I wanted to start,
without putting me further in debt.  After I got a pencil and paper
and figured it out, I saw I would at least get my money back. After
determining that the program is LEGAL and NOT A CHAIN LETTER, I asked
myself "WHY NOT?" and decided to do it.
        Initially I sent out 10,000 e-mails.  It only cost me about
us$15.00 for my time on-line.  The great thing about e-mail is that I
didn't need any money for printing to send out the program, only the
cost to fulfill my orders.  I am telling you like it is, I hope it
doesn't turn you off, but I promised myself that I would not "cheat"
anyone, no matter how much money it cost me!.
        In less than one week, I was starting to receive orders for
REPORT #1. By January 13th, I had received 26 orders for REPORT #1.
When you read the GUARANTEE in the program, you will see that "YOU
MUST RECEIVE 15 TO 20 ORDERS FOR REPORT #1 WITHIN TWO WEEKS.  IF YOU
DON'T, SEND OUT MORE PROGRAMS UNTIL YOU DO!"
        My first step in making us$200,000 in 6 months was done.
By January 30th, I had received 196 orders for REPORT #2.  If you go
back to the GUARANTEE, "YOU MUST RECEIVE 100 OR MORE ORDERS FOR REPORT
#2 WITHIN TWO WEEKS.  IF NOT, SEND OUT MORE PROGRAMS UNTIL YOU DO.
ONCE YOU HAVE 100 ORDERS, THE REST IS EASY, RELAX, YOU WILL MAKE YOUR
GOAL."  Well, I had 196 orders for REPORT #2, more than I needed.  So
I sat back and relaxed.  By March 19th, of my e-mailing of 10,000, I
received us$58,000 with more coming in every day.
        I paid off  ALL my debts and bought a much needed new car.
Please take time to read the attached program, IT WILL CHANGE YOUR
LIFE FOREVER! Remember,  it won't work  if you don't try it.  This
program does work, but you must follow it EXACTLY!  Especially the
rules of not trying to place your name in a different place.  It
doesn't work, you'll lose out on a  lot  of  money!  REPORT  #2
explains this.  Always follow the guarantee, 20 orders minimum for
REPORT #1, and 100 or more orders for REPORT #2 and you will make
us$200,000 or more in 6 months.  I AM LIVING PROOF THAT IT WORKS !!!
        If you choose not to participate in this program, I'm sorry.
It really is a great opportunity with little cost or risk to you.  If
you do choose to participate, follow the program and you will be on
your way to financial security. If you are a fellow business owner and
you are in financial trouble like I was, or you want to start your own
business, consider this a sign.  I DID!
                                        Sincerely,
                                        Christopher Erickson
PS.  Do you have any idea what 11,700 us$5 bills (us$58,000) look like
        piled up on a kitchen table? IT'S AWESOME!
"THREW IT AWAY"
        "I  had  received  this program before.  I  threw  it away,
but later wondered if I shouldn't have given it a try.  Of course, I
had no idea who to contact to get a copy, so I had to wait until I was
e-mailed another copy of the program.  Eleven months passed, then it
came.  I DIDN'T throw this one away.  I made us$41,000 on the first
try."
                                        Dawn W., Evansville, IN
"NO FREE LUNCH"
        "My late father always told me, "Remember, Alan, there is no
free lunch in life.  You get out of life what you put into it."
Through trial and error and a somewhat slow, frustrating start, I
finally figured it out. The program works very well, I just had to
find the right target group of people to e-mail it to.  So far this
year, I have made over us$63,000 using this program.  I know my dad
would have been very proud of me."
                                        Alan B., Philadelphia, PA
********************************************************************
A PERSONAL NOTE FROM THE ORIGINATOR OF THIS PROGRAM
By the time you have read the enclosed information and looked over the
enclosed program and reports, you should have concluded that such a
program,  and  one that is legal,  could not have been created by an
amateur.
Let me tell you a little about myself.  I had a profitable business
for ten years.  Then in 1979 my business began falling off.  I was
doing the same things that were previously successful for me, but it
wasn't working.  Finally, I figured it out.  It wasn't me; it was the
economy. Inflation and recession had replaced the stable economy that
had been with us since 1945.  I don't have to tell you what happened
to the unemployment rate...because many of you know from first hand
experience. There were more failures and bankruptcies than ever
before.
The middle class was vanishing.  Those who knew what they were doing
invested wisely and moved up.  Those who did not, including those who
never had anything to save or invest, were moving down into the ranks
of the poor.  As the saying goes, "THE RICH GET RICHER AND THE POOR
GET POORER."  The traditional methods of making money will never allow
you to "move up" or "get rich"; inflation will see to that. You have
just received information that can give you financial freedom for the
rest of your life, with "NO RISK" and "JUST A LITTLE BIT OF EFFORT."
You can make more money in the next few months than you have ever
imagined.
I should also point out that I will not see a penny of your money, nor
anyone else who has provided a testimonial for this program.  I have
already made over FOUR MILLION DOLLARS!  I have retired from the
program after sending out over 16,000 programs.  Now I have several
offices which market this and several other programs here in the US
and overseas.  By the Spring, we wish to market the 'Internet' by a
partnership with AMERICA ONLINE.
Follow the program EXACTLY AS INSTRUCTED.  Do not change it in any
way. It works exceedingly well as it is now.  Remember to e-mail a
copy of this exciting program to everyone that you can think of.  One
of the people you send this to may send out 50,000...and your name
will be on every one of them!.  Remember though, the more you send
out, the more potential customers you will reach.
So my friend, I have given you the ideas, information, materials and
opportunity to become financially independent, IT IS UP TO YOU NOW!
"THINK ABOUT IT"
Before you delete this program from your mailbox, as I almost did,
take a little time to read it and REALLY THINK ABOUT IT.  Get a pencil
and figure out what could happen when YOU participate.  Figure out the
worst possible response and no matter how you calculate it, you will
still make a lot of money!  Definitely you will get back what you
invested.  Any doubts you have will vanish when your first orders come
in.  IT WORKS!
                                        Paul Johnson, Raleigh, NC
HERE'S HOW THIS AMAZING PROGRAM WILL MAKE YOU $$$$$$
Let's say that you decide to start small, just to see how it goes, and
we'll assume you and all those involved send out 2,000 programs each.
Let's also assume that the mailing receives a .5% response.  Using a
good list the response would be much better.  Also many people will
send out hundreds of thousands of programs instead of 2,000.  But
continuing with this example, you send out only 2,000 programs.  With
a .5% response, that is only 10 orders for REPORT #1.
 Those 10 people respond by sending out 2,000 programs each for a
total of 20,000.  Out of those .5%, 100 people respond and order
REPORT #2.  Those 100 mail out 2,000 programs each for a total of
200,000.  The .5% response to that is 1,000 orders for REPORT #3.
Those 1,000 send out 2,000 programs each for a 2,000,000 total.  The
.5% response to that is 10,000 orders for REPORT #4.  That's 10,000
five dollar bills for you. CASH!!!!  Your total income in this example
is $50 + $500 + $5000 + $50,000 for a total of us$55,550!!!!
REMEMBER FRIEND, THIS IS ASSUMING 1,990 OUT OF 2,000 PEOPLE YOU
MAIL TO WILL DO ABSOLUTELY NOTHING... AND TRASH THIS PROGRAM!
DARE TO THINK FOR A MOMENT WHAT WOULD HAPPEN IF EVERYONE
OR HALF SENT OUT 100,000 PROGRAMS INSTEAD OF ONLY 2,000.  Believe me,
many people will do that and more!  By the way, your cost to
participate in this is practically nothing.  You obviously already
have an Internet connection and e-mail is FREE!!!  REPORT#3 will show
you the best methods for bulk e-mailing and purchasing e-mail lists.
THIS IS A LEGITIMATE, LEGAL, MONEY MAKING OPPORTUNITY.  It does not
require you to come in contact with people, do any hard work, and best
of all, you never have to leave the house except to get the mail.  If
you believe that someday you'll get that big break that you've been
waiting for, THIS IS IT!  Simply follow the instructions, and your
dream will come true.  This multi-level e-mail order marketing program
works perfectly...100% EVERY TIME.  E-mail is the sales tool of the
future.  Take advantage of this non-commercialized method of
advertising NOW!!  The longer you wait, the more people will be doing
business using e-mail.  Get your piece of this action!!
MULTI-LEVEL MARKETING (MLM) has finally gained respectability.  It is
being taught in the Harvard Business School, and both Stanford
Research and The Wall Street Journal have stated that between 50% and
65% of all goods and services will be sold throughout Multi-level
Methods by the mid to late 1990's.  This is a Multi-Billion Dollar
industry and of the 500,000 millionaires in the US, 20% (100,000) made
their fortune in the last several years in MLM.  Moreover, statistics
show 45 people become millionaires EVERY DAY through Multi-Level
Marketing.
This is not a chain letter, but a perfectly legal money making
opportunity.  Basically, this is what we do:  As with all
multi-level business, we build our business by recruiting new
partners and selling our products.  Every state in the USA allows you
to recruit new multi-level business partners, and we offer a product
for EVERY dollar sent. YOUR ORDERS COME AND ARE FILLED THROUGH THE
MAIL, so you are not involved in personal selling.  You do it
privately in your own home, store or office.
This is the GREATEST Multi-level Mail Order Marketing anywhere:
Here is how to work the program:
Step (1)    Order all four 4 REPORTS listed by NAME AND NUMBER.
           Do this by ordering the REPORT from each of the four (4)
           names listed on the next page.  For each REPORT, send us$5
           CASH, your EMail address if any, and a SELF-ADDRESSED,
           STAMPED envelope  (BUSINESS SIZE #10) to the person listed
           for the SPECIFIC REPORT.
           International orders should also include us$1 extra instead
           of postage.  It is essential that you specify the NAME and
           NUMBER of the report requested to the person you are
           ordering from.  You will need ALL FOUR (4) REPORTS because
           you will be REPRINTING and RE-SELLING them. DO NOT alter
           the names or sequence beyond doing what the instructions say.
 NOTE: Write your request on an 8 1/2 x 11 piece of paper
           and wrap the cash in that BEFORE you put it in the
           envelope. This helps to ensure the mail gets through!
Step (2)   Replace  the  name  and  address  under  REPORT #1  with
           yours,  moving the one that was there down to REPORT #2.
           Drop  the  name and address under REPORT #2 to REPORT #3,
           moving the one that was there to REPORT #4.  The name and
           address that was under REPORT #4 is dropped from the list
           and this party  is  no doubt on the way to the bank.
           When doing   this,   make   certain   you  type  the  names
           and addresses ACCURATELY!  DO NOT MIX UP MOVING
           PRODUCT/REPORT POSITIONS!!!
Step (3)   Having made the required changes in the NAME list, save it
           as a text (.txt) file in it's own directory to be used
           with whatever e-mail program you like.  Again, REPORT #3
           will tell you the best methods of bulk e-mailing and
           acquiring e-mail lists.
Step (4)   E-mail a copy of the entire program (all of this is very
           important) to everyone whose address you can get your
           hands on. Start with friends and relatives since you can
           encourage them to take  advantage of this fabulous money-making
           opportunity.  That's what I did.  And they love me now,
           more than ever.  Then, e-mail to anyone and everyone!  Use
           your  imagination!  You can get e-mail addresses from
           companies on  the Internet who specialize in e-mail mailing lists.
           These are very cheap: 100,000 addresses for around us$35.00.
IMPORTANT:  You won't get a good response if you use an old list, so
always request a FRESH, NEW list. You will find out where to purchase
these lists when you order the four (4) REPORTS.
ALWAYS PROVIDE SAME-DAY SERVICE ON ALL ORDERS!!!
REQUIRED REPORTS
***Order each REPORT by NUMBER and NAME***
ALWAYS SEND A SELF-ADDRESSED, STAMPED ENVELOPE AND us$5 CASH FOR
EACH ORDER REQUESTING THE SPECIFIC REPORT BY NAME AND NUMBER
________________________________________________________
REPORT #1       "HOW TO MAKE us$250,000 THROUGH MULTI-LEVEL SALES"
ORDER REPORT #1 FROM:
Sandra Plumbo
33-19 145PL FLUSHING
New York, N.Y. 11354
U.S.A.
________________________________________________________
REPORT #2       "MAJOR CORPORATIONS AND MULTI-LEVEL SALES"
ORDER REPORT #2 FROM:
Andrew Crossman
Suite 1124, 607 Gerrard St. East
Toronto, Ontario M4M 1Y2
Canada
________________________________________________________
REPORT #3       "SOURCES FOR THE BEST MAILING LISTS"
ORDER REPORT #3 FROM:
S.Y.Williams
Suite 314, 19-2555 Victoria Park Ave
Scarborough, Ontario M1T 1A3
Canada
___________________________________________________
REPORT #4       "EVALUATING MULTI-LEVEL SALES PLANS"
ORDER REPORT #4 FROM:
Cindy Porneycal
P.O.BOX 76510
1661 Denison St.
Markham, Ontario L3R 0N5
Canada
________________________________________________________
CONCLUSION
        I am enjoying my fortune that I made by sending out this
                                     program. You, too, will be making money
within six months, if you
follow the SIMPLE STEPS outlined in this mailing.
To be financially independent is to be FREE.  Free to make
financial decisions as never before.  Go into business, get into
investments, retire or take a vacation.  No longer will a lack of
money hold you back.
        However, very few people reach financial independence
because, when opportunity knocks, they choose to ignore it.  It is
much easier  to say "NO" than "YES," and this is the question that you
must answer for yourself.   Will YOU ignore this amazing opportunity
or will you take advantage of it? If you do nothing, you have indeed
missed something valuable, and nothing will change.  Please re-read
this material; this is a special opportunity. If you have any
questions, please feel free to write to the sender of this
information.  You will get a prompt and informative reply.        My
method is simple.  I sell thousands of people a product for us$5 that
costs me pennies to produce and e-mail.  I should also point out
again, that this program is legal and everyone who participates WILL
make money. This is not a chain letter or pyramid scheme.  At times
you have probably received chain letters, asking you to send money, on
faith, but getting NOTHING in return, NO product what-so-ever!  Not
only are chain letters illegal, but the risk of someone breaking the
chain makes them quite unattractive.        You are offering a
legitimate product to your people.  After they purchase the product
from you, they reproduce more and resell them. It's simple free
enterprise.  As you learned from the enclosed material, the PRODUCT is
a series of four (4) FINANCIAL AND BUSINESS REPORTS.  The information
contained in these REPORTS will not only help you in making your
participation in this program more rewarding, but will be useful to
you in any other business decisions you make in the years ahead. You
are also buying the rights to reprint all of the REPORTS, which will
be ordered from you by those to whom you mail this program.  The
concise one and two page REPORTS you will be buying can easily be
reproduced at a local copy center for a cost of about 3 cents a copy.
Best wishes with the program and Good Luck!
"IT WAS TRULY AMAZING"
"Not being the gambling type, it took me several weeks to make up my
mind to participate in this program.  But conservative as I am, I
decided that the initial investment was so little that there was no
way that I could not get enough orders to at least get my money back.
BOY, was I ever surprised when I found my medium sized post office box
crammed with orders!  I will make more money this year than any ten
years of my life before."
                                        Mary Riceland, Lansing, MI
TIPS FOR SUCCESS
Send for your four (4) REPORTS immediately so you will have them when
the orders start coming in.  When you receive a us$5 order, you MUST
send out the product/service to comply with U.S. Postal and Lottery
laws.  Title 18 Sections 1302 and 1341 specifically state that:  "A
PRODUCT OR SERVICE MUST BE EXCHANGED FOR MONEY RECEIVED."
WHILE YOU WAIT FOR THE REPORTS TO ARRIVE:
1.      Name your new company. You can use your own name if you
         desire.
2.      Get a post office box (preferred).
3.      Edit the names and addresses on the program. You must
         remember,  your name and address go next to REPORT #1 and the
         others  all move down one, with the fourth one being bumped OFF the
         list.
4.      Obtain as many e-mail addresses as possible to send until
         you receive the information on mailing list companies in REPORT
         #3.
5.      Decide on the number of programs you intend to send out.
         The more you send, and the quicker you send them, the more money
         you will make.
6.      After mailing the programs, get ready to fill the orders.
7.      Copy the FOUR (4) REPORTS so you are able to send them out
         as soon as you receive an order. IMPORTANT: ALWAYS PROVIDE
         SAME-DAY SERVICE ON ORDERS YOU RECEIVE!
8.      Make certain the letter and reports are neat and legible.
*******************************************************************
YOUR GUARANTEE
The check point which GUARANTEES your success is simply this:  you
must receive 20 orders for REPORT #1.  This is a must!!!  If you don't
within two weeks, e-mail out more programs until you do.  Then a
couple of weeks later you should receive at least 100 orders for
REPORT #2, if you don't, send out more programs until you do.  Once
you have received 100 or more orders for REPORT #2, (take a deep
breath) you can sit back and  relax,  because  YOU  ARE  GOING TO MAKE
 AT LEAST us$50,000. Mathematically  it  is  a  proven guarantee.   Of
 those  who  have participated in the program and reached the above
GUARANTEES, ALL have reached their goal.  Also, remember, every time
your name is moved down the list, you are in front of a different
REPORT, so you can keep track of your program by knowing what people
are ordering from you. IT'S THAT EASY; REALLY, IT IS!!!
REMEMBER:
"HE WHO DARES NOTHING, NEED NOT HOPE FOR ANYTHING."
"INVEST A LITTLE TIME, ENERGY AND MONEY NOW OR SEARCH FOR IT
        .................FOR THE REST OF YOUR LIFE."
From enrico.ferro@elsag.it  Wed Nov 19 06:52:57 1997
From: Enrico Ferro <enrico.ferro@elsag.it>
Date: Wed Nov 19 06:53:00 PST 1997
Subject: intLock() vs. taskLock()
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Hi guys,
we have an application that requires a time-critic operation to be done
without interruptions. This operation may be quite frequent also, so we
don't want to put much overhead to control it.
VxWorks provides intLock() to disable interrupts and taskLock() to disable
task context switching.
The question is, how long does it take to execute taskLock() and
taskUnlock() every time I have to make my uninterruptable operation? Or,
better still, how many instructions are executed by the two calls? Is it
wise to lock/unlock the context switching?
Thanks in advance to anyone who might reply my questions.
Enrico Ferro
Elsag Bailey Hartmann & Braun S.p.A.
Via Hermada 6, 16154 Genova - Italy
Tel. 0039-10-6586222 --- Fax. 0039-10-6586210
Home 0039-10-6517797
Work E-mail Enrico.Ferro@elsag.it
Backup work e-mail address Enrico.Ferro@usa.net
Home e-mail clusede@clu.assicomitalia.it
--MimeMultipartBoundary--
From blohm@vs.dasa.de  Wed Nov 19 07:07:37 1997
From: "Gundula Blohm" <blohm@vs.dasa.de>
Date: Wed Nov 19 07:07:40 PST 1997
Subject: Re: Problem booting mv3604
On 18 Nov 97 at 12:03, the vxWorks Users Group Explo wrote:
> Submitted-by biberdot@wpg.lmcda.lmco.com  Tue Nov 18 12:03:51 1997
> Submitted-by: "Biberdorf, Terry @ WIN" <biberdot@wpg.lmcda.lmco.com>
>
>
> I have installed tor101_mv2600_collection3.tar patch for the mv2600 BSP.
> :
> then when I power down the PowerPC and move jumper J2 to pins 1-2
> and power the card back up, I get what starts to look like vxWorks
> booting
> and then a fail message
> "network interface lse unknown"
> "can't load boot file!! "
>
> I was expecting the device network to be dc not lse.  As from the
> config.h file.
Hi Terry,
after doing the steps you described, i found the vxworks config being
corrupt, so i had to do that once more (ie set the interface, ip
addresses...). Don t know, why that s neccessary, but after that, all worked
fine.
HTH, Dula
===================================================
Gundula Blohm
Tel. +49 (731) 392-4731
Fax  +49 (731) 392-4958
mailto:blohm@vs.dasa.de
===================================================
From dale@shoretel.com  Wed Nov 19 10:03:14 1997
From: Dale Luck <dale@shoretel.com>
Date: Wed Nov 19 10:03:19 PST 1997
Subject: RE: intLock() vs. taskLock()
--MimeMultipartBoundary
Content-Type: text/plain
intLock and intUnlock are really quick on the mips implementation. You
don't need to
do taskLock if you do intLock.
Dale
--MimeMultipartBoundary--
From dale@shoretel.com  Wed Nov 19 11:05:46 1997
From: Dale Luck <dale@shoretel.com>
Date: Wed Nov 19 11:05:50 PST 1997
Subject: RE: intLock() vs. taskLock()
--MimeMultipartBoundary
Content-Type: text/plain
> intLock and intUnlock are really quick on the mips implementation. You
> don't need to
> do taskLock if you do intLock.
>
And the reason intUnlock is quick is because it is a very dangerous and
improperly coded routine.
It wipes out the entire contents of the register instead of just hitting
the
master interrupt enable bit.
Dale
--MimeMultipartBoundary--
From stan@rti.com  Wed Nov 19 11:17:28 1997
From: stan@rti.com (Stan Schneider)
Date: Wed Nov 19 11:17:31 PST 1997
Subject: Re: intLock() vs. taskLock()
>> Submitted-by enrico.ferro@elsag.it  Wed Nov 19 06:52:57 1997
>> Submitted-by: Enrico Ferro <enrico.ferro@elsag.it>
>>
>> The question is, how long does it take to execute taskLock() and
>> taskUnlock() every time I have to make my uninterruptable operation? Or,
>> better still, how many instructions are executed by the two calls? Is it
>> wise to lock/unlock the context switching?
Both intLock & taskLock are very fast & take about the same amount of time.  The only significant hit is that taskUnlock and intUnlock both do a reschedule; that takes a few usecs.  Choose the one to use based on your needs.  It's usually better not to lock interrupts unless you have to.
We have in the past lamented the lack of an "intUnlockButDontRescheduleBecauseIKnowIHaventCalledAnySystemRoutines()" function.  That would make intUnlock very, very fast. Maybe it doesn't fit in the target-based symbol table.  ;-)
        -- Stan
=============================================================================
=                                           =                               =
=   Stan Schneider                          =   email: stan@rti.com         =
=   Real-Time Innovations, Inc.             =   Phone: (408) 720-8312 x104  =
=   155A Moffett Park Drive, Suite 111      =   Fax:   (408) 734-5009       =
=   Sunnyvale, CA 94089                     =   http://www.rti.com          =
=                                           =                               =
=============================================================================
From dale@shoretel.com  Wed Nov 19 12:26:03 1997
From: Dale Luck <dale@shoretel.com>
Date: Wed Nov 19 12:26:10 PST 1997
Subject: RE: intLock() vs. taskLock()
--MimeMultipartBoundary
Content-Type: text/plain
Hmmm, the intUnlock for the mips chip does not call reschedule. it just
blasts the control reg 0
and returns.
>
> Both intLock & taskLock are very fast & take about the same amount of
time.  The only significant hit is that taskUnlock and intUnlock both do
a reschedule; that takes a few usecs.  Choose the one to use based on
your needs.  It's usually better not to lock interrupts unless you have
to.
>
> We have in the past lamented the lack of an
"intUnlockButDontRescheduleBecauseIKnowIHaventCalledAnySystemRoutines()"
function.  That would make intUnlock very, very fast. Maybe it doesn't
fit in the target-based symbol table.  ;-)
>
Dale
--MimeMultipartBoundary--
From cgrames@mdc.com  Wed Nov 19 13:24:46 1997
From: Charlie Grames <cgrames@mdc.com>
Date: Wed Nov 19 13:24:50 PST 1997
Subject: Re: Problem booting mv3604 -Reply
--MimeMultipartBoundary
Content-Type: text/plain
Content-Disposition: inline
The VxWorks boot parameters are stored in non-volatile RAM.  Open Firmware uses this
non-volatile RAM for its own purposes and thus trashes the VxWorks boot line in the process.
That is why you have to reconfigure when going back to VxWorks.
It is also important to note that DEFAULT_BOOT_LINE, defined in config.h, is only used if the boot
line cannot be read from NVRAM or is null.  It will NOT be used if anything, even junk, is stored in
the boot line in NVRAM.  See target/all/bootConfig.c for details.
You may be interested in knowing that Motorola no longer supports Open Firmware.  They now
offer only their own PPCBug (similar to the ROM monitors offered on older Motorola computer
products).  You might want to talk to your Motorola sales and/or tech reps to determine how this
might affect you.
Charlie Grames
The Boeing Company
(314) 233-1956
Charles.R.Grames@boeing.com
>>> the vxWorks Users Group Exploder <vxwexplo@lbl.gov> 11/19/97 09:07am >>>
Submitted-by blohm@vs.dasa.de  Wed Nov 19 07:07:37 1997
Submitted-by: "Gundula Blohm" <blohm@vs.dasa.de>
On 18 Nov 97 at 12:03, the vxWorks Users Group Explo wrote:
> Submitted-by biberdot@wpg.lmcda.lmco.com  Tue Nov 18 12:03:51 1997
> Submitted-by: "Biberdorf, Terry @ WIN" <biberdot@wpg.lmcda.lmco.com>
>
>
> I have installed tor101_mv2600_collection3.tar patch for the mv2600 BSP.
> :
> then when I power down the PowerPC and move jumper J2 to pins 1-2
> and power the card back up, I get what starts to look like vxWorks
> booting
> and then a fail message
> "network interface lse unknown"
> "can't load boot file!! "
>
> I was expecting the device network to be dc not lse.  As from the
> config.h file.
Hi Terry,
after doing the steps you described, i found the vxworks config being
corrupt, so i had to do that once more (ie set the interface, ip
addresses...). Don t know, why that s neccessary, but after that, all worked
fine.
HTH, Dula
--MimeMultipartBoundary--
From egbert@ra.timeplex.com  Wed Nov 19 14:55:47 1997
From: egbert@ra.timeplex.com (Stephen L. Egbert)
Date: Wed Nov 19 14:55:50 PST 1997
Subject: Re: intLock() vs. taskLock()
--MimeMultipartBoundary
Content-type: TEXT/PLAIN
> we have an application that requires a time-critic operation to be done
> without interruptions. This operation may be quite frequent also, so we
> don't want to put much overhead to control it.
>
> VxWorks provides intLock() to disable interrupts and taskLock() to disable
> task context switching.
>
> The question is, how long does it take to execute taskLock() and
> taskUnlock() every time I have to make my uninterruptable operation? Or,
> better still, how many instructions are executed by the two calls? Is it
> wise to lock/unlock the context switching?
The only time to call both intLock() and taskLock() is if you performed logMsg() inside the critical section at task-context.
logMsg() calls windExit() which in turns breaks the intLock().
Steve
Stephen (Steve) L. Egbert              Work: (214) 340-3300
ascom Timeplex                          Fax: (214) 341-3654
Dallas, Texas 75243-7095                Net: egbert_nospam @ ra.timeplex.com
        Linux O/S: Vilius, fortius, centius quam Microsoft
--MimeMultipartBoundary--
From R.Kirnum@dialogic.com  Wed Nov 19 15:01:30 1997
From: "Kirnum, Robert" <R.Kirnum@dialogic.com>
Date: Wed Nov 19 15:01:33 PST 1997
Subject: ARM Devel Boards
--MimeMultipartBoundary
Content-Type: text/plain
Anyone out there using a development board for ARM?  If so could you
post / email your comments?
Thanks,
Bob
________________________________________________________________________
D I A L	Bob Kirnum
_|_|_|O	Project Engineer
_|_|_|G	973-993-3000 Ext. 6589
_|_|_|I	973-993-5916 Fax
_|_|_|C	mailto:R.Kirnum@dialogic.com
Get the Dialogic Edge at http://www.dialogic.com
Dialogic Corp.  /  1515 Rt. 10  /  Parsippany, NJ 07054
________________________________________________________________________
           Did you know . . . that FireWire was developed by Apple?
       . . . that Apple is 150 in the Fortune 500 and Microsoft is 172?
Believe in Macintosh? Check out http://www.evangelist.macaddict.com/
--MimeMultipartBoundary--
From npr@jach.hawaii.edu  Wed Nov 19 16:05:27 1997
From: Nick Rees <npr@jach.hawaii.edu>
Date: Wed Nov 19 16:05:30 PST 1997
Subject: Re: Tornado configuirations that are compatible with 5.2 tools
I had some help about this from two people at Wind River. Thanks.
However, it turned out my ultimate problem was that it appears that to
synchronize symbol tables the _target_ needs a route to the license
server. For security reasons our live targets don't have routes to
machines outside the local net and the license server is on our
development net, not the live net.
I find this bad and strange - no other Tornado tools I have used need
this. My suggestion would be to remove this restriction - the licenses
are for developers, not targets.
Nick Rees
Joint Astronomy Centre                    Ph:       +1 (808) 961-3756
660 N. Aohoku Place                       Fax:      +1 (808) 961-6516
Hilo, HI.  96720                          Internet: npr@jach.hawaii.edu
From daemon@csg.lbl.gov  Thu Nov 20 04:00:21 1997
From: daemon@csg.lbl.gov
Date: Thu Nov 20 04:00:39 PST 1997
Subject: comp.os.vxworks newsdigest
Comp.Os.Vxworks Daily Digest    Thu Nov 20 04:00:17 PST 1997
        Subject: vxWorks Pricing!!!!!
-------------------------------------------------------
Newsgroups: comp.os.vxworks
Subject: vxWorks Pricing!!!!!
Date: Wed, 19 Nov 1997 14:03:17 GMT
From: blair@xvn.ds.boeing.com (Rick Blair)
Organization: The Boeing Company
Message-ID: <EJwCDH.K6I@news.boeing.com>
Sender: nntp@news.boeing.com (Boeing NNTP News Access)
Hi all,
	I'm surprised that no one else has started a tread about the
cost of vxWorks/tornado.  I have been a vxWorks developer for almost 8
years now.  I am, howver, starting to look for less expensive alternatives.
Don't get me wrong,  I love vxWorks! I even Like tornado!  I just cannot
justify the cost anymore!!  Especially things like 11K$ for Java!!!
and thats on top of the 19K or so for tornado!!  I am also a low volume
kind of developer.  None of my projects will ever amount to more than
5 or 10 items installed, so a price of $1000 for a runtime license puts
off many of my potential users.  Plus a different development license for
PPC and 68K?  Now I'm at 40K?  Thats a real hard sell to my management
when they see a full up visual c++ for about 1/10 of that!
I'm starting this thread not to gripe (ok, maybe a little), but I see
a real threat to vxworks coming from windows CE2!  I do not want to use
a microsoft product, but may be forced to based on price!  The
price of the hardware, price of the os, price of the runtime license, and
price of developement environment!!!  I'm sure I will hear, "You get
what you pay for", but if windows CE will do the job at 1/10 the cost, then
I will be forced to use it.  Remember how the PC killed the Mac in sales?
Where is apple now?  It is a better platform, just way too expensive!
Make vxWorks a comodity!  Lower the prices, fix the licensing,  make it where
I can afford to use it!!  Please Help ME!!
Thanks for listening
Rick
- --
**************************************************************************
* email:   blair@xvn.ds.boeing.com  * The contents of this message in    *
* voice:   (206)773-8962            * in no way reflect  the opinions    *
* usSnail: P.O. Box 3707 M/S 3E-28  * of the Boeing Company. Opinions    *
*          Seattle, Wa 98124        * expressed here are strictly my own *
*    -------------  SUPPORT YOUR LOCAL POP3 SERVER --------------        *
**************************************************************************
---------------------------
End of New-News digest
**********************
From elesh.mistry@gecm.com  Thu Nov 20 06:49:21 1997
From: Elesh Mistry <elesh.mistry@gecm.com>
Date: Thu Nov 20 06:49:32 PST 1997
Subject: Register for the exploder
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Dear WindRiver Systems,
	I on behalf of my company would like to register for the WRS
	exploder mailing list to share insights, rpoblems and solutions
	with other users of your product.
	Name 				: Elesh C. Mistry
	Company Name 			: GEC Marconics - Avionics
	Address 			: The Grove
					  Warren Lane
					  Stanmore
					  Middlesex
					  HA7 4LY
	Telephone Number 		: 0181-954-2311 x. 7910
	Fax Number 			: 0181-420-3844
	E-Mail Address 			: Elesh.Mistry@gecm.com
	Description of Application 	: Defence Application
	Hardware Type 			: DY4
--MimeMultipartBoundary--
From dleviner@HiWAAY.net  Thu Nov 20 06:56:55 1997
From: David Leviner <dleviner@HiWAAY.net>
Date: Thu Nov 20 06:56:59 PST 1997
Subject: DEC SA-1100 StrongARM & IEEE 1394 Firewire support
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
VxWorks Gurus,
Does anyone know if VxWorks supports the Digital Semicomductor
SA-110 or SA-1100 StrongARM microprocessor, or any of the ARM
microprocessors? If so to what degree? Is there a BSP available or
in the works?
Also, is there an interface for the IEEE 1394 firewire serial bus supported
under VxWorks?
Any bit of information concerning these two subjects would help.
Thanks,
David Leviner
Real-Time Systems Software Engineer
Chandler/May, Inc.
dleviner@hiwaay.net
205-722-0175
--MimeMultipartBoundary--
From lars.antback@pullmax.se  Thu Nov 20 08:49:40 1997
From: lars.antback@pullmax.se
Date: Thu Nov 20 08:49:43 PST 1997
Subject: RE: Tornado on Windows NT
Hi !
We are using the Windows NT as platform for Tornado and have had some
problems although it works fine most of the time. To answer your
questions,
Q1
We are not using any Source Control system
Q2
It is not allways a stable development environment and we have had some
problems with the connection between host and target. Also the time for
communicating with the target can be considerably long, especially when
using the debugger. My biggest complains are the lack of a usable editor
and some tools for project management. I our case we are using about 400
different files and it can not be handled efficiently from the Tornado
environment. We are instead using a standard Windows development tool for
editing code, Borland C++, and a makefile structure to build the
application .
Q3
We have installed the Tornado tree on each machine and are copying the
"\tornado\target" tree each time a change in the kernel is made. This
adds some amount of administration but it works. Another experience is
that we are using a Novell Netware network and whats called roaming
profiles for Windows NT, it's a nice thing to allways have the same
desktop not depending on the current machine. This configuration does not
work completly with Tornado, I have not figured out why but some parts of
the local configuration stays with the user, not the machine. The only
thing is that when starting the target server we have to add parameters
each time.
It must be said that except for these things the system works. When the
application is started the OS runs just as expected and we have not had
any serious problem with it.
Best Regards /Lars Antbaeck, Pullmax, Sweden
From mea@mclean.sparta.com  Thu Nov 20 08:58:50 1997
From: "Mike Anderson" <mea@mclean.sparta.com>
Date: Thu Nov 20 08:58:54 PST 1997
Subject: Re: comp.os.vxworks newsdigest
--MimeMultipartBoundary
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
>Hi all,
>
> I'm surprised that no one else has started a tread about the
>cost of vxWorks/tornado.  I have been a vxWorks developer for almost 8
>years now.  I am, howver, starting to look for less expensive alternatives.
>Don't get me wrong,  I love vxWorks! I even Like tornado!  I just cannot
>justify the cost anymore!!  Especially things like 11K$ for Java!!!
>and thats on top of the 19K or so for tornado!!  I am also a low volume
>kind of developer.  None of my projects will ever amount to more than
>5 or 10 items installed, so a price of $1000 for a runtime license puts
>off many of my potential users.  Plus a different development license for
>PPC and 68K?  Now I'm at 40K?  Thats a real hard sell to my management
>when they see a full up visual c++ for about 1/10 of that!
>
[snip]
Greetings!
  When I first started w/ VxWorks 10 Years ago, the O/S was $19K
and the "network-capable" target licenses where $600 each.  There
was no compiler and the source debugger was a hack of Sun's
dbxTool that cost $4K.  So, many of us did development without
source debuggers ;-).
  Then, WRS decided that because of the demise of the Sun native
68K compiler and the associated SPARC x 68k compiler (and the
dbxTool for that matter) that they would bundle in a compiler/
debugger into the O/S.  This was the public domain GNU compiler.
But the price of VxWorks jumped by a strangely coincidental $4k
to $23k and the targets jumped to $1k.  This caused a lot of
defections to PSOS and other O/Ses, but not enough to effect pricing
policies by much.  WRS's primary market target had always been the
large manufactuers and Aerospace companies, not the "mom-and-pop"
ISV/developer.
  However, the licensing model of VxWorks was a large, centralized
server with up to 10 users on a single license.  There were no
license managers or host locking, which meant that the S/W could
be replicated on as many servers as the user wanted.  A flagrant
violation of license agreements, but there was little that WRS could
do to enforce the policy.  Also, you were supposed to purchase a
new copy of VxWorks for each subsequent project at additional $$$.
Now, since most of their customers were large corporations, there
was no way those folks would risk a law suit over a licensing
violation.  Therefore, everyone paid up.
  Enter Tornado.  I feel that WRS believed that if they could
introduce host-locking, they could eliminate any software
piracy that was going on (although I doubt that there was much
happening in the first place).  They would "lower" the price
of Tornado to $16K, but that would then be a single seat rather
that a 10 seat license as before.  At $2.7K for each additional
seat, an equivalent 10 seat Tornado license was now $40K!  I had
persnally argued for a much lower price of say $8K for the first
seat and then $3K for each additional seat.  That still resulted
in more revenue for WRS ($35K vs. $23K for 10 users), but had the
effect of making the price of entry much lower for the small
projects and 1-2 man development teams.
  My logic was, "Well, if I can get the Cadillac of RTOSes for a
couple of $K more than the Nucleuses and C-Execs of the world,
then it's money well spent".  I reasoned that this would have
the net effect of giving WRS significant penetration into the
low-end of the market thereby eliminating some of the competition
there.  There would be more Tornado seats out there as the projects
grew in size and scope and the revenue from target licenses would
also increase (especially if you cut the target license price
down to $500 per target).  This would also limit the defections
of projects to other RTOSes/Win CE/NT by eliminating the huge
financial bite that Tornado takes out of a project.  A bit
predatory I must admit, but it seemed like a good strategy.
Unfortunately, this suggestion fell on deaf ears at WRS.
  Now, if you look at WRS's financials, you'll see that WRS is
raking in the money anyway.  Their primary market is still the
large corporation (let's face it, manufacturers are where the
money's at anyway).  As the prices continue to increase and
we get nickle-and-dimed to death with the add-ons ($11K for
the Java VM!?!?), there will be some defections to the cheapy
x86 kernels.  But, as long as WRS's revenues continue to
increase, there is absolutely no incentive for them to change
their pricing/licensing policies.  I too love VxWorks (in spite
of my rantings about Tornado) and if money is no object, I'll
pick VxWorks every time.  However, some of the x86 kernels aren't
too bad (for the right kind of application).  If I were WRS,
I wouldn't get too complacent about their leadership role in the
RTOS marketplace.  There are lots of good kernels sneaking up
behind.
Regards,
---------------------------------------------------------------------
|Michael E. Anderson        | Voice -> 703 448 1683 x235            |
|Chief Engineer             | FAX   -> 703 893 5494                 |
|mea@mclean.sparta.com      | http://www.mclean.sparta.com          |
|___________________________|_______________________________________|
|             SPARTA, Inc.              |                           |
|     /\\     C4I Operation             |"Software Development is   |
|    ///\\    7926 Jones Branch Drive   | like making a baby...     |
|   /////\\   Suite 900                 | You can't make a baby in  |
|  /////  \\  McLean, VA 22102          | one month by impregnating |
| / \\\\\  \\ 703-448-0210              | nine women.               |
| \  \\\\\ //                           |                           |
|  \  //////                            | Some things just take     |
|   \//////   SPARTA                    | time."                    |
|    \////    Pride In Performance      |                           |
|     \//     --------------------      |                           |
---------------------------------------------------------------------
--MimeMultipartBoundary--
From eugenel@flash.condorsys.com  Thu Nov 20 09:03:51 1997
From: eugenel@flash.condorsys.com (Eugene Leung x714)
Date: Thu Nov 20 09:03:57 PST 1997
Subject: dram offset for mv2603 bsp
Hi all,
Can someone tell me what I need to do to offset the dram from 0 for the
moto mv2603 board?  I want to offset the dram from 0 to 0x02000000, this
way 0 is an illegal address.  I've made changes in romInit.s to change
the base address for the falcon chip and changed the definitions for
local ram in config.h as well as sysLib.c. What else do I need to do?
The board just won't boot at all now.
Please reply directly to eugenel@condorsys.com. TIA.
Eugene
From leif.thuresson@tsl.uu.se  Thu Nov 20 09:23:32 1997
From: Leif Thuresson <leif.thuresson@tsl.uu.se>
Date: Thu Nov 20 09:23:35 PST 1997
Subject: Soft reboot hangs IPIC on MVME162-512A
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Rebooting my MVME162-512A with <cntrl-X> seam to hang the IndustryPack
Interface Controller (IPIC). I get a bus error when I try to read the
ID-ROM on the
IP's after a <cntrl-X> reboot. After a hardware reset the IPIC works
okay.  I have
several  MVME162-022A and I have never had this problem with these
boards.
-Leif
-----------------------------------------------------------
Leif Thuresson               Tel:    +46-18-4713860
Uppsala University           Fax:    +46-18-4713833
The Svedberg Laboratory      E-mail: leif.thuresson@tsl.uu.se
P.O.Box 533
S-751 21 Uppsala
Sweden
--MimeMultipartBoundary--
From tpe@dmc22.com  Thu Nov 20 09:39:35 1997
From: tpe@dmc22.com
Date: Thu Nov 20 09:39:42 PST 1997
Subject: Software/Electrical Engineer Needed
I queried the Boolean expression "laser AND medical" in the DMC Million Plus resume
database and several Internet search engines.  One of the retrieved resumes, postings or
pages advertised your email address indicating that you would welcome email inquiries on
related subjects.  Hence I am writing to ask for your assistance.
I am looking to hire a Software/Electrical Engineer to conduct research and develop medical
lasers used mainly for dermatological therapy, varicose vein removal, tattoo removal, and
skin lesions to work at our Massachusetts facility.
Qualified candidate must be able to program real time commands using C on Intel 8051
series microprocessors, develop hardware and software interfaces and develop algorithms for
high voltage energy.
If you know someone that would be interested I can be contacted at:
Thom Erickson
Voice: 609-584-9000 ext. 259
Fax: 609-584-9575
OUR ANTI-SPAM POLICY
We DO NOT send unsolicited email. We DO NOT send email to lists purchased from any
list marketing vendor or producer.
We do send email to individuals that included their email address on their resume or
advertised their email address, thusly soliciting inquiries, on postings or web sites which
discuss job or resumes or professional or industrial matters related to the job opportunity we
are trying to fill.
Sometimes, people forget they submitted their email address to Diedre Moire, included it on
their resume or solicited response on postings or pages. In rare situations, individuals' email
addresses are advertised without their knowledge or consent.  In any case, we gladly react to
any request that we cease future mailings by placing a filter on our mailing software and
removing your resume from the Diedre Moire Million Plus resume database.  If you do not
want to hear from us type "remove" in the subject field and send via the reply command or
address to rem@dmc22.com. We will cease mailings and remove your resume for the Diedre
Moire Million Plus resume database. Please note that over seventy-five Fortune 500
Corporations and many more small and medium companies tap that database when hiring.
Removal of your resume may, in many instances, eliminate your access to jobs at those
companies.
GENERAL DRAW SOLICITATION
We DO NOT support general draw solicitation.  General draw is a technique used to "troll"
for potential prospects by sending mass quantities of announcements to groups of people in
the hopes that some might respond with a general interest.
We only announce specific job openings that must be filled immediately and endeavor to
contact only those individuals who indicated interest in the related area and made their email
addresses available via public posting or resume submission.
FORWARDING
Sometimes, people we did not send to receive our mail. This occurs when the originally
targeted recipient forwards the email we send to a friend or acquaintance. Such forwarding is
not under our control.
WHO DO WE WORK FOR
You may notice the response name and address listed above does not belong to Diedre Moire
Corporation, Inc. but some other company, firm or organization. In such cases, Diedre Moire
selected your address and mailed to you, but our client requested that referrals, inquiries and
candidate applications be made via direct contact to their offices.
From ajohnston@rainbow.robins.af.mil  Thu Nov 20 09:48:50 1997
From: "Albert S. Johnston" <ajohnston@rainbow.robins.af.mil>
Date: Thu Nov 20 09:48:54 PST 1997
Subject: Tornado porting FAQ ?
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi....
I am in the process of porting from 5.11 to 5.2.  I understand going to 5.3 will
be much worse....
Has anyone put together a FAQ that addresses the issues one encounters when
moving from
vxWorks to "tornado"?
thanks...
    -al
--MimeMultipartBoundary--
From termohlen.david@orbital.com  Thu Nov 20 09:57:36 1997
From: "Termohlen.David"<termohlen.david@Orbital.COM>
Date: Thu Nov 20 09:57:40 PST 1997
Subject: Re-hosing of RISC Watch
--MimeMultipartBoundary
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
     I am currently hosting a RISCWatch on an OLD IBM-AIX box.  I would
     like to re-host on a newer system (preferably a Solaris based system).
     Any advice?
     Dave Termohlen
--MimeMultipartBoundary--
From uchenick@tis4000.com  Thu Nov 20 10:41:34 1997
From: Gordon Uchenick <uchenick@tis4000.com>
Date: Thu Nov 20 10:41:38 PST 1997
Subject: RE: Soft reboot hangs IPIC on MVME162-512A
I have had the same problem on the MVME162-042. Also, a call to reboot()
will do the same thing. My solution was to write my own reboot routine which
used the watchdog timer to cause a hardware reset. If you like, I can share
that code with you.
----------
Rebooting my MVME162-512A with <cntrl-X> seam to hang the IndustryPack
Interface Controller (IPIC). I get a bus error when I try to read the
ID-ROM on the
IP's after a <cntrl-X> reboot. After a hardware reset the IPIC works
okay.  I have
several  MVME162-022A and I have never had this problem with these
boards.
From phil@naic.edu  Thu Nov 20 11:39:47 1997
From: phil@naic.edu (Phil Perillat)
Date: Thu Nov 20 11:39:50 PST 1997
Subject: RE: Soft reboot hangs IPIC on MVME162-512A
>
> Submitted-by uchenick@tis4000.com  Thu Nov 20 10:41:34 1997
> Submitted-by: Gordon Uchenick <uchenick@tis4000.com>
>
> I have had the same problem on the MVME162-042. Also, a call to reboot()
> will do the same thing. My solution was to write my own reboot routine which
> used the watchdog timer to cause a hardware reset. If you like, I can share
> that code with you.
>
> ----------
>
> Rebooting my MVME162-512A with <cntrl-X> seam to hang the IndustryPack
> Interface Controller (IPIC). I get a bus error when I try to read the
> ID-ROM on the
> IP's after a <cntrl-X> reboot. After a hardware reset the IPIC works
> okay.  I have
> several  MVME162-022A and I have never had this problem with these
> boards.
>
Check page 4-31 of the mvme162fx programmers reference guide:
"Unlike the IPIC used on earlier versions of the MVME162, the IPRESET* is
not asserted when the RESET* in to the ASIC (board level reset) is asserted"..
phil perillat
arecibo observatory
phil@naic.edu
From chip@Fiberlane.com  Thu Nov 20 13:13:03 1997
From: Chip Roberson <chip@Fiberlane.com>
Date: Thu Nov 20 13:13:06 PST 1997
Subject: Re: comp.os.vxworks newsdigest
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hello,
I'm curious about this $11k price tag for the JVM from WRS.
I've heard a substantially higher price.  What's the deal?
Thanks,
 Chip
--
Charles S. Roberson <Chip@Fiberlane.com>
This message may contain two attachments:
My Netscape Address Card and my S/MIME Public Key Digital Certificate
--MimeMultipartBoundary--
From bob_anderson@void.mclean.mcd.mot.com  Thu Nov 20 13:58:10 1997
From: Bob Anderson <bob_anderson@void.mclean.mcd.mot.com>
Date: Thu Nov 20 13:58:14 PST 1997
Subject: RE: Soft reboot hangs IPIC on MVME162-512A
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
I don't recall the differences but the -512A uses the IPchip2 interface
which has a slightly different reset mechanism from the IPchip1 used on
the -022A.  Check with your local Motorola office to see if he can dig
up the info for you.
Bob Anderson
------------------------------------------------------------------------
-----
Robert E. Anderson
Motorola Computer Group
8945 Guilford Road, Ste 145
Columbia, MD 21046
voice: 410-312-5929, fax: 410-381-4496
page: 800-SKY-PAGE pin 2839557
bob_anderson@mcg.mot.com
http://www.mot.com/computer
>-----Original Message-----
>From:	vxwexplo@lbl.gov [SMTP:vxwexplo@lbl.gov]
>Sent:	Thursday, November 20, 1997 12:24 PM
>To:	vxworks_users@csg.lbl.gov
>Subject:	Soft reboot hangs IPIC on MVME162-512A
>
>Submitted-by leif.thuresson@tsl.uu.se  Thu Nov 20 09:23:32 1997
>Submitted-by: Leif Thuresson <leif.thuresson@tsl.uu.se>
>
>--MimeMultipartBoundary
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
>Rebooting my MVME162-512A with <cntrl-X> seam to hang the IndustryPack
>Interface Controller (IPIC). I get a bus error when I try to read the
>ID-ROM on the
>IP's after a <cntrl-X> reboot. After a hardware reset the IPIC works
>okay.  I have
>several  MVME162-022A and I have never had this problem with these
>boards.
>
>-Leif
>
--MimeMultipartBoundary--
From SSearcy@mis-resources.com  Thu Nov 20 14:19:57 1997
From: Shawn Searcy <SSearcy@mis-resources.com>
Date: Thu Nov 20 14:20:00 PST 1997
Subject: HELP ME PLEASE !!!
--MimeMultipartBoundary
Content-Type: text/plain
  Dear Sir/ Ma'am,
  Hello, my name is Shawn Searcy,  and I am  Recruiter for a company
here in the Atlanta, Ga. area called MIS Resources International. I am
contacting you because I am looking to fill a position for a contract
and I am not having any luck. I was wondering if you could help me.
here is the requirements for the position, where can I find someone who
would fit this background, or do you know anyone who fits this?
 Thank you , and if I can ever do anything for you, please dont hesitate
to contact me.  Shawn Searcy
DEC VMS VX Works - Real-time
 Coastal, NC
 Must have strong experience with C in a VXWorks operating system.  Also
needs experience in the manufacturing environment with development in a
UNIX host evironment and VMS.  Experience with X/Motif, DataViews and/or
X-Designer, and TCP/IP a plus.
Shawn Searcy
ssearcy@mis-resources.com
(800)486-1704
ssearcy@hotmail.com     personal
--MimeMultipartBoundary--
From cgrames@mdc.com  Thu Nov 20 15:20:58 1997
From: Charlie Grames <cgrames@mdc.com>
Date: Thu Nov 20 15:21:01 PST 1997
Subject: UDP Broadcasts
All,
Has anyone ever attempted a UDP broadcast with VxWorks?  I managed to do everything I needed
in Berkeley sockets to get the broadcast to work, but I was kind of surprised that sending to IP
address 255.255.255.255 did not cause the message to go out all IP (Ethernet and backplane)
interfaces (it just went out the first in the interface list).  On multihomed UNIX systems I have
tested (Solaris), the message was sent out all interfaces.  Is there something special I have to do
(enable, etc.) under VxWorks to get the same behavior, or do I just need to send the broadcast out
each interface separately?  Thanks.
Charlie Grames
The Boeing Company
(314) 233-1956
Charles.R.Grames@boeing.com
From cgrames@mdc.com  Thu Nov 20 15:29:59 1997
From: Charlie Grames <cgrames@mdc.com>
Date: Thu Nov 20 15:30:02 PST 1997
Subject: RE: Tornado on Windows NT -Reply
--MimeMultipartBoundary
Content-Type: text/plain
Content-Disposition: inline
Submitted-by lars.antback@pullmax.se  Thu Nov 20 08:49:40 1997
Submitted-by: lars.antback@pullmax.se
>We have installed the Tornado tree on each machine and are copying the
>"\tornado\target" tree each time a change in the kernel is made. This
>adds some amount of administration but it works.
It is not necessary to install the entire Tornado tree on each NT machine.  We have had a lot of
success with maintaining Tornado on a single machine and using NT sharing and drive mapping
to provide access to other machines.  The only thing that needs to be done on the remote
machines to support this is to define the environment variables WIND_BASE and
WIND_REGISTRY to contain the path of the base of the Tornado tree and the name of the
machine on which the Wind Registry is running, respectively.  (The hosts file must also contain
the IP address of the registry machine.)  Adding the Portmapper to the startup group on the
remote machine completes the setup.
Charlie Grames
The Boeing Company
(314) 233-1956
Charles.R.Grames@boeing.com
--MimeMultipartBoundary--
From a.g.kirke@ieee.org  Thu Nov 20 15:35:49 1997
From: Al Kirke <a.g.kirke@ieee.org>
Date: Thu Nov 20 15:35:56 PST 1997
Subject: Re: HELP ME PLEASE !!!
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
At 02:20 PM 11/20/97 PST, you wrote:
What's it worth?
Al Kirke
>Submitted-by SSearcy@mis-resources.com  Thu Nov 20 14:19:57 1997
>Submitted-by: Shawn Searcy <SSearcy@mis-resources.com>
>
>--MimeMultipartBoundary
>Content-Type: text/plain
>
>  Dear Sir/ Ma'am,
>  Hello, my name is Shawn Searcy,  and I am  Recruiter for a company
>here in the Atlanta, Ga. area called MIS Resources International. I am
>contacting you because I am looking to fill a position for a contract
>and I am not having any luck. I was wondering if you could help me.
>here is the requirements for the position, where can I find someone who
>would fit this background, or do you know anyone who fits this?
> Thank you , and if I can ever do anything for you, please dont hesitate
>to contact me.  Shawn Searcy
>
>DEC VMS VX Works - Real-time
> Coastal, NC
> Must have strong experience with C in a VXWorks operating system.  Also
>needs experience in the manufacturing environment with development in a
>UNIX host evironment and VMS.  Experience with X/Motif, DataViews and/or
>X-Designer, and TCP/IP a plus.
>
>Shawn Searcy
>ssearcy@mis-resources.com
>(800)486-1704
>ssearcy@hotmail.com     personal
--MimeMultipartBoundary--
From daemon@csg.lbl.gov  Fri Nov 21 04:01:41 1997
From: daemon@csg.lbl.gov
Date: Fri Nov 21 04:01:46 PST 1997
Subject: comp.os.vxworks newsdigest
Comp.Os.Vxworks Daily Digest    Fri Nov 21 04:01:37 PST 1997
        Subject: Q: Very strange behaviour of sprintf. Any hints?
        Subject: Re: intLock() vs. taskLock()
        Subject: Re: USB Chipset support
        Subject: Re: How to interface the IP stack
-------------------------------------------------------
Newsgroups: comp.os.vxworks
Subject: Q: Very strange behaviour of sprintf. Any hints?
Date: Thu, 20 Nov 1997 11:04:27 +0100
From: "Martin Schulten" <schulten@aps.rwth-aachen.de>
Organization: Aachen University of Technology / Rechnerbetrieb Informatik
Message-ID: <65120o$12b$1@news.rwth-aachen.de>
hi,
i use Tornado/NT in combination with a mv1604 target.
compiling the following code makes different results:
double pos[18];
char replyMsg[1024];
(...)
- ---> solution 1:
sprintf(replyMsg, "%f %f %f %f %f %f %f %f %f %f %f %f %f %f %f %f %f
%f\r\n",
        pos[0], pos[1], pos[2], pos[3], pos[4], pos[5],
        pos[6], pos[7], pos[8], pos[9], pos[10], pos[11],
        pos[12], pos[13]+PI/2.0, pos[14]-PI/2.0, pos[15]+PI/2.0, pos[16],
pos[17]);
this is the way most people would do it, including me. unfortunately, the
result is amazing:
some values are missing, some are 0, ...
if i declare replyMsg as static, vxWorks throws an exception (alignment or
FP underflow ?!)
- ---> solution 2:
sprintf(replyMsg, "%f %f %f %f %f %f",
        pos[0], pos[1], pos[2], pos[3], pos[4], pos[5]);
sprintf(replyMsg, "%s %f %f %f %f %f %f",
        replyMsg, pos[6], pos[7], pos[8], pos[9], pos[10], pos[11]);
sprintf(replyMsg, "%s %f %f %f %f %f %f\r\n",
        replyMsg, pos[12], pos[13]+PI/2.0, pos[14]-PI/2.0, pos[15]+PI/2.0,
pos[16], pos[17]);
this way everything works fine!
can anybody explain this behaviour? i increased the stack size and tried a
lot of other things,
but i cannot see a reason for it.
any ideas are extremely welcome.
thanx in adv., martin.
---------------------------
Newsgroups: comp.os.vxworks
Subject: Re: intLock() vs. taskLock()
Date: 20 Nov 1997 18:29:06 GMT
From: Hwa-Jin Bae <chaos@idiom.com>
Organization: The DeRome Mansion
Message-ID: <651vhi$j85$1@news.idiom.com>
References: <199711191908.LAA26054@volcanoes.rti.com>
Hi!
Contrary to what's been said by others, intUnlock does do
reschedule (unlike taskUnlock).  This is true for all
VxWorks architecture ports that I've used -- 68k, mips, sparc, i960.
It would make no sense to make intUnlock do rechedule anyway.
---------------------------
Newsgroups: comp.os.vxworks
Subject: Re: USB Chipset support
Date: Thu, 20 Nov 1997 11:29:45 -0800
From: Dennis Chou <dchou4u@hotmail.com>
Organization: Cisco Systems, Inc.
Message-ID: <34748FA8.DCEB5CB5@hotmail.com>
References: <3474881F.129AF2BE@efficient.com>
Cypress Semi has sample source to control their USB chips. Just ask for
it.
But it is not VxWorks driver, if that is what you are asking 4.
Dennis
Tim Michals wrote:
> All,
>
> Is there any dirvers for any USB chip set available?
>
> Tim
---------------------------
Newsgroups: comp.os.vxworks
Subject: Re: How to interface the IP stack
Date: Wed, 19 Nov 1997 09:18:49 -0500
From: "Joshua" <jyoo@stisierra.com>
Organization: Sierra Technologies, Inc
Message-ID: <3459ceb3.0@news.ronconet.com>
References: <3471EBA8.53A6@nortel.ca>
Network driver has similarities with Unix Driver model.
If you are familiar with that, it will be helpful.
BSp porting Kit manual Chapter 9 describes the most
basic thing you have to do. Though it is not intended to teach
alphabet, it gives most of ideas. And some sample driver
source code can be really helpful.
garo@nortel.ca wrote in message <3471EBA8.53A6@nortel.ca>...
>We are writing our data link layer software and I am looking for
>information on the VxWorks (5.3.1) IP stack interface. Are there any
>libraryfunctions where we can attach our send/receive routines etc. and
>let the the Network Layer and above functionality being taken care of IP
>stack.
>
>Has any one done this before ? I would appreciate any information on
>this subject.
>
>Thanks in advance.
>
>Garo
---------------------------
End of New-News digest
**********************
From froeber@bbn.com  Fri Nov 21 05:34:19 1997
From: Fred Roeber <froeber@bbn.com>
Date: Fri Nov 21 05:34:22 PST 1997
Subject: Re: VxWorks pricing
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Mike Anderson wrote:
>   Now, if you look at WRS's financials, you'll see that WRS is
> raking in the money anyway.  Their primary market is still the
> large corporation (let's face it, manufacturers are where the
> money's at anyway).  As the prices continue to increase and
> we get nickle-and-dimed to death with the add-ons ($11K for
> the Java VM!?!?), there will be some defections to the cheapy
> x86 kernels.  But, as long as WRS's revenues continue to
> increase, there is absolutely no incentive for them to change
> their pricing/licensing policies.  I too love VxWorks (in spite
> of my rantings about Tornado) and if money is no object, I'll
> pick VxWorks every time.  However, some of the x86 kernels aren't
> too bad (for the right kind of application).  If I were WRS,
> I wouldn't get too complacent about their leadership role in the
> RTOS marketplace.  There are lots of good kernels sneaking up
> behind.
I too have been a VxWorks fan for many years. I just had to make
the decision whether to use VxWorks on yet another project. The
steep price ($19K for one target/one seat) gave me great pause.
Turns out PSOS is about that much too now. There are, however,
plenty of other OS products out there that are cheaper to buy
and to license per target. Because of our background with VxWorks
(not wanting to take the hit for learning some other toolset/OS)
we decided to stick with VxWorks for the project.
Part of the reason there hasn't been much talk about pricing here is
that there was a lot of discussion when Tornado first came out about
having to pay to get it. Lots of us just decided to put off getting
Tornado at that time and stick with 5.2. The early obsolesence of
VxWorks 5.2 however is not what was expected. I would worry a bit
if I were Wind River that some good competition could cause a big
defection. If (when?) Windows CE gets its act together it could be
a serious force to be dealt with. All I can say is that I am
beginning to feel that Wind River is acting a bit like Digital
Equipment Corp acted in the early 80s (guess that dates me). Back
then DEC had a pretty good lock on the technical computing market
with their VAXes. They started driving up prices for machines and
support and add-on products. People started defecting to the (then
new) SUN workstations. Even though the SUNs were problematical
at first, the cost savings was substantial so people put up with
the problems. Through heavier use, the SUN stuff quickly improved.
The rest, as they say, is history with DEC entering a big slump and
suffering many years of low and negative earnings.
What's the saying, "those that don't pay attention to history are
doomed to repeat it". Don't get me wrong. I think Wind Rivers products
are technically great and I like their continuing improvements.
It's just getting harder and harder to justify the prices. Enough
said.    Fred
--
   |     Fred J Roeber,  BBN Systems & Technologies     |
   |   4 John Clarke Road   Middletown, RI  02842-5202  |
   |         froeber@bbn.com     401-848-3548           |
--MimeMultipartBoundary--
From mblack@synaptyx.com  Fri Nov 21 05:56:23 1997
From: Mitch Black <mblack@synaptyx.com>
Date: Fri Nov 21 05:56:26 PST 1997
Subject: RE: Customizing target shell
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Has anyone attempted to add customized commands to the target shell?  We =
want to use the shell as a rudimentary system config interface.  With =
only a few available commands.  I would customize help and probably edit =
symtbl.c so the whole thing isn't included in the app image.  Has anyone =
done anything like this?
Thanks!
Mitchell Black
Synaptyx Corporation
12850 Middlebrook Road, #209
Germantown, MD  20874
Email:  mblack@synaptyx.com
Web:  www.synaptyx.com
--MimeMultipartBoundary--
From Jim.Rosenow@mts.com  Fri Nov 21 07:03:02 1997
From: "Rosenow, Jim" <Jim.Rosenow@mts.com>
Date: Fri Nov 21 07:03:05 PST 1997
Subject: RE: comp.os.vxworks newsdigest
--MimeMultipartBoundary
Content-Type: text/plain
Martin,
The PowerPC EABI specification for calling convention states that the
first 8 ints, longs or pointers get passed in r3 - r10.  The first 8
floats get passed in f1-f8.  The ninth (and beyond) get passed on a
stack in memory.  This is NOT how the GNU compiler is passing arguments.
Consider the following call:
doit(0,1,2,1.0,2.0,3.0,4.0,5.0,6.0,7.0,8.0,9.0);
EABI would fill registers thusly:
r3 = 0;    f1 = 1.0;
r4 = 1;    f2 = 2.0;
r5 = 2;    f3 = 3.0;
              f4 = 4.0;
              f5 = 5.0;
              f6 = 6.0;
              f7 = 7.0;
              f8 = 8.0;
stack --> 9.0 (as double);
GNU ccppc is filling them like so:
r3 = 0;                                                          f1 =
1.0;
r4 = 1;                                                          f2 =
2.0;
r5 = 2;                                                          f3 =
3.0;
r6 = upper 32bits of the double 9.0              f4 = 4.0;
r7 = lower 32bits of the double 9.0               f5 = 5.0;
                                                                    f6 =
6.0;
                                                                    f7 =
7.0;
                                                                    f8 =
8.0;
The problem is that the vxWorks link libraries are built with a
different compiler than the GNU compiler that WRS ships with the PowerPC
development environment.  The link libs expect the EABI stacking
convention.  In my example, the var_arg library call sprintf is looking
on the stack for the ninth float when in fact the GNU compiler passed it
in r6 and r7!  If you were to compile your example under the DAIB
compiler,  a truly EABI compilant compiler, the call would behave the
way you expect.  See SPR 9138.
Jim
> -------------------------------------------------------
>
> Newsgroups: comp.os.vxworks
> Subject: Q: Very strange behaviour of sprintf. Any hints?
> Date: Thu, 20 Nov 1997 11:04:27 +0100
> From: "Martin Schulten" <schulten@aps.rwth-aachen.de>
> Organization: Aachen University of Technology / Rechnerbetrieb
> Informatik
> Message-ID: <65120o$12b$1@news.rwth-aachen.de>
>
> hi,
>
> i use Tornado/NT in combination with a mv1604 target.
> compiling the following code makes different results:
>
> double pos[18];
> char replyMsg[1024];
> (...)
>
> - ---> solution 1:
> sprintf(replyMsg, "%f %f %f %f %f %f %f %f %f %f %f %f %f %f %f %f %f
> %f\r\n",
>         pos[0], pos[1], pos[2], pos[3], pos[4], pos[5],
>         pos[6], pos[7], pos[8], pos[9], pos[10], pos[11],
>         pos[12], pos[13]+PI/2.0, pos[14]-PI/2.0, pos[15]+PI/2.0,
> pos[16],
> pos[17]);
>
> this is the way most people would do it, including me. unfortunately,
> the
> result is amazing:
> some values are missing, some are 0, ...
> if i declare replyMsg as static, vxWorks throws an exception
> (alignment or
> FP underflow ?!)
>
>
> - ---> solution 2:
> sprintf(replyMsg, "%f %f %f %f %f %f",
>         pos[0], pos[1], pos[2], pos[3], pos[4], pos[5]);
> sprintf(replyMsg, "%s %f %f %f %f %f %f",
>         replyMsg, pos[6], pos[7], pos[8], pos[9], pos[10], pos[11]);
> sprintf(replyMsg, "%s %f %f %f %f %f %f\r\n",
>         replyMsg, pos[12], pos[13]+PI/2.0, pos[14]-PI/2.0,
> pos[15]+PI/2.0,
> pos[16], pos[17]);
>
> this way everything works fine!
>
> can anybody explain this behaviour? i increased the stack size and
> tried a
> lot of other things,
> but i cannot see a reason for it.
>
> any ideas are extremely welcome.
>
> thanx in adv., martin.
>
>
>
--MimeMultipartBoundary--
From froeber@bbn.com  Fri Nov 21 07:38:46 1997
From: Fred Roeber <froeber@bbn.com>
Date: Fri Nov 21 07:38:57 PST 1997
Subject: Re: UDP Broadcasts
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Charlie Grames wrote:
> Has anyone ever attempted a UDP broadcast with VxWorks?  I managed to do everything I needed
> in Berkeley sockets to get the broadcast to work, but I was kind of surprised that sending to IP
> address 255.255.255.255 did not cause the message to go out all IP (Ethernet and backplane)
> interfaces (it just went out the first in the interface list).  On multihomed UNIX systems I have
> tested (Solaris), the message was sent out all interfaces.  Is there something special I have to do
> (enable, etc.) under VxWorks to get the same behavior, or do I just need to send the broadcast out
> each interface separately?
It's sort of a coincidence that I was checking into a related problem
with networking last night. In going through what I consider to be
the best definitive guides on the subject (the Stevens TCP/IP
Illustrated Volume 1/2 books) I read and was surprised by how this
exact issue is handled. Unfortunately, I can't provide an exact
page reference but I think it was in Volume 1, not Volume 2. As with
most networking stuff, the way it works is inconsistent across
implementations. MOST implementations will only send "general"
broadcasts out the first configured network in a multihomed system.
Some (such as Solaris) will send general broadcasts out all
connected interfaces. To be safe/portable you really should send
"network" broadcasts for each connected network rather than general
broadcasts.
Don't you just love the consistency of UNIX? My big question is how
much all these little details in network handling will change with
the new VxWorks networking protocol stack implementation? How much
code will have to change? Anyone have any good answers on exactly
what the new code is and when we see it? I heard performance
is greatly improved.   Fred
--
   |     Fred J Roeber,  BBN Systems & Technologies     |
   |   4 John Clarke Road   Middletown, RI  02842-5202  |
   |         froeber@bbn.com     401-848-3548           |
--MimeMultipartBoundary--
From a.g.kirke@ieee.org  Fri Nov 21 07:40:12 1997
From: Al Kirke <a.g.kirke@ieee.org>
Date: Fri Nov 21 07:40:15 PST 1997
Subject: Re: VxWorks pricing
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
At 05:34 AM 11/21/97 PST, you wrote:
>Submitted-by froeber@bbn.com  Fri Nov 21 05:34:19 1997
>Submitted-by: Fred Roeber <froeber@bbn.com>
>
>--MimeMultipartBoundary
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
>Mike Anderson wrote:
>
-snip
>I too have been a VxWorks fan for many years. I just had to make
>the decision whether to use VxWorks on yet another project. The
>steep price ($19K for one target/one seat) gave me great pause.
-snip
>If (when?) Windows CE gets its act together it could be
>a serious force to be dealt with.
WRS prices: $2800(?!) for Tornado(TM) maintenance and phone support.
WRS prices, for a lot of projects, are now outweighed by other factors.
WRS prices will be adjusted when competition shows up, but
WRS prices will be remembered.
I like what I know about QNX.  I wonder if they send out
evaluation copies.
>What's the saying, "those that don't pay attention to history are
>doomed to repeat it".
This statement is wrong. History does not repeat. People do.
Cheers,
Al Kirke
--MimeMultipartBoundary--
From jford@sadira.gb.nrao.edu  Fri Nov 21 07:57:40 1997
From: John Ford <jford@bara.gb.nrao.edu>
Date: Fri Nov 21 07:57:43 PST 1997
Subject: Re: VxWorks pricing
>Submitted-by froeber@bbn.com  Fri Nov 21 05:34:19 1997
>Submitted-by: Fred Roeber <froeber@bbn.com>
<big snip>
> I would worry a bit
> if I were Wind River that some good competition could cause a big
> defection.
I have been following the development of the RTEMS system.  It is
pretty neat, being based on the now defunct ORKID spec.  It lacks only
a few key features that vxWorks has, (networking, run-time loadable
modules, run-time task spawning, resident shell), but it seems that
many of these features are being added by users.  For users of deeply
embedded systems (the ones WRS is targeting with tornado), I think
that RTEMS is probably as good a choice.
For us, the run-time loader, networking, and task spawning are the big
reasons for using vxWorks, along with inertia.  Our systems are highly
dynamic, with code changes occuring often, so we will never get to the
deeply embedded realm.  That said, however, there are more than a few
people grumbling with the price/value equation of vxWorks run-times
and support costs vis-a-vis something else (QNX,RTEMS,Nucleus, etc.)
> If (when?) Windows CE gets its act together it could be
> a serious force to be dealt with.
<spit>  Unfortunately, I think you are right.
--
John Ford
National Radio Astronomy Observatory
Green Bank, WV 24944-0002
jford@nrao.edu
From froeber@bbn.com  Fri Nov 21 08:08:35 1997
From: Fred Roeber <froeber@bbn.com>
Date: Fri Nov 21 08:08:38 PST 1997
Subject: Re: intLock() vs. taskLock()
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hwa-Jin Bae wrote:
> Contrary to what's been said by others, intUnlock does do
> reschedule (unlike taskUnlock).  This is true for all
> VxWorks architecture ports that I've used -- 68k, mips, sparc, i960.
> It would make no sense to make intUnlock do rechedule anyway.
Ok, lets try to get this straight once and for all. Hwa-Jin was
typing a bit too fast when he tried to explain what happens. On
the first line he should have said "intUnlock does NOT do reschedule".
That is the correct statement and agrees with the last line of his
message. Thus, from a performance perspective (which is where this
thread originally started), locking interrupts is a more efficient
way of protecting a critical section than task locking since
interrupt locking just involves hardware manipulation and task
unlocking requires a pass through the rescheduling code. That said,
there is still the issue that interrupt locking is dangerous. You
make a mistake with interrupts locked, you hang your processor.
Further, interrupt locking directly affects VxWorks responsiveness
and latency at handling things. Lock interrupts too long and hardware
stops working. Still, used carefully, nothing beats interrupt
locking for high performance, short, critical sections. Interrupt
locking is like a sharp knife. It does the job a lot better than
a dull one but can hurt a lot worse if used wrong.   Fred
--
   |     Fred J Roeber,  BBN Systems & Technologies     |
   |   4 John Clarke Road   Middletown, RI  02842-5202  |
   |         froeber@bbn.com     401-848-3548           |
--MimeMultipartBoundary--
From cpinkard@falcon.kla-tencor.com  Fri Nov 21 11:10:11 1997
From: Christopher Pinkard <cpinkard@falcon.kla-tencor.com>
Date: Fri Nov 21 11:10:14 PST 1997
Subject: Re: VxWorks pricing
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
the vxWorks Users Group Exploder wrote:
>
> WRS prices: $2800(?!) for Tornado(TM) maintenance and phone support.
>
> WRS prices, for a lot of projects, are now outweighed by other factors.
>
> WRS prices will be adjusted when competition shows up, but
> WRS prices will be remembered.
>
I just reluctantly got sign-off on two seats for Tornado/Windview:
The total was $38,745.  That is way out of line.  There is a bandwagon
effect going on.  I've used VxWorks on and off since 1987.  I had
two years using PSOS with Xray and found it to be a better debugging
environment.  I really wanted to give Chorus a chance on this
project, but management prefers to dance with the devil they know
than one they don't.  Now Chorus was bought by Sun, so I don't know
anymore.
I also just paid $1250 for a MIPS development environment from
Algorithmics in the UK, which is an order of magnitude better value
for the price for a value-added GNU port, compared to either Wind
River or Cygnus.
At embedded systems conference a few weeks back, I had lots of
interesting conversations with emerging RTOS people who can offer
competition as alternatives to VxW or CE.
--
----------------------------------------------------
Chris Pinkard             Sr. Staff SW Engineer
KLA-Tencor                RAPID Engineering
160 Rio Robles            C2-3400
San Jose, CA              95161-9055
cpinkard@falcon.kla.com   408-875-4346
--MimeMultipartBoundary--
From Sunita_Bhama_at_2-Troy-HITC@CCGATE.HAC.COM  Fri Nov 21 12:11:35 1997
From: Sunita_Bhama_at_2-Troy-HITC@CCGATE.HAC.COM
Date: Fri Nov 21 12:11:39 PST 1997
Subject: Combinning object file on VxWorks
     Hi All,
     I am working on a project, in which VxWorks/Tornado is new for every
     one in the group.
     I am trying to port Bootp server (Unix/C version) to VxWorks. The
     source consists of several object files. I need to create one ".o"
     file for VxWorks. My understanding is that executable need to be ".o"
     file to load on VxWorks (Please correct me if I am wrong).
     Is there a way you can do it? Any hints, pointers will be helpful.
     Thanks in advance for the any help.
     Sunita Bhama
From cpinkard@falcon.kla-tencor.com  Fri Nov 21 18:17:50 1997
From: Christopher Pinkard <cpinkard@falcon.kla-tencor.com>
Date: Fri Nov 21 18:17:53 PST 1997
Subject: Re: VxWorks pricing
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
In all fairness, after a half hour of discussion with my Wind River
rep, who is upset that I have unfairly portrayed the costs and
benefits by not comparing apples to apples ...
Let me try to mitigate my previous remarks:
>I just reluctantly got sign-off on two seats for Tornado/Windview:
>The total was $38,745.
The fair figure for simply two Tornado seats is $22,520.
WindView is a unique tool, according to my rep.  Meaning it is
unlike anything else out there. I have not used it yet, but
it looks like a very useful tool for monitoring the run-time
behavior of a system.  Hopefully a great addition to the debug
arsenal, costing $8,775 for the two seats.
We also bought the BSP porting kit for $3000 and a device
drivers kit for $5000.  That's how we got to over 38K.
>That is way out of line.
Am I as wrong as my rep thinks about this?  Is the completeness and
portability and scalability and all the other "ilities" of Tornado
worth all those thousands - compared to salaries and overheads
and other tools?  They say their prices have come down and PSOS
and others have come up, so that they are in fact the most cost
effective solution as well as the most comprehensive.  Maybe they're
right.  I will still be watching the market for other companies
whose "ilities" are not quite as great but whose features are
adequate to keep me productive.
We also spent $35,000 for another custom processor board to have
another RTOS company give us a complete development environment,
target agents, TCP/IP based debugging, full kernel services
(including priority inversion safe semaphores, etc), customized
porting and creation of our BSP, full support for a year, and
guess what, complete source code - kernel, libs and all.  We
don't really wan't to dink around with kernel source code, that's
why we go to a proven kernel.  It's still comparing apples and
oranges, in that VxWorks does more, on more processors, with more
3rd party vendors, more guarantee that they'll be here for the
long term, etc., whereas this small aggressive company has more
than met our needs and expectations by doing the port, providing
source code and excellent technical support.
>There is a bandwagon effect going on.
>I've used VxWorks on and off since 1987.  I had
>two years using PSOS with Xray and found it to be a better debugging
>environment.  I really wanted to give Chorus a chance on this
>project, but management prefers to dance with the devil they know
>than one they don't.  Now Chorus was bought by Sun, so I don't know
>anymore.
Tornado is getting the lion's share of the market - is it a steamroller
effect? everybody jumping on the bandwagon?  Or is it really head and
shoulders above all the competition?  Do they provide stability and
features nobody else does?  Or is it that people like to go with a winner
and Wind Rivers is winning?  It works.  People are building complex
systems that work.  It has capabilities that you can grow your system
into - mainly all the cool net-enabled things like web and java
serving.  I don't know the answer, I only have my limited opinion,
which I've stated.
>I also just paid $1250 for a MIPS development environment from
>Algorithmics in the UK, which is an order of magnitude better value
>for the price for a value-added GNU port, compared to either Wind
>River or Cygnus.
Here I got criticized again for apples vs. VxWorks.  Tornado is not
just a Gnu value addition.  But for a MIPS 5000 solution to start
implementing my low level monitor for board bringup, the Algorithmics
stuff has provided me with a great environment and excellent MIPS
oriented libraries for MMU and cache management.  But still, it's
only a well documented Gnu port for compiling and debugging - it's
not an institution.  So it's more than an order of magnitude less
than Tornado in both cost and benefit.  But it's meeting my needs
right now.
>At embedded systems conference a few weeks back, I had lots of
>interesting conversations with emerging RTOS people who can offer
>competition as alternatives to VxW or CE.
Most of them advertise in embedded systems trade publications.
It's america, I can root for the underdogs ;-)
--
----------------------------------------------------
Chris Pinkard             Sr. Staff SW Engineer
KLA-Tencor                RAPID Engineering
160 Rio Robles            C2-3400
San Jose, CA              95161-9055
cpinkard@falcon.kla.com   408-875-4346
--MimeMultipartBoundary--
From darryl@cognex.com  Fri Nov 21 18:47:24 1997
From: darryl@cognex.com (Darryl Troxel)
Date: Fri Nov 21 18:47:31 PST 1997
Subject: booting pc486 BSP
We're spec-ing the hardware for a Pentium/PCI implementation of our
material-inspection system.  Generic PC motherboards don't give us
enough slots or space for the proprietary boards we're using in these
systems, and one of these is a PCI-bus little-endian coprocessor....so,
we've decided to use a passive PCI backplane with a PC-compatible
Pentium SBC, under the generic "pc486" BSP.
These CPU's will be on a net, but physically remote in an industrial
environment.  I'm thinking of using an NVRAMdisk emulator for booting
because that looks like it will work with the least difference between
booting on my desk and booting in the field, and maybe fewer changes to
the BSP.  Does anybody have experiences or recommendations on this
point, either using this BSP or others?  How much difference in cost or
availability between an NVRAMdisk and plain flashRAM, on- or off-board?
Darryl
__________________________________________________________________
Darryl Troxel                    COGNEX Surface Inspection Systems
darryl@isys.com                              2060 Challenger Drive
Tel: 510.865.9882                            Alameda, CA 94501 USA
__________________________________________________________________
From rmcbain@dynavision.com  Fri Nov 21 22:45:58 1997
From: ram <rmcbain@dynavision.com>
Date: Fri Nov 21 22:46:01 PST 1997
Subject: Re: VxWorks pricing
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
<big snip>
When I evaluated RTOSs for our application, I assigned a $ value for
what the features were worth to us in terms of what it would cost us not
to have a certain feature (e.g, TCP/IP performance, or code size) or to
have a certain handicap (like poor documentation or an OS which hasn't
been shaken out by 1000s of applications). Once amortized over 100s or
1000s of targets per year, I found VxWorks impossible to beat. WRS (and
my company) probably wouldn't like me to publish this, but we were
quoted license costs of about 5% of our total material costs for the
units we shipped ($200 to $600 materials costs). Not bad when you
consider the technology WRS were supplying.
Yes, they do go for volume applications; why piss around with somebody
who sells a couple units a year? Where will that get you as a company?
Whether you like it or not, the Microsoftian way of looking for volume
applications is what rules.  Do you think Henry Ford is stupid or what?
Regards,
Rick McBain
Senior Engineer
Dynamic Control Systems
ps. This is, of course, my rant and rave against people who choose one
OS over and don't use the bottom line:   $      .
pps. In the end we chose Chorus(Sun) because our R&D chief views it as a
way to project his career move into the distributed object/java world
(which has very little to do with our VERY traditional embedded
application). Fuck. You try and use logic (what's best for the company),
and somebody comes along with choosing what's best for their careers or
their OS religion. I guess techies go into management to pull BS like
that.
--MimeMultipartBoundary--
From lee@medcom.ru  Sat Nov 22 18:34:32 1997
From: lee@medcom.ru (Lonely? Call Me)
Date: Sat Nov 22 18:34:36 PST 1997
Subject: Lonely?  Horny?  Call Me NOW 011-592-244-066
<HTML><PRE><BODY BGCOLOR="#000000"><FONT COLOR="#00FFFF" SIZE=3>
         Phone Sex -  For Adults Only
       Live Adult Chat Line - One on One
          Any topic - No holds Barred
                011-592-244-066
                011-592-246-350
  DO NOT  Pay $3.99/minute for Phone Sex
You only pay for the phone call - no other charge
          As low as 69 cents/minute
   International Long Distance Rates Apply
</FONT><FONT  COLOR="#000000" SIZE=3>

Co
From gotaa@medcom.ru  Sat Nov 22 20:43:42 1997
From: gotaa@medcom.ru (Lonely? Call Me)
Date: Sat Nov 22 20:43:46 PST 1997
Subject: Lonely?  Horny?  Call Me NOW 011-592-244-066
<HTML><PRE><BODY BGCOLOR="#000000"><FONT COLOR="#00FFFF" SIZE=3>
         Phone Sex -  For Adults Only
       Live Adult Chat Line - One on One
          Any topic - No holds Barred
                011-592-244-066
                011-592-246-350
  DO NOT  Pay $3.99/minute for Phone Sex
You only pay for the phone call - no other charge
          As low as 69 cents/minute
   International Long Distance Rates Apply
</FONT><FONT  COLOR="#000000" SIZE=3>

From rodmelby@csys.win-uk.net  Sun Nov 23 02:26:42 1997
From: rodmelby@csys.win-uk.net (Rodney W Melby)
Date: Sun Nov 23 02:26:46 PST 1997
Subject: New products
We provide the following tools that might be of interest to you:
Language transformation, code coverage vxworks C/C++, year 2000 COBOL,
Fortran and C/C++, rtos embedded database and requirements based testing.
Regards
From uweiner@madge.com  Sun Nov 23 23:54:55 1997
From: "Uri Weiner LAN-Tel" <uweiner@madge.com>
Date: Sun Nov 23 23:54:59 PST 1997
Subject: vxWorks & Winnt4.0
Have anyone tried to build GNU g++ compiler to run in winnt 4.0
environment, and to produce i960 code ?
And if so,
Is it possible to integrate it with vxWorks 5.2 libraries residing
on UNIX hosts?
Currently, I cross compile vxWorks i960 code on remote Unix stations.
Since I am not the only developer compiling on those remote UNIX
machines,
the compilations can get really sllllloooow.
My objective is to do all cross compilation locally, on my PC.
What do you think ?
~ Uri Weiner - Madge Networks
~ Tel.: (972)+3 6457602 { Home: (972)+3 6131834 }
~ Fax: (972)+3 6487146
~ Email: uweiner@madge.com { Home: uriw@netvision.net.il }
From Eli_Wittner@cti-pet.com  Mon Nov 24 06:24:24 1997
From: "Eli Wittner"<Eli_Wittner@cti-pet.com>
Date: Mon Nov 24 06:24:27 PST 1997
Subject: Re: VxWorks pricing
--MimeMultipartBoundary
Content-type: text/plain; charset=US-ASCII
Rick McBain wrote:
>>>...Yes, they do go for volume applications; why piss around with
somebody
>>>who sells a couple units a year? Where will that get you as a company?
>>>Whether you like it or not, the Microsoftian way of looking for volume
>>>applications is what rules.  Do you think Henry Ford is stupid or
what?...
>>> (Major Expletive Deleted)
Excuse me, but I'm one of the little guys who gets pissed on for selling a
couple of units a year!  In my eyes, the dialog in this thread has been
right on target so far.  Why can't Wind River make its big bucks from the
volume guys and make concessions to the little guy to broaden visibility
across multiple markets and increase the number of engineers willing to
spec. vxWorks on future projects?
The real issue aside.....Use of a public forum for personal vendetta, and
use of profanity to make a point is in extremely poor taste!
Eli Wittner
CTI Cyclotron Systems, Inc.
--MimeMultipartBoundary--
From mea@mclean.sparta.com  Mon Nov 24 07:50:57 1997
From: "Mike Anderson" <mea@mclean.sparta.com>
Date: Mon Nov 24 07:51:01 PST 1997
Subject: Re: VxWorks pricing
--MimeMultipartBoundary
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
>Submitted-by: "Eli Wittner"<Eli_Wittner@cti-pet.com>
[snip]
>Excuse me, but I'm one of the little guys who gets pissed on for selling a
>couple of units a year!  In my eyes,
Wow, getting it in the eyes must really hurt ;-).
>the dialog in this thread has been
>right on target so far.  Why can't Wind River make its big bucks from the
>volume guys and make concessions to the little guy to broaden visibility
>across multiple markets and increase the number of engineers willing to
>spec. vxWorks on future projects?
>
That is a perennial question when it comes to pricing any given
product.  Do we price it cheap and sell oodles of them (the old
Turbo Pascal model) or do we price it high and sell fewer units
(but make lots of money on those we sell).  This is always a tough
decision.  But, since WRS started in the latter camp, they've
chosen to stay there for the time being.  When the stock price
starts slipping, then maybe WRS will be interested in the "low
end" of the market with the onesey-twosey kind of opportunity.
In the mean time, it appears that we'll have to continue to tolerate
$30K+ kinds of price tags for our projects if we want to use
VxWorks/Tornado (heavy sigh...).
Regards,
---------------------------------------------------------------------
|Michael E. Anderson        | Voice -> 703 448 1683 x235            |
|Chief Engineer             | FAX   -> 703 893 5494                 |
|mea@mclean.sparta.com      | http://www.mclean.sparta.com          |
|___________________________|_______________________________________|
|             SPARTA, Inc.              |                           |
|     /\\     C4I Operation             |"Software Development is   |
|    ///\\    7926 Jones Branch Drive   | like making a baby...     |
|   /////\\   Suite 900                 | You can't make a baby in  |
|  /////  \\  McLean, VA 22102          | one month by impregnating |
| / \\\\\  \\ 703-448-0210              | nine women.               |
| \  \\\\\ //                           |                           |
|  \  //////                            | Some things just take     |
|   \//////   SPARTA                    | time."                    |
|    \////    Pride In Performance      |                           |
|     \//     --------------------      |                           |
---------------------------------------------------------------------
--MimeMultipartBoundary--
From owens2@llnl.gov  Mon Nov 24 13:50:27 1997
From: Doug Owens <owens2@llnl.gov>
Date: Mon Nov 24 13:50:30 PST 1997
Subject: SCSI and PPC (again)
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Anyone out there had this happen?
1. Running vxWorks - SCSI OK
2. Rebuild vxWorks with minor changes.
3. SCSI is DEAD!
I am using the ADDED_MODULES option to include my application code into
vxWorks.  Something as simple as declaring a small integer array in
one of my modules will break SCSI.  These sort of things are really
testing my faith in WRS.  (Tornado + vxWorks 5.3.1 under SunOS with
MV1603 PPC 200 Mhz target).  Anyone have any ideas?
TIA
Doug Owens
owens2@llnl.gov
--MimeMultipartBoundary--
From wong@vms.masd.northgrum.com  Mon Nov 24 15:59:52 1997
From: wong@vms.masd.northgrum.com (J. Pierre Wong)
Date: Mon Nov 24 15:59:56 PST 1997
Subject: C40 or C60 compilers
greetings,
does anyone know of any C40 or C60 Ada or C compilers hosted on a PC/NT?
Pierre Wong
wong@vms.masd.northgrum.com
From ratkin@ix.netcom.com  Mon Nov 24 16:12:55 1997
From: ratkin@ix.netcom.com
Date: Mon Nov 24 16:12:58 PST 1997
Subject: Re: Re-hosing of RISC Watch
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
>
>     I am currently hosting a RISCWatch on an OLD IBM-AIX box.  I would
>     like to re-host on a newer system (preferably a Solaris based system).
>     Any advice?
>
>
>     Dave Termohlen
>
Dave,
I don't think you can host the RISCWatch on anything but an IBM micro-channel
based machine running AIX 3.2.x (x = 3,4, or 5).
The classic example of this is a RS6000 Model 320 (is this what you have?), although
I think some people are using different machines.
I couldn't even port to AIX 4.1 when it came out, and had to keep the old clunker
around to host the RISCWatch card ... I simply NFS mounted the relevant directories,
and did all development on another machine.
I hope this helps, and sorry to have to say that I think you are S.O.L. !!!
Rob Atkin
Tiger Innovations, L.L.C.
--MimeMultipartBoundary--
From uucp@xmission.xmission.com  Mon Nov 24 18:41:15 1997
From: MIKE@colmek.com
Date: Mon Nov 24 18:41:18 PST 1997
Subject: Re: C40 or C60 compilers
--MimeMultipartBoundary
Content-Type: text/plain; charset=US-ASCII
Date:          Mon, 24 Nov 97 15:59:57 PST
To:            vxworks_users@csg.lbl.gov
From:          vxwexplo@lbl.gov (the vxWorks Users Group Exploder)
Subject:       C40 or C60 compilers
Submitted-by wong@vms.masd.northgrum.com  Mon Nov 24 15:59:52 1997
Submitted-by: wong@vms.masd.northgrum.com (J. Pierre Wong)
greetings,
does anyone know of any C40 or C60 Ada or C compilers hosted on a PC/NT?
Pierre Wong
wong@vms.masd.northgrum.com
If you are talking about TI TMS320C40 and TMS320C60, I have been
using the 'C' compilers from TI and have no complaints.  Tartan was
selling ADA compilers but I think TI bought them so you should be
able to get ADA from TI also.
Thanks,
Mike Taylor
miket@colmek.com
====================================
Colmek Systems Engineering
2001 South 3480 West
Salt Lake City, UT 84104-4914 USA
Voice : (801) 973-9136
Fax   : (801) 973-9285
If you have a E-mail probelms contact:
<postmaster@colmek.com>
========================================
--MimeMultipartBoundary--
From daemon@csg.lbl.gov  Tue Nov 25 04:01:07 1997
From: daemon@csg.lbl.gov
Date: Tue Nov 25 04:01:12 PST 1997
Subject: comp.os.vxworks newsdigest
Comp.Os.Vxworks Daily Digest    Tue Nov 25 04:01:04 PST 1997
        Subject: Re: VxWorks as UNIX?
        Subject: Re: vxWorks Pricing!!!!!
-------------------------------------------------------
Newsgroups: comp.os.vxworks
Subject: Re: VxWorks as UNIX?
Date: 24 Nov 1997 12:54:14 -0500
From: nigel@access1.digex.net (Nigel Tzeng)
Organization: Express Access Online Communications, Greenbelt, MD USA
Message-ID: <65cf06$c9e@access1.digex.net>
References: <65ca0e$id3@cnn.exu.ericsson.se>
In article <65ca0e$id3@cnn.exu.ericsson.se>,
David B. Paul <exudpau@exu.ericsson.se> wrote:
>OK, maybe this is going to start a feud, but...
>
>Do you consider VxWorks to be a UNIX, or merely
>UNIX-like?  I don't so much want to begin a war regarding
I consider it vaguely UNIX like.
>Or, to word the issue another way:  If someone says they have
>VxWorks experience, would you say they have UNIX experience?
Not really.  They'll have skills related to common unix development
environments (gnu, etc) but not much else.
About the only RTOS that you could make that claim for is Lynx...which
if I recall correctly is a bsd variant on top of a RT kernel.
But honestly, if you can handle VxWorks, learning unix wont be a
hardship.
As an employer in a unix environment that's good enough.  I can always
hand you a "Unix in a Nutshell" book and let you play for a week or
two to get familiar.
Just don't list Unix on your resume or I might ask you some questions
you can't answer yet.  Then that would make me hesitant to believe
anything on your resume.
>David B. Paul                |   1010 E. Arapaho Rd, M/S L-04
Nigel
---------------------------
Newsgroups: comp.os.vxworks
Subject: Re: vxWorks Pricing!!!!!
Date: 20 Nov 97 02:33:20 GMT
From: steved@pacifier.com (Steve Doiel)
Message-ID: <3473a170.0@news.pacifier.com>
References: <EJwCDH.K6I@news.boeing.com>
I agree that the price to develop for VxWorks is excessively high.  While
WRS does provide a good real-time OS, we have considered moving
to other systems strictly based on price.
I agree that WindowsCE or something else (RTEMS?) might easily take over
VxWorks position in the rankings due to this high cost.
SteveD
---------------------------
End of New-News digest
**********************
From lucard@tin.it  Tue Nov 25 06:07:55 1997
From: Luca Rodda <lucard@tin.it>
Date: Tue Nov 25 06:08:02 PST 1997
Subject: ISO/OSI Networking
This is a multi-part message in MIME format.
--------------DDD856C99F0EB920A72BA6A2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hello to everybody, does anyone know about software and/or hradware for
running ISO/OSI networking instead or together TCP/IP networking in
VxWorks environment?
The specification are as follows.
Transport Protocol: ISO 8073 Class 4
Data Link Protocol: IEEE 802.2 Class 1
Bus arbitration method: CSMA/CD following IEEE 802.3
Thanks
Luca Rodda
--------------DDD856C99F0EB920A72BA6A2
Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Luca Rodda
Content-Disposition: attachment; filename="vcard.vcf"
begin:          vcard
fn:             Luca Rodda
n:              Rodda;Luca
org:            ECT - European Computer Trading s.r.l.
adr:            via Imperia 23;;;Milano;;20142;ITALY
email;internet: lucard@tin.it
title:          Dott.
tel;work:       + 39 2 8466813
tel;fax:        + 39 2 89516186
x-mozilla-cpt:  ;0
x-mozilla-html: FALSE
end:            vcard
--------------DDD856C99F0EB920A72BA6A2--
From rschibler@BayNetworks.COM  Tue Nov 25 08:11:46 1997
From: Ross Schibler <rschibler@BayNetworks.COM>
Date: Tue Nov 25 08:11:50 PST 1997
Subject: Re: Re-hosing of RISC Watch
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
>  >
> >     I am currently hosting a RISCWatch on an OLD IBM-AIX box.  I would
> >     like to re-host on a newer system (preferably a Solaris based system).
> >     Any advice?
>
>
> I don't think you can host the RISCWatch on anything but an IBM micro-channel
> based machine running AIX 3.2.x (x = 3,4, or 5).
I disagree. We're running the ethernet attached version of the box for a PPC403
just fine with a Solaris 2.5 host. I believe they also offer a windoze 95 version.
Ross
--
Ross Schibler                      email: ross@rapid-city.com
Bay Networks, Rapid City Div.      voice:              415-237-8612
1215 Terra Bella Avenue            fax:                415-237-7388
Mountain View, CA 94043            http://www.rapid-city.com
--MimeMultipartBoundary--
From mam@pluto.dspt.com  Tue Nov 25 08:46:17 1997
From: "Mark Menge" <mam@pluto.dspt.com>
Date: Tue Nov 25 08:46:20 PST 1997
Subject: 68040 DTT0 and DTT1 register questions
I am trying to solve some problems I have with scsi and the gmsv46
board.  When I turn on data caching, SCSI locks up.
I see in sysALib.s some references to the data cache, but they are
not clear.
1. Does anyone know where I can get a good manual which describes these
registers?
2. Where do I find information on gcc asm functions?
 movel	#0x0000e000,d0		/* enable data passthrough */
movec d0,DTT0
From tkb@mclean.sparta.com  Tue Nov 25 09:36:59 1997
From: "Thomas K. Buchanan" <tkb@mclean.sparta.com>
Date: Tue Nov 25 09:37:02 PST 1997
Subject: Re: SCSI and PPC (again)
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
>I am using the ADDED_MODULES option to include my application code into
>vxWorks.  Something as simple as declaring a small integer array in
>one of my modules will break SCSI.  These sort of things are really
>testing my faith in WRS.  (Tornado + vxWorks 5.3.1 under SunOS with
>MV1603 PPC 200 Mhz target).  Anyone have any ideas?
After adding your application to the kernel, will it still load under
the bootrom image?  This can cause all kinds of headaches.
adios
--MimeMultipartBoundary--
From stan@rti.com  Tue Nov 25 12:27:37 1997
From: stan@rti.com (Stan Schneider)
Date: Tue Nov 25 12:27:40 PST 1997
Subject: Re: intLock() vs. taskLock()
Oops.  I was blew that one.  I published too quickly; intLock (at least on PPC where I looked) does not reschedule, only taskUnlock.  Sorry about the confusion...
	-- Stan
From aram.nahidipour@spdg.COM  Tue Nov 25 15:22:19 1997
From: aram.nahidipour@spdg.COM (Aram Nahidipour)
Date: Tue Nov 25 15:22:22 PST 1997
Subject: Loading compressed objects
All,
I am downloading a compressed object file from the net and
decompess it using inflate() into memory.
Then I use memDevCreate() to create a memory file which I open() later.
After that I use loadModule() to load the decompressed module. I free all
memories and close all the files at the end.
Everything is working fine except the moduleShow output is strange and if
I use "lkup" to see one of the global symbols in the newly loaded module
I get "Data abort".  Anyone have any ideas what is wrong?
Thanks in advance for the any help.
=====================================================================
Here is the psuedo code & output of moduleShow and lkup:
         if (tftpXfer (hostname, 0, filename,  "get",  "binary",
     &dataFd, &errorFd) == ERROR) /* download the compressed object */
         read (dataFd, buff, buff_size);
	 /* decompress it */
	 inflate(buff,raw_buf,size);
	/* create a memory device */
	 memDevCreate("/mem/test/",raw_buf, raw_size);
	 fd=open("/mem/test/0",2,0);
	 loadModule(fd, LOAD_GLOBAL_SYMBOLS);
	 close(fd)
	 free(raw_buf)
============================================================
Here is the output of moduleShow and lkup
-> moduleShow (gives me the following )
MODULE NAME     MODULE ID  GROUP #    TEXT START DATA START  BSS START
--------------- ---------- ---------- ---------- ---------- ----------
PHmpnnnnnnnn7npnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn/mem/test  0x1ffcb04          1  0x1ffc820  0x1ffcafc  0x1ffcafc
              0  0x1ffd88c          2  0x1f81720  0x1f819fc  0x1f819fc
value = 0 = 0x0
-> lkup "test"
Data abort
Exception address: 0x00071304
Current Processor Status Register: 0x20000013
  f2d4 _vxTaskEntry   +28 : _shell ()
 3abbc _shell         +14c: 3abfc ()
 3adcc _shell         +35c: _execute ()
 3af58 _execute       +b8 : _yyparse ()
 6ec10 _yyparse       +678: 6d098 ()
 6d1e8 _yystart       +7e0: _lkup ()
 51508 _lkup          +18 : _show ()
 50460 _show          +dc : _objShow ()
 554f8 _objShow       +78 : _symShow ()
 4444c _symShow       +d8 : _symEach ()
 441c4 _symEach       +74 : _hashTblEach ()
 433f8 _hashTblEach   +8c : _sllEach ()
From kenneth.j.ostaszewski@boeing.com  Tue Nov 25 16:23:04 1997
From: "Ken J. Ostaszewski" <kenneth.j.ostaszewski@boeing.com>
Date: Tue Nov 25 16:23:07 PST 1997
Subject: VMIC 6015 Register Setup
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
I am trying to use the VMIVME6015 quad serial board.
I can't seem to get the right combination of jumpers/resisters in the
right position to provide a simple setup for DCE communication to my NT
Host which is running HyperTerminal.
Any suggestions?
--MimeMultipartBoundary--
From ratkin@ix.netcom.com  Tue Nov 25 18:46:15 1997
From: ratkin@ix.netcom.com
Date: Tue Nov 25 18:46:18 PST 1997
Subject: Re: Re-hosing of RISC Watch
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
>>
>> I don't think you can host the RISCWatch on anything but an IBM micro-channel
>> based machine running AIX 3.2.x (x = 3,4, or 5).
>
>I disagree. We're running the ethernet attached version of the box for a PPC403
>just fine with a Solaris 2.5 host. I believe they also offer a windoze 95
>version.
>
>Ross
>
Ross,
I neglected to mention that my target is a RAD6000. This is a POWER architecture
and the POWER Dash only runs under AIX 3.2.3-5 and only supports the micro-channel
version of the RISCWatch. I have been told this by Lockheed Martin Federal Systems
(the RAD6000 board supplier -- used to be IBM Federal Systems) as well as IBM, so
I am inclined to believe it.
I was under the impression that the original question applied to a RAD6000 (I am not
exactly sure why) ... hence my answer. I apologize for any confusion it may have
generated!
Do you happen to know if your version of the RISCWatch supports the POWER architecture?
If I could get away from the RS/6000 model 320, I would be very happy. (maybe the LMFS
people are mistaken!)
Rob Atkin
Tiger Innovations, L.L.C.
--MimeMultipartBoundary--
From 05133971@aol.com  Tue Nov 25 20:54:30 1997
From: 05133971@aol.com
Date: Tue Nov 25 20:54:33 PST 1997
Subject: Earn Money Shopping
<HTML><PRE><BODY BGCOLOR="#000000"><FONT COLOR="#00FFFF" SIZE=3>
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
  ?   ?   ?   ?   ?   ?   ?      GET PAID TO SHOP   ?   ?   ?   ?   ?   ?   ?
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
How would you like to get paid $20 to $50 an hour to shop?  Stores
and restaurants that have several or even thousands of different
locations rely on 'Mystery Shoppers' all over the country to check
every location.  By having a Community Customer go to each store
and report back on the service, cleanliness, product or food quality,
guarantees consistency at every store in a chain or franchise.
'Mystery Shoppers' provide a link between Corporate Headquarters
and all their stores.  So, without going to each location, Corporate
can find out how clean their stores are, how good the service is, the
food quality and monitor how well customers are treated.
As a 'Mystery Shopper' you will use the stores or restaurants money
to shop.  many times, you will be allowed to keep the merchandise
you purchase.  There are no qualifications to be a 'Mystery Shopper'
other than the willingness to accept shopping assignments and have
a neat appearance.
This manual will even furnish you with over one hundred companies
that have contacted us, seeking 'Mystery Shoppers'.  We will ONLY
ship one manual per zip code, so order today!
This manual comes to you for the low, one-time price of only $39.95
plus $4.95 shipping and handling.  If you order by fax, within 24 hours
of receiving this advertisement, you can save $5.00!  Simply deduct
$5.00 from the purchase price and postage and handling.
Again, only one manual per zip code will be shipped, so ORDER TODAY!
Internet Marketing Solutions
5201 Kingston Pike
Suite 6-216
Knoxville, Tennessee 37919
YES,  please rush the 'Mystery Shopper (c 1997)'
___________  I have enclosed $39.95 plus $4.95 shipping and handling. ($44.90 total)
___________  I want to save $5.00! I am ordering by fax within 24 hours - I have enclosed $34.95 plus $4.95 shipping and handling. ($39.90 total)
___________ Please RUSH my order - add an additional $15.00 (OPTIONAL)
I have enclosed (Check One):
_____ Cashiers Check
_____ Money Order
_____ Personal Check
SHIPPING INFORMATION
Name:__________________________________________________
Telephone:_______-______-____________
Mailing Address:__________________________________________
_______________________________________________________
City:____________________________________________________
State:_________      ZIP:___________________________________
Your E-Mail Address (Needed for order confirmation)____________________________
 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
SAVE AN ADDITIONAL $5.00!!!  FAX YOUR ORDER NOW!
Please tape your completed and signed check in the space below and fax to IMS. That facsimile number is 1-423-681-6520.
*************************************
FAX: 1-423-681-6520
PLEASE TAPE YOUR CHECK HERE
Please SIGN you check
*************************************
Thank You For Your Order
</FONT><FONT  COLOR="#000000" SIZE=3>
From enrico.ferro@elsag.it  Wed Nov 26 02:48:29 1997
From: Enrico Ferro <enrico.ferro@elsag.it>
Date: Wed Nov 26 02:48:33 PST 1997
Subject: Wait on events and/or a time out
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Hi guys,
I am jusy quite new at VxWorks, and I'd like to have an experienced opinion
about a design issue:
Suppose that a task, at a certain point, has to wait for two different
events and a time-out. It would be something like:
        wait for (Event1, Event2, time-out)
the wait ends for whichever of the three conditions is satisfied first.
What could be the best way to implement this thing with VxWorks? It looks to
me as though it's not possible to hang on timeout and events a the same
time: am I wrong?
Thanks in advance to all of you that will provide help.
Enrico
Enrico Ferro
Elsag Bailey Hartmann & Braun S.p.A.
Via Hermada 6, 16154 Genova - Italy
Tel. 0039-10-6586222 --- Fax. 0039-10-6586210
Home 0039-10-6517797
Work E-mail Enrico.Ferro@elsag.it
Backup work e-mail address Enrico.Ferro@usa.net
Home e-mail clusede@clu.assicomitalia.it
--MimeMultipartBoundary--
From tkb@mclean.sparta.com  Wed Nov 26 04:43:44 1997
From: "Thomas K. Buchanan" <tkb@mclean.sparta.com>
Date: Wed Nov 26 04:43:47 PST 1997
Subject: Re: Wait on events and/or a time out
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
>What could be the best way to implement this thing with VxWorks? It looks to
>me as though it's not possible to hang on timeout and events a the same
>time: am I wrong?
If your "events" are associated with the I/O subsystem and the device drivers
all support it, you can use the select function.  If this is not the case,
your
conclusion is correct.  You can't block on multiple semaphores.
The good news is that there is very little overhead per task in VxWorks, I
suggest you have a task to handle each event.  With the occasional
exception of socket and file I/O, this often yields a better design in an
real-time embedded system. Nothing is free, using something like 'select'
will add a non-trivial delay.
adios
--MimeMultipartBoundary--
From froeber@bbn.com  Wed Nov 26 05:08:54 1997
From: Fred Roeber <froeber@bbn.com>
Date: Wed Nov 26 05:08:57 PST 1997
Subject: Re: 68040 DTT0 and DTT1 register questions
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Mark Menge wrote:
>
> I am trying to solve some problems I have with scsi and the gmsv46
> board.  When I turn on data caching, SCSI locks up.
Sounds like the SCSI chip on the board must not support cache snooping
the way most of the Moto boards does. If this is the case, then
data caching will cause major problems with the device. I would have
thought the BSP developer had addressed this issue. You most likely
have to set up a fixed area of memory for the interface to the SCSI
chip and then set up just that area as uncached using the MMU
(which uses the sysPhysMemDesc structure usually located in sysLib.c).
> I see in sysALib.s some references to the data cache, but they are
> not clear.
>
> 1. Does anyone know where I can get a good manual which describes these
> registers?
The Motorola 68040 User's Manual describes the registers. I ordered
it from Motorola years ago. You can probably get a copy through
their web site these days.
> 2. Where do I find information on gcc asm functions?
>
>  movel  #0x0000e000,d0          /* enable data passthrough */
> movec d0,DTT0
The same book as above outlines the processor instruction set. For
the most part, gas (the assembler) uses the same mnemonics as are
in the book. In a few cases there are differences but not many.
I don't think the transparent translation registers will help you
do what you want. They only allow disabling caching on big chunks
of memory space (16MB minimum). I think you will have to use the
MMU to do what you want. I would ask the board vendor about the
problem first. It sounds like their BSP could be deficient.   Fred
--
   |     Fred J Roeber,  BBN Systems & Technologies     |
   |   4 John Clarke Road   Middletown, RI  02842-5202  |
   |         froeber@bbn.com     401-848-3548           |
--MimeMultipartBoundary--
From phil.quiney@gecm.com  Wed Nov 26 05:30:38 1997
From: Philip Quiney <phil.quiney@gecm.com>
Date: Wed Nov 26 05:30:41 PST 1997
Subject: Re: Wait on events and/or a time out
Hi Enrico,
> Hi guys,
>
> I am jusy quite new at VxWorks, and I'd like to have an experienced opinion
> about a design issue:
>
> Suppose that a task, at a certain point, has to wait for two different
> events and a time-out. It would be something like:
>
>         wait for (Event1, Event2, time-out)
>
> the wait ends for whichever of the three conditions is satisfied first.
If the 'events' the tasks sees can be implemented as messages placed on a
message queue, then the msgQReceive function can be used. This can take a
timeout parameter this being the number of 'ticks' to wait. The wait will
terminate when an 'event' is received or if the number of ticks is exceeded,
whichever occurs first.
>
> What could be the best way to implement this thing with VxWorks? It looks to
> me as though it's not possible to hang on timeout and events a the same
> time: am I wrong?
>
Hope this helps
Phil Quiney
===============================================================================
Phil Quiney          _/_/_/_/        _/  _/_/_/_/  email : phil.quiney@gecm.com
GEC Marconi         _/    _/        _/  _/    _/     tel : +44 1245 353221x3914
Communications Ltd _/_/_/_/  _/    _/  _/  _/_/      fax : +44 1245 275448
Chelmsford        _/        _/_/_/_/  _/_/_/_/
England CM1 1PL                              _/
===============================================================================
From uchenick@tis4000.com  Wed Nov 26 06:15:48 1997
From: Gordon Uchenick <uchenick@tis4000.com>
Date: Wed Nov 26 06:15:51 PST 1997
Subject: RE: Wait on events and/or a time out
There is no single system call that lets you wait on multiple events. The
way to implement this under some other operating system is to associate an
event flag with each event and then design your task to  wait for the
logical OR of those event flags.
I have implemented this type of architecture under vxWorks, but had to use
an extra task as a "helper." For example, I wanted to have a single task
service a socket AND a ring buffer. The task should sleep until a message
arrived over the socket OR another task stuck something into the ring
buffer. Here's what worked for me:
create a binary semaphore, initially empty.
One very small task does a select on the socket(s) and does a semGive()
when a message or error condition is detected.
The library routines that put stuff into the ring buffer do a semGive() on
the same semaphore.
The service task does a semTake on that semaphore, waiting forever. When
the task wakes up, it checks the fd_set from the select and then empties
 the ring buffer.
Hope this helps. Contact me directly if you want to talk more about this.
Gordon
From ohurley@iona.com  Wed Nov 26 09:46:57 1997
From: Oisin Hurley <ohurley@iona.com>
Date: Wed Nov 26 09:47:00 PST 1997
Subject: Re: Wait on events and/or a time out
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
At 02:48 AM 11/26/97 PST, you wrote:
>I am jusy quite new at VxWorks, and I'd like to have an experienced opinion
>about a design issue:
>
>Suppose that a task, at a certain point, has to wait for two different
>events and a time-out. It would be something like:
>
>        wait for (Event1, Event2, time-out)
>
>the wait ends for whichever of the three conditions is satisfied first.
>
>What could be the best way to implement this thing with VxWorks? It looks to
>me as though it's not possible to hang on timeout and events a the same
>time: am I wrong?
Depending on the implementation of the event delivery the simplest
structure you could use is a counting semaphore, with both event
sources using the same semaphore and assuming the events are sourced
in another task (or two).
     semTake (counting_sem, timeout)
thing is, you won't know *which* of event1 and event2 has arrived
without a poll of some sort.
Reason for using counting semaphore is to ensure you don't drop
events during the loop.
There is no definitive solution to this - it's very dependent on the
nature of the problem elements.
   --oh
--MimeMultipartBoundary--
From espin@idiom.com  Wed Nov 26 10:25:06 1997
From: Geoffrey Espin <espin@idiom.com>
Date: Wed Nov 26 10:25:09 PST 1997
Subject: Re: Loading compressed objects
--MimeMultipartBoundary
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Aram,
> Submitted-by aram.nahidipour@spdg.COM  Tue Nov 25 15:22:19 1997
> I am downloading a compressed object file from the net and
> decompess it using inflate() into memory.
> Then I use memDevCreate() to create a memory file which I open() later.
> ...
Pretty dang clever!  The bug is with memDrv.c memIoctl() function
lacking a FIOGETNAME function code and loadModule() not checking
the return code, I suspect.  Just add it (target/src/config/memDrv.c)
rebuild, and all will be well.  Thanks for the tight algorithm.
Geoff
--
Geoffrey Espin espin@idiom.com
--MimeMultipartBoundary--
From espin@idiom.com  Wed Nov 26 10:31:00 1997
From: Geoffrey Espin <espin@idiom.com>
Date: Wed Nov 26 10:31:03 PST 1997
Subject: Tornado on NT4.0 and PPP
--MimeMultipartBoundary
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Folks,
I've been unsuccessful in using NT4.0 as a pppd/server for
an i960 vxworks target.
I installed DUN/RAS, setup up a modem (pc 2 pc cable and/or 9600 modem)
on COM1 and/or COM2 ports, tested h/w connectivity (i.e. was able to see
control chars come into NT4.0 hypertrm session from the vxworks target),
so what gives!?
Thanks in advance,
Geoff
--
Geoffrey Espin espin@idiom.com
--MimeMultipartBoundary--
From Jerry.I@lmco.com  Wed Nov 26 11:13:22 1997
From: "Gerard F. (Jerry) Iacangelo" <Jerry.I@lmco.com>
Date: Wed Nov 26 11:13:25 PST 1997
Subject: Embedded Client/Server Inquiry
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Please read the description of the original inquiry after the initial
reply from a WRS Field Application Engineer. In a nutshell, I am looking
for an embedded X11-based World Map tool to use in a VME system whose
configuration is defined below.
+----------------------------------------------------+
Reply From:
  Jeff Johnson
  Sr. FAE, Southeast Region
  Wind River Systems
  Email:  jeff.johnson@wrs.com
  Voice:  919-844-4885
  Fax:     919-844-4886
Reply To:
  Jerry Iacangelo
  Lockheed Martin
  VOX: 703-367-3704  FAX:703-367-3942
  E-mail: Jerry.I@lmco.com
+---------------------------------------------------+
Thanks for the inquiry Jerry.  I've forwarded you message to the network
of FAE's around the world.  This will give us some insight into anyone
out there that may be using/producing a world map tool for VxWorks.
Another place to look is on our web site at www.wrs.com.  You'll find a
list of third party vendors there.  You may also want to post your
inquiry on the new group at comp.os.vxworks.  This is maintained by
users and is often used to find information such as what you're looking
for.  There is also a users group that may have some information also.
I forget the URL for it, but we have a link from our website.
For inside inquiries, I'll be glad to be the front man.  I have the
ability to quiry both the inside and outside world of WRS.  Please feel
free to send me any future requests.
I'll be sure to forward any responses to you as soon as they arrive.
Thanks for allowing me to assist you.
At 03:47 PM 11/21/97 -0500, Iacangelo, G. F.         (Jerry) wrote:
>Mr. Johnson,
>
>  What is the best way to launch an inquiry into the vast resources of
>WRS?  Here's the configuration:
>
>Development Host: Sun Workstation
>Host OS:  Solaris 1.1.1A
>
>Embedded Host: 68040 (Motorola MVME167)
>Embedded OS: VxWorks 5.1.1
>Embedded Motif for VxWorks: VisiCom VxWindows 3.x
>Embedded X11R5 Color Graphics Server: Vigra VGS-882 (Vigra is a subsidiary of VisiCom a WRS >partner)
>
>Here's the application:
>
>Customer wants us to rapidly prototype two types of displays - status and map.  The status display is not >a problem.  The map display is and here's why.  We need to find a World Map Data Base tool in X >supported under the embedded configuration defined above.  It is assumed that this world map data is >stored on an embedded hard disk and the operator selects the geographic area of interest to display in >the main plain of the graphics server.  A desired feature of this map tool is zoom and pan.
>
>A display task will then put detection symbology and text information at the associated lat./long in the >overlay planes of the server so as not to obscure the map beneath it.  We have heard there are few >vendors that offer an X-based world map tool and of those that do it's usually at a  higher level of >integration by including the  detection display on top of the map tool.  All you have to do is  package your >data per their defined interface and the tool does the rest.  However it's our understanding that these >solutions run on a workstation platform.  In which case a port may be involved. Depending on the size >and schedule of the porting effort this could be an option.
>
>Please advise as to the best way to launch such an inquiry in the  hopes of rapidly identifying at least >one practical solution?  Regards,
>
--MimeMultipartBoundary--
From jrm@mclean.sparta.com  Wed Nov 26 15:35:22 1997
From: "John R. Moore III" <jrm@mclean.sparta.com>
Date: Wed Nov 26 15:35:25 PST 1997
Subject: SCSI2 on the Symbios 53C810
--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hello,
	Has anyone successfully implemented SCSI2 on the Symbios 53C810 ?
And if so, what platform are you using.
I'm working on a Pentium and the scsi2IfInit() call causes my network
interface to cease functioning.
Thanks,
--
------------------------------------------------------------
|John R. Moore              | Voice -> 703 448 1683 x229   |
|Principal Engineer         | FAX   -> 703 893 5494        |
|EMAIL:                     | On the WEB!                  |
|jrm@mclean.sparta.com      | http://www.mclean.sparta.com |
|___________________________|______________________________|
|                                     |                    |
|     /\\     SPARTA, Inc.            |                    |
|    ///\\    7926 Jones Branch Drive |                    |
|   /////\\   Suite 900               |                    |
|  /////  \\  McLean, VA 22102        |                    |
| / \\\\\  \\ 703-448-0120            |         	   |
| \  \\\\\ //                         |                    |
|  \  //////                          |                    |
|   \//////   SPARTA                  |                    |
|    \////    Pride In Performance    |                    |
|     \//     --------------------    |                    |
------------------------------------------------------------
--MimeMultipartBoundary--
From enrico.ferro@elsag.it  Thu Nov 27 00:43:09 1997
From: Enrico Ferro <enrico.ferro@elsag.it>
Date: Thu Nov 27 00:43:12 PST 1997
Subject: How to access WindSurf
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Hi guys,
I am experiencing difficulties in accessing WindSurf: I get to the point
when the two boxes must be checked: after that, it should ask for my
username and password, but instead he keeps repeating the page where the txo
boxes to be checked are, over and over again. The result is, I can't get
through.
I called the support, but they claim this is impossible.
Did any of you ever encounter the same problem?
Enrico
--MimeMultipartBoundary--
From phil.quiney@gecm.com  Thu Nov 27 02:23:18 1997
From: Philip Quiney <phil.quiney@gecm.com>
Date: Thu Nov 27 02:23:22 PST 1997
Subject: Re: How to access WindSurf
Hi Enrico,
Try pointing your browser at this URL. It should bring up the
username/password prompt directly.
http://www.wrs.com/csdocs/surfmenu.html
Regards
Phil Q
> Hi guys,
>
> I am experiencing difficulties in accessing WindSurf: I get to the point
> when the two boxes must be checked: after that, it should ask for my
> username and password, but instead he keeps repeating the page where the txo
> boxes to be checked are, over and over again. The result is, I can't get
> through.
>
> I called the support, but they claim this is impossible.
>
> Did any of you ever encounter the same problem?
>
> Enrico
>
===============================================================================
Phil Quiney          _/_/_/_/        _/  _/_/_/_/  email : phil.quiney@gecm.com
GEC Marconi         _/    _/        _/  _/    _/     tel : +44 1245 353221x3914
Communications Ltd _/_/_/_/  _/    _/  _/  _/_/      fax : +44 1245 275448
Chelmsford        _/        _/_/_/_/  _/_/_/_/
England CM1 1PL                              _/
===============================================================================
From daemon@csg.lbl.gov  Thu Nov 27 04:01:12 1997
From: daemon@csg.lbl.gov
Date: Thu Nov 27 04:01:17 PST 1997
Subject: comp.os.vxworks newsdigest
Comp.Os.Vxworks Daily Digest    Thu Nov 27 04:01:09 PST 1997
        Subject: Re: VxWorks as UNIX?
        Subject: Re: VxWorks as UNIX?
-------------------------------------------------------
Newsgroups: comp.os.vxworks
Subject: Re: VxWorks as UNIX?
Date: 24 Nov 1997 19:23:52 GMT
From: exudpau@exu.ericsson.se (David B. Paul)
Organization: Ericsson North America Inc.
Message-ID: <65ck88$m62@cnn.exu.ericsson.se>
References: <IoSPnda00iWP01p580@andrew.cmu.edu>
Reply-To: exudpau@exu.ericsson.se
In article IoSPnda00iWP01p580@andrew.cmu.edu, Kevin Bradley <kb+@andrew.cmu.edu> writes:
[snip]
>However, it is possible to migrate code between them because
>VxWorks supports the POSIX API, so applications written for
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Ah, thank you for bringing that up.  I've read that VxWorks
supports POSIX 1003.1b Real-Time Extensions, but what about
the rest of POSIX?
[snip]
>                                                    -- Kevin
>
- ---
David B. Paul                |   1010 E. Arapaho Rd, M/S L-04
Product Development          |   Richardson, TX  75081, U.S.A.
Network Systems              |   Phone: (972) 583 5482
Ericsson Inc.                |   mailto:david.b.paul@ericsson.com
---------------------------
Newsgroups: comp.os.vxworks
Subject: Re: VxWorks as UNIX?
Date: Mon, 24 Nov 1997 12:44:09 -0500
From: Kevin Bradley <kb+@andrew.cmu.edu>
Organization: Doctoral student, Electrical and Computer Engineering, Carnegie Mellon, Pittsburgh, PA
Message-ID: <IoSPnda00iWP01p580@andrew.cmu.edu>
References: <65ca0e$id3@cnn.exu.ericsson.se>
Excerpts from netnews.comp.os.vxworks: 24-Nov-97 VxWorks as UNIX? by
David B. Paul@exu.ericss
> Do you consider VxWorks to be a UNIX, or merely
> UNIX-like?  I don't so much want to begin a war regarding
> what constitutes UNIX; mostly, I'm looking for an
> assessment as to how close VxWorks is to OSs that are
> commonly accepted as being "real" UNIX (whatever that is ;-).
I would say "No", given that I know Unix and VxWorks.
VxWorks doesn't act like Unix (no memory protection default,
no dynamic priority, no processes, no notion of user really).
However, it is possible to migrate code between them because
VxWorks supports the POSIX API, so applications written for
Unix can (somewhat) be migrated to VxWorks.  As an example,
the socket interface is the same (externally, anyway).
Remember that VxWorks is intended for an embedded system,
so it's designed to run tasks quickly and properly, usually
in single-user (although multi-threaded) mode.  Unix
is designed to be secure and multi-user, which leads to
very different things.
> Or, to word the issue another way:  If someone says they have
> VxWorks experience, would you say they have UNIX experience?
No.  Unix experience means a different thing than VxWorks experience.
They're similar enough that an expert from one system could
understand the other quickly, as the fundamental principles
are similar enough.  Although I'm not sure about just being
a VxWorks expert and how well you could learn Unix; going the
other way was pretty easy.
                                                    -- Kevin
---------------------------
End of New-News digest
**********************
From Lants30332@aol.com  Fri Nov 28 00:11:00 1997
From: Lants30332@aol.com
Date: Fri Nov 28 00:11:03 PST 1997
Subject: Re:
   The Virtual Girlfriend and Virtual Boyfriend are artificial intelligence
programs for your IBM PC or compatible and also for MACINTOSH. You
can watch them, talk to them, ask them questions, tell them secrets, and
relate with them.  Watch them as you ask them to take off different clothes
and guide them through many different activities. Watch and participate in
the hottest sexual activities available on computer, including: several
sexual positions, using many unique toys, even bringing in multiple partners.
This is no doubt one of the most realistic, sexually stimulating computer
games available. They will remember your name, birthday, your likes and your
dislikes. Every time you start the program, they say different things, and
act differently. Each time, they have a different personality. With the VGA
digital graphics, The Virtual Girlfriend and Virtual Boyfriend software have
some of the hottest, sexiest graphics out there.  And with a Soundblaster or
compatible card, you can actually hear their voice as they talk to you. This
is the first adult software title that was designed for both heterosexual and
homosexual people. I would like you to try the actual full copy out before it
is put on the market.  It will be sold for 1/5 of the actual price ($10.00)
until I can get back some information on what people think of the program.
Please give it a try and write back any comments.      Thank you.
    If you are interested and would like to order a copy, then you can read
the mailing instructions below.  It comes in an unmarked package and is sent
out at most 4 days after the order is received. You are not put on any
mailing lists whatsoever, guaranteed. It will run on any 386, 486 or higher,
and 100% IBM compatibles.  Required is VGA graphics, and a hard drive.
The sound card is optional. Macintosh requires at least 4 meg of ram.
Virtual Girlfriend and Virtual Boyfriend are artificial intelligence
programs, meaning they are completely interactive. It would be just like if
you were talking to someone.  You can actually have simple conversations.
Their attitudes change with the different things you say, so you can say
things that will upset them, and then say things that will please them. The
more you play/talk with them, the more you learn what they can do, and what
they like to do. It really is a blast.  With all these movies coming out
about virtual reality, it's amazing to actually have a virtual reality
program like this for your own computer. It's easy to install, and
instructions are easy to follow.
  ~~~~~~~~~~~~~~~~Special Software Offer~~~~~~~~~~~~~~~~~~
This is to inform you about the new adult game that VCS Magazine
rated "The best game of "97".  "The Search for Paradise is no doubt one
of the greatest XXX adult games available".  The first games where it is
as much fun as it is a turn on!  Travel the world to every continent, every
country you can think of, and meet some of the most beautiful women in
existence.  These women will treat you like a king and obey your every
command.  Any sexual wish you can think of, these women know it all.
There is a different paradise for every guy out there, and this game will
have them all.  This game uses real models, digital video, and digital sound
to make it as realistic as possible.  You will feel like you're in the same
room as the girl you're talking to!!!
          As an added bonus you'll receive "Club Celebrity X"
     Meet, talk to and even have your way with the celebrities of your
choice.
     Imagine being in a club with some very beautiful, well known, actual
     celebrities! You have seen these girls on T.V., Magazines and billboard
ads.
     Now they are on your computer begging for action.  This game is hot and
once you
     start playing, you won't be able to stop!!!
~Required: 386 or better, 4 meg ram or better, Windows 3.1 or higher (Win95
is fine), sound card is optional, Rom is optional.  (Game is given either
CD-rom or compressed 3.5" diskettes).~~$19.95!
                            Order now and get everything for just $24.95!!!!
At your request, the programs can come with a password protection utility
that only allows the program to run when the correct password is entered.
                                   (You must be 18 or over to purchase)
Please fill out the following form and mail it to the address above.
(Feel free to write out the order form by hand)
            -
           Send to:                    Mark Wrhel
                                         P.O. Box 0118
                                      Tujunga, Ca. 91043
Your Name ___________________________________________ Date ____________
Address ______________________________________________________________
City ____________________________ State __________ Zip Code ______________
Phone#  _____________________ E-mail Address ___________________________
Do you have an IBM (   ) or MAC (   )?  CD rom (   ) or Disks (   )?
(   ) Virtual Girdfriend or (   ) Boyfriend for $10.00 (   ) *both just
$15.95
(   ) The Search for Paradise and Club Celebrity X for $19.95
(   ) Everything!!! The Search for Paradise, Club Celebrity X,
      Virtual Girlfriend and Virtual Boyfriend.
       >>>>All for just $24.95<<<<
From daemon@csg.lbl.gov  Fri Nov 28 04:00:26 1997
From: daemon@csg.lbl.gov
Date: Fri Nov 28 04:00:32 PST 1997
Subject: comp.os.vxworks newsdigest
Comp.Os.Vxworks Daily Digest    Fri Nov 28 04:00:23 PST 1997
        Subject: Booting VxWorks
        Subject: Timing out a UDP socket call
-------------------------------------------------------
Newsgroups: comp.os.vxworks
Subject: Booting VxWorks
Date: 24 Nov 1997 13:07:39 -0800
From: beltas <beltas@aludra.usc.edu>
Organization: University of Southern California, Los Angeles, CA
Message-ID: <Pine.SV4.3.94.971124125714.29091A-100000@aludra.usc.edu>
Hi,
I am new in the VxWorks world and I have the following elementary
question.
My company just bought a MVME 167 and I want to use VxWork, version 5.1.1
with it. As far as I understand the way to go is to burn two EPROMs with
the bootrom.hex and replace the existing vendor supplied ROMs with them,
which by the way contain the 167Bug. Am I right or wrong? And if I am
right, do I have to split the bootrom.hex in high and low?
Is there another way to boot VxWorks? For example using 167Bug and BOOTP?
Any help will be really appreciated.
Periklis Beltas
---------------------------
Newsgroups: comp.os.vxworks
Subject: Timing out a UDP socket call
Date: Mon, 24 Nov 1997 16:00:21 -0500
From: Frederick Byrne <fbyrne@motown.lmco.com>
Organization: Lockheed Martin
Message-ID: <3479EAE5.F2226DB5@motown.lmco.com>
Does anyone know of a way (or the preferred way) to time
out a socket call.  I was thinking of doing a non-blocking
socket and use a watchdog timer but how do I cancel the
socket call?  Am I over complicating things?  Thanks in
advance for any help.
- --
==============================================================
The opinions and ideas expressed here are my own (unless they
make money and then they belong to my employer :-)
        Frederick "Rick" Byrne          fbyrne@motown.lmco.com
        Lockheed Martin Government Electronic Systems
---------------------------
End of New-News digest
**********************
From art@iotek.ns.ca  Fri Nov 28 09:06:31 1997
From: Art Cole <art@iotek.ns.ca>
Date: Fri Nov 28 09:06:34 PST 1997
Subject: Creating ROM images for the 2604
--MimeMultipartBoundary
Content-Type: TEXT/PLAIN; charset=US-ASCII
Hi all:
I have been trying unsuccessfully to create a ROM-able image
for the MVME2604 board. I have tried creating both ROM-resident
and non ROM-resident versions of the code, but alas, when the
board is powered up, nothing happens. Knowing that it's quite
easy to waste a lot of time and effort on this without achieving
any success, I decided to see if anyone else out there in VxWorks
land has done this already. Anyone ??
Art Cole
MDA Halifax
phone: (902)-481-3523
fax:   (902)-468-2278
email: art@iotek.ns.ca
--MimeMultipartBoundary--
From mmcquade@aa.net  Fri Nov 28 11:46:55 1997
From: Mike McQuade <mmcquade@aa.net>
Date: Fri Nov 28 11:46:58 PST 1997
Subject: Re: Creating ROM images for the 2604
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
At 09:06 AM 11/28/97 PST, you wrote:
>Submitted-by art@iotek.ns.ca  Fri Nov 28 09:06:31 1997
>Submitted-by: Art Cole <art@iotek.ns.ca>
>I have been trying unsuccessfully to create a ROM-able image
>for the MVME2604 board. I have tried creating both ROM-resident
>and non ROM-resident versions of the code, but alas, when the
>board is powered up, nothing happens. Knowing that it's quite
>easy to waste a lot of time and effort on this without achieving
>any success, I decided to see if anyone else out there in VxWorks
>land has done this already. Anyone ??
>
Art,
Ive been doing this on a 2603 for sometime, the PowerPC boots up
in about 5 to 6 seconds from ROM (FLASH), much nicer than net booting.
Here are the steps:
1. (optional) add your app to MACH_EXTRA.
2. Make vxWorks_rom
3. elfToBin <vxWorks_rom> arts_vx_rom
4. use Moto PPC BUG to put the new image (arts_vx_rom) into Flash.
(send me email if you need instructions for PPC-BUG).
Note:
The other variations of ROM-resident didn't work for us.
I worte some code that programs the 4Mb flash from VxWorks, we
FTP our new application (vxWorks_rom + our_application) into a
RAM disk, from there, we use our own routine to program the
flash rom.
An easier way was needed for customers that need to update the
Firmware in the field.
Let me know if you are interested in doing something like this,
I can get you pointed into the right direction.
Mike.
--MimeMultipartBoundary--
From daemon@csg.lbl.gov  Sat Nov 29 04:00:41 1997
From: daemon@csg.lbl.gov
Date: Sat Nov 29 04:00:45 PST 1997
Subject: comp.os.vxworks newsdigest
Comp.Os.Vxworks Daily Digest    Sat Nov 29 04:00:37 PST 1997
        Subject: Re: Re-hosing of RISC Watch
        Subject: Re: Q: Very strange behaviour of sprintf. Any hints?
-------------------------------------------------------
Newsgroups: comp.os.vxworks
Subject: Re: Re-hosing of RISC Watch
Date: 25 Nov 1997 03:21:59 GMT
From: mda@bnr.ca (Mark Dapoz)
Organization: Bell-Northern Research Ltd.
Message-ID: <65dg8n$lt4@bcarh8ab.bnr.ca>
References: <19971124191345241@ix.netcom.com>
In article <19971124191345241@ix.netcom.com>,  <ratkin@ix.netcom.com> wrote:
>--MimeMultipartBoundary
>>     I am currently hosting a RISCWatch on an OLD IBM-AIX box.  I would
>>     like to re-host on a newer system (preferably a Solaris based system).
>>     Any advice?
>I don't think you can host the RISCWatch on anything but an IBM micro-channel
>based machine running AIX 3.2.x (x = 3,4, or 5).
If you have the old microchannel based JTAG controller, then yes, you're SOL.
However, if you're using the newer ethernet based JTAG controller then you
can easily re-host it on a SPARC running Solaris.  You just need to buy the
Solaris version of the software.
			-mark
- --
Mark Dapoz	Bell-Northern Research, Ottawa, Canada	    Mark.Dapoz@bnr.ca
Fingers and toes, fingers and toes, forty things we share, forty one if you
include the fact that we don't care.  - The Tragically Hip
---------------------------
Newsgroups: comp.os.vxworks
Subject: Re: Q: Very strange behaviour of sprintf. Any hints?
Date: 29 Nov 1997 01:46:16 -0800
From: Martin Shepherd <mcs@goblin.caltech.edu>
Organization: California Institute of Technology.
Message-ID: <yc9ra80ghhz.fsf@goblin.caltech.edu>
References: <65120o$12b$1@news.rwth-aachen.de> <65g185$63r@lotho.delphi.com>
	<yc93ekkszmc.fsf@goblin.caltech.edu> <65k7d8$1j6@lotho.delphi.com>
jodle@bix.com (jodle) writes:
> Martin Shepherd (mcs@goblin.caltech.edu) wrote:
>
> : Printf is expecting 8 bytes to go with %f, so this isn't the problem.
 [material omitted]
> : 1. Make sure that stdio.h is included. The absence of a prototype for
> :    printf could well cause strange behavior on some systems.
>
> Strange behavior such as warnings that there is no prototype for
> printf.
It could be much more insidious than that. The Standard requires that
calls to functions taking a variable number of arguments must occur in
the presence of a prototype. This allows implementations to use
different argument passing methods for variadic functions than for
normal functions. As a result, on some systems, unexpected things will
happen if printf() is used without having included stdio.h.
> I want to believe (and assumed) that he eliminated all such warnings
> before posting the question,
Hopefully true, but the poster may not have had the relevant warnings
enabled.
> but omitting the prototype for printf would
> seem consistent with the described behavior.  Without the printf
> declaration, wouldn't each float be stacked as a doubleword rather than a
> quadword, leading to printf wandering outside the stack frame looking for
> arguments?
No, in the absence of function prototypes, C compilers are required to
widen float arguments to double; char and short arguments to int, etc...
This is a holdover from the way that C worked before the standard
introduced function prototypes.
Martin Shepherd  (mcs@astro.caltech.edu)
---------------------------
End of New-News digest
**********************
From jshaw_shade@compuserve.com  Sat Nov 29 08:31:45 1997
From: John Shaw <jshaw_shade@compuserve.com>
Date: Sat Nov 29 08:31:48 PST 1997
Subject: Re: comp.os.vxworks newsdigest
--MimeMultipartBoundary
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
Regarding the message:-
> Subject: Timing out a UDP socket call
> From: Frederick Byrne <fbyrne@motown.lmco.com>
> Does anyone know of a way (or the preferred way) to time
> out a socket call.  I was thinking of doing a non-blocking
> socket and use a watchdog timer but how do I cancel the
> socket call?  Am I over complicating things?  Thanks in
> advance for any help.
If socket calls are non-blocking, you won't have a problem
because calls will succeed immediately or fail with an error
to indicate that there is no data or no pending events.
You could use a blocking call, to say read data, on a socket
employing UDP. The calling task would block and your watchdog
timer interrupt routine could close the socket to terminate
the pending read. The socket would then have to be reopened.
You could use a select call on the socket. If an event occurs
on the socket, the select call will return successfully. After
determining the cause of the event by a one-off poll, you could
use a blocking socket call to handle the event (eg. read data).
The select function can be given a timeout so that it returns
with an error if no events have occurred within the prescribed
period.
Hope this is helpful.
John Shaw
Shade (Computer Services) Ltd., Calne, Wiltshire, England, UK.
Email: jshaw_shade@compuserve.com=
--MimeMultipartBoundary--
From Elec-98@goplay.com  Sun Nov 30 03:49:11 1997
From: Elec-98@goplay.com
Date: Sun Nov 30 03:49:14 PST 1997
Subject: Profits With POWER!!!
************************************************************************************************
 There is a Awesome Opportunity in the exciting Utilities field if you just take 2 minutes to read the following NEW NEWS!.
 (Removal Instructions Below)
 ----------------------------------------------------
 ELECTRIC POWER DEREGULATED!
 Monumental Breakthrough!  The first Network
 Marketing company in the Nation to offer Discounted
 Electric Power!!  Tremendous Profit Potential!!!!
 -----------------------------------------------------
 You can be the first in your Zip Code, County or even State, to offer
 Electric Power to your customers with savings up to 40% and earn a
 substantial income at the same time!
 How would you have liked to have been one of the first people in Excel
 after Long Distance was first deregulated.  Excel Reps made a fortune!
 You have the same Ground Floor Opportunity IF YOU ACT FAST.
 This program is only weeks old!
 Electricity is deregulating in all 50 states starting with CA in Jan.  What
 this means for the consumer is the same electric company would read the
 meter, service the lines, the same truck with the same logo would pull up to
 the house.  The only difference the consumer would see is paying their bill
 to another company and a reduced bill.
 We will be able to offer the customer a 20-40% off their electric generation!!
 This is a once-in-a lifetime opportunity for those who act
 today!  We wish you the best of  Success for 1998 and
 beyond!
 For Further Details Please Reply To :
  <a href="mailto:Elec-98@goplay.com?subject=More Info">  Elec98@gopay.com</a>,
 Or visit
<a href="http://www.cybernet5/Elec98.html">http://www.cybernet5.com/Elec98.html
</a>
 To be removed from this list and many others,
 Send request to : <A HREF="mailto:remove@olma.net">remove@olma.net</a>
From daemon@csg.lbl.gov  Sun Nov 30 04:00:56 1997
From: daemon@csg.lbl.gov
Date: Sun Nov 30 04:01:00 PST 1997
Subject: comp.os.vxworks newsdigest
Comp.Os.Vxworks Daily Digest    Sun Nov 30 04:00:52 PST 1997
        Subject: fmod problems.
        Subject:  Who sells PMC w/ Generic Parallel Port
        Subject: Re: Q: Very strange behaviour of sprintf. Any hints?
        Subject: stdio redirection
        Subject: Re: Q: Very strange behaviour of sprintf. Any hints?
-------------------------------------------------------
Newsgroups: comp.os.vxworks
Subject: fmod problems.
Date: Tue, 25 Nov 1997 09:36:57 -0500
From: Vince Banes <avbosc@www710.gsfc.nasa.REMOVE.gov>
Organization: NASA Goddard Space Flight Center -- Greenbelt, Maryland USA
Message-ID: <347AE289.28DD@www710.gsfc.nasa.REMOVE.gov>
We are using a MV2603 PowerPC board with Tornado 1.0.1.  Nothing fancy.
The basic BSP kernal has the floating point and math extension included.
The following code works:
//////////////////////////////////////////
double  f = 12345.67;
double  m = 10.0;
double  r = fmod(f,m);
//////////////////////////////////////////
The next chuck of code causes the system to lock up.  The only
differance is the size of the first value for fmod().
//////////////////////////////////////////
double  f = 12345123451234512345.67;
double  m = 10.0;
double  r = fmod(f,m);
//////////////////////////////////////////
It seems to take a long time (10's of seconds) to do the computation
if the first value is large.
Any ideas where to look?
- --
Vince Banes
email really is = <avbosc@rs712b.gsfc.nasa.NOSPAM>
if you change NOSPAM to gov
---------------------------
Newsgroups: comp.os.vxworks
Subject:  Who sells PMC w/ Generic Parallel Port
Date: 25 Nov 1997 17:52:26 GMT
From: lsrsearch@aol.com (LSRsearch)
Organization: AOL http://www.aol.com
Message-ID: <19971125175201.MAA17443@ladder02.news.aol.com>
 Who sells PMC w/ Generic Parallel Port?  Please refer me to vendors.
Thankyou,
Lisa Solomon
LSRsearch@aol.com
---------------------------
Newsgroups: comp.os.vxworks
Subject: Re: Q: Very strange behaviour of sprintf. Any hints?
Date: 29 Nov 1997 18:23:29 GMT
From: jodle@bix.com (jodle)
Organization: BIX
Message-ID: <65pmj1$lbd@lotho.delphi.com>
References: <65120o$12b$1@news.rwth-aachen.de> <65g185$63r@lotho.delphi.com> <yc9ra80ghhz.fsf@goblin.caltech.edu>
Martin Shepherd (mcs@goblin.caltech.edu) wrote:
: It could be much more insidious than that. The Standard requires that
: calls to functions taking a variable number of arguments must occur in
: the presence of a prototype. This allows implementations to use
: different argument passing methods for variadic functions than for
: normal functions. As a result, on some systems, unexpected things will
: happen if printf() is used without having included stdio.h.
: Hopefully true, but the poster may not have had the relevant warnings
: enabled.
Same difference!
: No, in the absence of function prototypes, C compilers are required to
: widen float arguments to double; char and short arguments to int, etc...
: This is a holdover from the way that C worked before the standard
: introduced function prototypes.
He was passing doubles, not floats.  You said in a previous posting that
%f assumes doubles were passed.  That is, the same scheme is used for
variable argument lists as for unprototyped parameters. Therefore, it
seems the printf call should be working with or without the prototype, no?
What did I miss?
---------------------------
Newsgroups: comp.os.vxworks
Subject: stdio redirection
Date: 25 Nov 1997 15:06:42 -0500
From: Tom Emerson <tree@spyglass.com>
Organization: Spyglass, Inc.
Message-ID: <0xhg90sppp.fsf@nigiri.cam.spyglass.com>
I'm using Tornado 1.0.1 on VxWorks 5.3.1 with the PC 486 BSP, and have
a question about StdIO redirection.
I'm writing unit tests for individual components in our system. The
test driver (which was first written on Solaris) takes the test data
from standard input and writes its output to standard output.
This isn't working on VxWorks: if I invoke the test's entry point in
the shell,
- -> ld < testdriver.o
- -> parsetest() < test.msg
hangs at the point where the driver starts trying to read from stdin
(essentially "fgetc(stdin)"). The file "test.msg" is in the same
directory on the host as "testdriver.o".
My next attempt was to open a file descriptor to the test file and
then make this the standard input with ioGlobalStdSet. That doesn't
work though,
- -> fd = open("test.msg",0,0)
returns -1 and "permission denied" is written to the console. Well,
since test.msg doesn't exist on the target this isn't going to work,
right? I don't want to rely on NFS here either (this was the point of
using stdin in the first place).
So now I'm stuck. Does anyone have a suggestion on how this should be
done? Is my only alternative to rely on NFS during testing?
Thanks in advance,
    -tre
---------------------------
Newsgroups: comp.os.vxworks
Subject: Re: Q: Very strange behaviour of sprintf. Any hints?
Date: 29 Nov 1997 21:17:34 -0800
From: Martin Shepherd <mcs@goblin.caltech.edu>
Organization: California Institute of Technology.
Message-ID: <yc9pvnjq7td.fsf@goblin.caltech.edu>
References: <65120o$12b$1@news.rwth-aachen.de> <65g185$63r@lotho.delphi.com>
	<yc9ra80ghhz.fsf@goblin.caltech.edu> <65pmj1$lbd@lotho.delphi.com>
jodle@bix.com (jodle) writes:
> Martin Shepherd (mcs@goblin.caltech.edu) wrote:
> : It could be much more insidious than that. The Standard requires that
> : calls to functions taking a variable number of arguments must occur in
> : the presence of a prototype. This allows implementations to use
> : different argument passing methods for variadic functions than for
> : normal functions.
> :...
In the above, when I said "different argument passing methods" I
wasn't referring to whether arguments are widened or not, I was
referring to the actual mechanics of passing arguments to
functions. For example, a hypothetical implementation might use a
predetermined number of registers to pass arguments to normal
functions, but switch to copying arguments into variable-sized
activation frames when passing arguments to variadic functions like
printf. On such a system, if the prototype of a variadic function
wasn't in scope, the compiler would place arguments in registers
instead of into an activation frame. At best printf would then print
values left in the activation frame by a previous function activation.
> ...
> variable argument lists as for unprototyped parameters. Therefore, it
> seems the printf call should be working with or without the prototype, no?
>
> What did I miss?
See above.
We've gone off topic, so please direct followups to E-mail.
Martin Shepherd  (mcs@astro.caltech.edu)
---------------------------
End of New-News digest
**********************