--- /usr/local/epics/R3.14.12/base/src/RTEMS/base/rtems_init.c 2010-11-24 12:54:36.000000000 -0800 +++ rtems_init.c 2010-12-09 09:18:34.270548000 -0800 @@ -209,7 +209,15 @@ { #ifdef OMIT_NFS_SUPPORT printf ("***** Initializing TFTP *****\n"); +#if __RTEMS_MAJOR__>4 || (__RTEMS_MAJOR__==4 && __RTEMS_MINOR__>9) || (__RTEMS_MAJOR__==4 && __RTEMS_MINOR__==9 && __RTEMS_REVISION__==99) + mount_and_make_target_path(NULL, + "/TFTP", + RTEMS_FILESYSTEM_TYPE_TFTPFS, + RTEMS_FILESYSTEM_READ_WRITE, + NULL); +#else rtems_bsdnet_initialize_tftp_filesystem (); +#endif if (!hasLocalFilesystem) { char *path; int pathsize = 200;
On Dec 9, 2010, at 9:06 AM, Daron Chabot wrote: Hi Jim,
Have a look at tftpTest/init.c from the RTEMS network-demos (cvs HEAD):
cvs -d :pserver:[email protected]:/usr1/CVS co network-demos
It looks like the new initialization steps are:
rtems_bsdnet_initialize_network ();
mount_and_make_target_path( NULL, "/TFTP", RTEMS_FILESYSTEM_TYPE_TFTPFS, RTEMS_FILESYSTEM_READ_WRITE, NULL
);
Patches to Base welcome :-)
-- dc
On Thu, Dec 9, 2010 at 11:26 AM, Jim Chen <[email protected]> wrote:
Eric,
It seems like that rtems-4.10 has changed some function prototypes in
tftpDriver.c code such as rtems_bsdnet_initialize_tftp_filesystem (doesn't
exist anymore) which fails the build of EPICS3.14.11/12 that doesn't use NFS
(with OMIT_NFS_SUPPORT defined). Is there a particular reason for this and
how can I get around with this please?
Best regards,
Jim
Hytec Electronics Ltd.
Tel: +44 (0) 118 975 7770
Fax: +44 (0) 118 975 7566
Web: www.hytec-electronics.co.uk
Incorporated in England No 1246940
VAT NO GB 285 2479 27
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
|