search for: byteorder

The inet stuff is including, asm/byteorder.h It has some inlines like this: static __inline__ __attribute_const__ __u64 ___arch__swab64(__u64 val) I think I'm choking on the __attribue_const__ Do we need an include of linux/compiler.h somewhere? ../linux/include/asm/byteorder.h:28: error: syntax error before "__u64"compil...

tree: git://github.com/ablock84/linux-btrfs.git btrfs-far head: f9a5bb450a8cc7aa5fd4f11d0306b3f48cf2771d commit: 29aefeaaf482ab396ff53c2bbf5c35ce237b91c0 [19/20] fs: add libfarstream support config: make ARCH=s390 allmodconfig All error/warnings: In file included from include/linux/byteorder/big_endian.h:4:0, from arch/s390/include/uapi/asm/byteorder.h:4, from include/asm-generic/bitops/le.h:5, from arch/s390/include/asm/bitops.h:829, from include/linux/bitops.h:22, from include/linux/kernel.h:10,...

...iler-rt/ -- The C compiler identification is Clang -- Check for working C compiler: /home/jocke/llvm/build/Release/bin/clang -- Check for working C compiler: /home/jocke/llvm/build/Release/bin/clang -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Looking for sys/byteorder.h -- Looking for sys/byteorder.h - not found -- Looking for AvailabilityMacros.h -- Looking for AvailabilityMacros.h - not found -- Looking for TargetConditionals.h -- Looking for TargetConditionals.h - not found -- Looking for libkern/OSAtomic.h -- Looking for libkern/OSAtomic.h - not found -- Loo...

Now that 2.6.9 is final. Here is an update of the iproute2 utilities that contains all the patches in my queue. * lnstat to replace rtstat and ctstat (from Harald Welte) * latest xfrm related changes * several small typo''s and build fixes for older systems http://developer.osdl.org/dev/iproute2/download/iproute2-2.6.9-041019.tar.gz

v173 doesn't build on current 2.6 Linus BK on x86 Complaints about undeclared __le64, __le32, __be64, __be32, __be16 What am I doing wrong? In file included from ../linux/include/asm/byteorder.h:57, from ../klibc/include/endian.h:9, from ../klibc/include/netinet/in.h:13, from ../klibc/include/arpa/inet.h:11, from inet/inet_ntoa.c:5: ../linux/include/linux/byteorder/little_endian.h:43: error: syntax error before "__c...

The __constant_htons and similar are defined in klibc version of netinet/in.h, but not in glibc counterpart. Include the same thing from <asm/byteorder.h>, which is available in both glibc and klibc. Perhaps __constant_htons should be dropped from the klibc version of netinet/in.h: it provides nothing that you cannot get via asm/byteorder, and gets in the way of porting between glibc and klibc. Signed-off-by: Erik van Konijnenburg <ekonijn...

https://bugzilla.netfilter.org/show_bug.cgi?id=1253 Bug ID: 1253 Summary: interface wildcard in variables causes Error: Byteorder mismatch: expected big endian, got host endian Product: nftables Version: unspecified Hardware: x86_64 OS: All Status: NEW Severity: normal Priority: P5 Component: nft Assignee: pa...

...core/resources.c:52:44: error: empty scalar initializer 52 | u32 out[MLX5_ST_SZ_DW(create_uctx_out)] = {}; | ^ drivers/vdpa/mlx5/core/resources.c:52:44: note: (near initialization for 'out') In file included from include/linux/byteorder/big_endian.h:5, from arch/mips/include/uapi/asm/byteorder.h:13, from arch/mips/include/asm/bitops.h:20, from include/linux/bitops.h:29, from include/linux/kernel.h:12, from include/linux/mlx5/driver....

...ude ../include-glibc/glibc-bugs.h -I/usr/src/linux/include -I../include -DRESOLVE_HOSTNAMES -c -o ll_map.o ll_map.c In file included from /usr/src/linux/include/linux/in.h:241, from ../include-glibc/netinet/in.h:7, from ll_map.c:19: /usr/src/linux/include/asm/byteorder.h:14: error: syntax error before "__u32" /usr/src/linux/include/asm/byteorder.h:28: error: syntax error before "__u64" In file included from /usr/src/linux/include/linux/byteorder/little_endian.h:11, from /usr/src/linux/include/asm/byteorder.h:57,...

