Displaying 13 results from an estimated 13 matches for "be32".
Did you mean:
b32
2016 May 18
2
BE8 elf format on gold
Hi Guys ,
We are trying to enable LTO on our code base for clang(3.8) using
gold linker , and we are stuck with below error
bash-4.1$ /arm-install/bin/armeb-linux-gnueabi-ld.gold --be8
/arm-install/bin/armeb-linux-gnueabi-ld.gold: --be8: unknown option
And found that ,Be8 (byte invariant addressing) is not supported in
the gold linker,
Questions is ,how do we go from here ?
Do be8
2016 Oct 28
3
[cfe-dev] Using lld in ELLCC for different targets
...e:
> Awesome results!
I'm surprised! LLD is barely working on ARM at the moment. :)
> I wonder if ARM32 BE is a real thing. I know that the processor is
> bi-endian, but is there any system that uses ARM32 in big-endian mode?
Yes... it is "a thing". :)
ARM has two modes: BE32 and BE8 (mixed) and they can be enabled via
CP15 registers.
http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0290g/ch06s05s01.html
cheers,
--renato
2013 Dec 09
0
Gluster - replica - Unable to self-heal contents of '/' (possible split-brain)
...luster/stor1
[root@blade6 stor1]# pwd
/gluster/stor1
[root@blade6 stor1]# ls -lh
total 0
[root@blade7 stor1]# pwd
/gluster/stor1
[root@blade7 stor1]# ls -lh
total 0
[root@blade6 stor1]# gluster volume info
Volume Name: stor_fast
Type: Distribute
Volume ID: ad82b554-8ff0-4903-be32-f8dcb9420f31
Status: Started
Number of Bricks: 1
Transport-type: tcp
Bricks:
Brick1: blade7.xen:/gluster/stor_fast
Options Reconfigured:
nfs.port: 2049
Volume Name: stor1
Type: Replicate
Volume ID: 6bd88164-86c2-40f6-9846-b21e90303e73
Status: Started
Number of Bricks: 1 x 2 = 2
Tran...
2023 Mar 01
6
[libnbd PATCH 0/6] common: catch up with nbdkit
If we compare the "common" subdirectory between nbdkit @ 6b4178d0fdfe
("ci: Temporarily disable perl in MacOS", 2023-02-27) and libnbd @
d05cd8f384a7 ("Version 1.15.11.", 2023-02-28), we find differences. We
can categorize these differences along two (orthogonal) axes:
- Intentional or unintentional.
Intentional differences are for example when one of the libnbd
2014 Feb 17
0
Custom policy executable
...re subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/30d1d249-b648-4eb2-be32-1578f6118705%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
2016 Oct 28
0
[cfe-dev] Using lld in ELLCC for different targets
On Fri, Oct 28, 2016 at 2:56 PM, Richard Pennington via cfe-dev <
cfe-dev at lists.llvm.org> wrote:
> With all the talk about using lld on the list, I thought it would be
> interesting to try using it in my clang based ELLCC cross compilation tool
> chain. http://ellcc.org
>
> The change was simple, since I use configuration files to tell clang how
> to compile, where to
2012 Nov 20
52
[PATCH RFC] stubdom: Change vTPM shared page ABI
Since the vTPM implementations are being incorproated into Xen and
possibly upstream Linux, I would like to see if this protocol change
could be added before we have significant legacy implementations. If
not, I still think it would be useful as either a v2 or negotiated
protocol change.
The current vTPM protocol is a copy of the network protocol. This was
likely done for ease of implementation,
2014 Mar 25
0
[PATCH 4/4] vbios/prom: fetch the vbios using only aligned 32-bit accesses
...mage to system memory */
> - bios->size = nv_rd08(bios, 0x300002) * 512;
> + bios->size = ((nv_rd32(bios, 0x300000) >> 16) & 0xff) * 512;
You already read this out once, might as well save it. BTW, is CPU
endianness affected here? i.e. does nv_rd32 do a le32 -> be32
conversion on a be cpu? I would assume it must since everything
assumes that 32-bit reads read in integer values... but then your
logic is all wrong, since the bytes are laid out in a different order
on be.
> if (!bios->size)
> goto out;
>
> bios->...
2014 Mar 25
2
[PATCH 4/4] vbios/prom: fetch the vbios using only aligned 32-bit accesses
Other kind of accesses are unreliable on Maxwell cards. As advised by NVIDIA,
let's only use 32-bit accesses to fetch the vbios from PROM.
This fixes vbios fetching on my nve7 which failed in certain specific
conditions.
I suggest we Cc stable, for all kernels they still maintain after the big
rewrite.
Suggested-by: Christian Zander <czander at nvidia.com>
Signed-off-by: Martin Peres
2013 Nov 19
23
[PATCH v6 00/16] xen: arm: 64-bit guest support and domU FDT autogeneration
Biggest change is to switch the new DTB node to /xen-core-devices
instead of /xen at Stefano''s request.
I also dropped the few patches title HACK etc which weren''t supposed to
be there and fixed up some bits and pieces which folks commented on.
George, WRT the freeze I think this is functionality which we cannot
ship Xen 4.4 without. The impact is entirely constrained to the
2013 Apr 16
1
update config.guess and config.sub to support aarch64
Hello,
would it be possible to update config.sub and config.guess to the latest versions (or at least version
from automake-1.13.1) in order to support new architectures based on the ARM 64 bit CPU?
Patch: http://plautrba.fedorapeople.org/openssh/openssh-latest-config.sub-config.guess.patch
Related Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=926284
Thanks,
Petr
2023 May 09
5
[Bridge] [RFC PATCH net-next 0/5] Add layer 2 miss indication and filtering
tl;dr
=====
This patchset adds a single bit to the skb to indicate that a packet
encountered a layer 2 miss in the bridge and extends flower to match on
this metadata. This is required for non-DF (Designated Forwarder)
filtering in EVPN multi-homing which prevents decapsulated BUM packets
from being forwarded multiple times to the same multi-homed host.
Background
==========
In a typical EVPN
2023 May 18
5
[Bridge] [PATCH net-next 0/5] Add layer 2 miss indication and filtering
tl;dr
=====
This patchset adds a single bit to the skb to indicate that a packet
encountered a layer 2 miss in the bridge and extends flower to match on
this metadata. This is required for non-DF (Designated Forwarder)
filtering in EVPN multi-homing which prevents decapsulated BUM packets
from being forwarded multiple times to the same multi-homed host.
Background
==========
In a typical EVPN