public inbox for
help / color / mirror / Atom feed
From: Sebastian Huber <>
Subject: [newlib-cygwin] RTEMS: Introduce <machine/_kernel_uio.h>
Date: Fri, 24 Aug 2018 13:12:00 -0000	[thread overview]
Message-ID: <> (raw);h=c07fa084e023d897996b65f76aa1f1251dcb3f16

commit c07fa084e023d897996b65f76aa1f1251dcb3f16
Author: Sebastian Huber <>
Date:   Tue Aug 7 15:35:37 2018 +0200

    RTEMS: Introduce <machine/_kernel_uio.h>
    This helps to avoid Newlib updates due to FreeBSD kernel space changes.
    Signed-off-by: Sebastian Huber <>

 newlib/libc/sys/rtems/include/sys/uio.h | 60 ++++-----------------------------
 1 file changed, 6 insertions(+), 54 deletions(-)

diff --git a/newlib/libc/sys/rtems/include/sys/uio.h b/newlib/libc/sys/rtems/include/sys/uio.h
index 4aff08e..38d5ba9 100644
--- a/newlib/libc/sys/rtems/include/sys/uio.h
+++ b/newlib/libc/sys/rtems/include/sys/uio.h
@@ -50,59 +50,7 @@ typedef	__off_t	off_t;
 #define	_OFF_T_DECLARED
-#ifdef _KERNEL
-struct uio {
-	struct	iovec *uio_iov;		/* scatter/gather list */
-	int	uio_iovcnt;		/* length of scatter/gather list */
-	off_t	uio_offset;		/* offset in target object */
-	ssize_t	uio_resid;		/* remaining bytes to process */
-	enum	uio_seg uio_segflg;	/* address space */
-	enum	uio_rw uio_rw;		/* operation */
-	struct	thread *uio_td;		/* owner */
- * Limits
- *
- * N.B.: UIO_MAXIOV must be no less than IOV_MAX from <sys/syslimits.h>
- * which in turn must be no less than _XOPEN_IOV_MAX from <limits.h>.  If
- * we ever make this tunable (probably pointless), then IOV_MAX should be
- * removed from <sys/syslimits.h> and applications would be expected to use
- * sysconf(3) to find out the correct value, or else assume the worst
- * (_XOPEN_IOV_MAX).  Perhaps UIO_MAXIOV should be simply defined as
- * IOV_MAX.
- */
-#define UIO_MAXIOV	1024		/* max 1K of iov's */
-struct vm_object;
-struct vm_page;
-struct bus_dma_segment;
-struct uio *cloneuio(struct uio *uiop);
-int	copyinfrom(const void * __restrict src, void * __restrict dst,
-	    size_t len, int seg);
-int	copyiniov(const struct iovec *iovp, u_int iovcnt, struct iovec **iov,
-	    int error);
-int	copyinstrfrom(const void * __restrict src, void * __restrict dst,
-	    size_t len, size_t * __restrict copied, int seg);
-int	copyinuio(const struct iovec *iovp, u_int iovcnt, struct uio **uiop);
-int	copyout_map(struct thread *td, vm_offset_t *addr, size_t sz);
-int	copyout_unmap(struct thread *td, vm_offset_t addr, size_t sz);
-int	physcopyin(void *src, vm_paddr_t dst, size_t len);
-int	physcopyout(vm_paddr_t src, void *dst, size_t len);
-int	physcopyin_vlist(struct bus_dma_segment *src, off_t offset,
-	    vm_paddr_t dst, size_t len);
-int	physcopyout_vlist(vm_paddr_t src, struct bus_dma_segment *dst,
-	    off_t offset, size_t len);
-int	uiomove(void *cp, int n, struct uio *uio);
-int	uiomove_frombuf(void *buf, int buflen, struct uio *uio);
-int	uiomove_fromphys(struct vm_page *ma[], vm_offset_t offset, int n,
-	    struct uio *uio);
-int	uiomove_nofault(void *cp, int n, struct uio *uio);
-int	uiomove_object(struct vm_object *obj, off_t obj_size, struct uio *uio);
-#else /* !_KERNEL */
+#ifndef _KERNEL
 ssize_t	readv(int, const struct iovec *, int);
@@ -113,6 +61,10 @@ ssize_t	pwritev(int, const struct iovec *, int, off_t);
-#endif /* _KERNEL */
+#endif /* !_KERNEL */
+#ifdef _KERNEL
+/* Header file provided outside of Newlib */
+#include <machine/_kernel_uio.h>
 #endif /* !_SYS_UIO_H_ */

                 reply	other threads:[~2018-08-24 13:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).