Compile issues on an older BSD/OS 4.2 system: src/lib/byteorder.h needs #include <netinet/in.h> to pick up in_addr struct src/lib/byteorder.c no "libgen" here (no basename()). Added it inline, no big deal, but you might want to have configure test for this and provide one if it's missing. Also, on this system there are no types...

...| ^~~~~~~~~~~~~~~~~~ include/uapi/linux/swab.h:115:54: note: in definition of macro '__swab32' 115 | #define __swab32(x) (__u32)__builtin_bswap32((__u32)(x)) | ^ include/linux/byteorder/generic.h:94:21: note: in expansion of macro '__cpu_to_be32' 94 | #define cpu_to_be32 __cpu_to_be32 | ^~~~~~~~~~~~~ include/linux/stddef.h:17:32: note: in expansion of macro '__compiler_offsetof' 17 | #define offsetof(TYPE, MEMBER) __compi...

Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/bochs/bochs_mm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/bochs/bochs_mm.c b/drivers/gpu/drm/bochs/bochs_mm.c index 857755ac2d..781d35bdff 100644 --- a/drivers/gpu/drm/bochs/bochs_mm.c +++ b/drivers/gpu/drm/bochs/bochs_mm.c @@ -508,7 +508,7 @@

While wading through the code I've noticed we have a little issue in virtio: We attach a format to the bo when it is created (DRM_IOCTL_MODE_CREATE_DUMB), not when we map it as framebuffer (DRM_IOCTL_MODE_ADDFB). Easy way out: support a single format only. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/virtio/virtgpu_gem.c | 5 ++++-

Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/virtio/virtgpu_gem.c | 2 +- drivers/gpu/drm/virtio/virtgpu_plane.c | 31 ------------------------------- 2 files changed, 1 insertion(+), 32 deletions(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_gem.c b/drivers/gpu/drm/virtio/virtgpu_gem.c index cc025d8fbe..4f2c2dc731 100644 ---

Be consistent with the rest of the code base. No functional change. In theory this change is incompatible on bigendian machines, but in practice 3d acceleration is supported only on little endian machines, so the affected code paths never run on bigendian machines. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/virtio/virtgpu_vq.c | 14 ++++++++++++-- 1 file

Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/bochs/bochs_mm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/bochs/bochs_mm.c b/drivers/gpu/drm/bochs/bochs_mm.c index 857755ac2d..781d35bdff 100644 --- a/drivers/gpu/drm/bochs/bochs_mm.c +++ b/drivers/gpu/drm/bochs/bochs_mm.c @@ -508,7 +508,7 @@

While wading through the code I've noticed we have a little issue in virtio: We attach a format to the bo when it is created (DRM_IOCTL_MODE_CREATE_DUMB), not when we map it as framebuffer (DRM_IOCTL_MODE_ADDFB). Easy way out: support a single format only. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/virtio/virtgpu_gem.c | 5 ++++-

Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/virtio/virtgpu_gem.c | 2 +- drivers/gpu/drm/virtio/virtgpu_plane.c | 31 ------------------------------- 2 files changed, 1 insertion(+), 32 deletions(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_gem.c b/drivers/gpu/drm/virtio/virtgpu_gem.c index cc025d8fbe..4f2c2dc731 100644 ---

Be consistent with the rest of the code base. No functional change. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/virtio/virtgpu_drv.h | 4 ++-- drivers/gpu/drm/virtio/virtgpu_plane.c | 12 ++++++------ drivers/gpu/drm/virtio/virtgpu_vq.c | 12 ++++++------ 3 files changed, 14 insertions(+), 14 deletions(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_drv.h

Add bochs_hw_set_*_endian() helper functions, to set the framebuffer byteorder at mode set time. Support both DRM_FORMAT_XRGB8888 and DRM_FORMAT_BGRX8888 framebuffer formats, no matter what the native machine byte order is. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/bochs/bochs.h | 4 ++- drivers/gpu/drm/bochs/bochs_fbdev.c | 3 +-...