ntk()".
How could printf() from an ISR work at all, let alone seem to work well? The
"logtxt()" was only to the console, maybe that's why.
Also, is there an equivalent to the VxWorks "in_isr()" for a simple-minded
"logtxt()" that switches between prin
is stored on the media.
I expect that's why the open group document specifies in the "RATIONALE"
section that the conformance document should identify a way to identify how a
file can be created in a manner that "fsync()" and "fdatasync()" are likely to
work.
users@rtems.org
> > http://lists.rtems.org/mailman/listinfo/users
> >
>
> ___
> users mailing list
> users@rtems.org
> http://lists.rtems.org/mailman/listinfo/users
> ___
> us
changes
I put in;
- Drop the changes I made that on that branch in the other branches, e.g
mvme5500-final, atsam-fixes etc so that those branches are now based on
origin/master and only have the changes related to what I was working on.
Any advice?
Peter
-
Peter Dufault
HD
ion
0xdaf1c[ 4]: long (*)()
_bfd_elf_slurp_version_tables
USER VARIABLES:
0x (0)
cexp_main>printf("%s\n",(char *)&_RTEMS_version)
rtems-4.7.1(PowerPC/PowerPC 7455/beatnik)
0x002a (42)
cexp_main>
-
- Do you have the sou
sers who are working on RTEMS can't work
in a VM running CentOS, and how many don't have a machine that allows that?
Let me know if I'm wrong.
This is different from e.g. mingw support, where I think the tools need to work
as plug-ins.
Peter
-
Peter Dufault
HD Asso
bH
>
> Address : Dornierstr. 4, D-82178 Puchheim, Germany
> Phone : +49 89 189 47 41-16
> Fax : +49 89 189 47 41-09
> E-Mail : sebastian.hu...@embedded-brains.de
> PGP : Public key available on request.
>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG
