similar to: [RFC] Tensilica Xtensa (ESP32) backend

Hello, James, Thank you very much for your advices! The next step in compiler development on Espressif is object file generation. There are no essential problems with this step, it will be implemented in nearest future. Currently Xtensa backend is able to print and parse assembly, I used about 1300 tests from gcc torture testsuite and GNU binutils to debug assembly output and now all tests

Tom via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes: >>That makes sense. So you'll have input voltage, output voltage, and >>output current I would guess. You might consider a nodemcu (ESP8266) >>publishing via MQTT to reduce power and use of unobtainium. > > Yes, that is exactly what I was planning to instrument. Maybe battery > voltage too

> Yes, in that we changed the compile time default at some point between those two because pipes have better close semantics for what sshd wants to do. Thanks for quick reply, appreciate it. > That sounds a bit silly. Which daemons? At least python-daemon lib. Look here for functions is_process_started_by_superserver() and is_detach_process_context_required()

These chipsets include the VP2 engine which is composed of a bitstream processor (BSP) that decodes H.264 and a video processor (VP) which can do iDCT/mo-comp/etc for MPEG1/2, H.264, and VC-1. Both of these are driven by separate xtensa chips embedded in the hardware. This patch provides the mechanism to load the kernel for the xtensa chips and provide the necessary interactions to do the rest of

Hey, guys, I have a question about a difference between openssh 4.3 and 5.3. I have plenty of servers with RHEL5 and RHEL6. Most of RHEL5 servers have openssh-server version 4.3p2-72.el5_6.3 (kernel 2.6.39-100.7.1uek) And RHEL6 servers have 5.3p1-111.el6 (kernel 3.8.13-35.el6uek.x86_64) So there is the difference in assigning stdin and stdout for ssh connections. Openssh 4.3 assigns socket (I

Can you give me some insights to implement the windowed calling convention in this xtensa backend : https://github.com/afonso360/llvm-xtensa/tree/xtensa/lib/Target/Xtensa ? For now, only the simpler CALL0 calling convention is implemented. In order to implement the windowed calling convention, every routines must start with the ENTRY instruction which increments the register window pointer. Do

This patchset centralizes the firmware-loading procedure to one set of functions instead of having each engine load its firmware as it pleases. This helps ensure that all firmware comes from the same place, namely nvidia/<chip>/. This changes where the firmware is fetched from for falcon/xtensa/bios, but these locations never seemed to have been official anyway. Also for most (all?) chips

Hey, Op 04-06-13 20:38, Ilia Mirkin schreef: > On Mon, Jun 3, 2013 at 5:02 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >> These chipsets include the VP2 engine which is composed of a bitstream >> processor (BSP) that decodes H.264 and a video processor (VP) which can >> do iDCT/mo-comp/etc for MPEG1/2, H.264, and VC-1. Both of these are >> driven by separate

Hi, I am trying to build asterisk with xtensa compiler on embedded platform. I am trying to integrate my driver code to asterisk. For this tying to call driver code IOCTLs from chan_dahdi instead of dahdi IOCTLs. While compiling asterisk with xtensa, Observed chan_dahdi is not compiling [chan_dahdi.so is not creating].But with default settings [/usrc/src] it was creating. Please let me

While porting opus 1.2.1 to esp32, my compiler had a grumble (error) about possible use of uninitialized variables in decide_dtx_mode() Existing code: --------SNIP--------- /* Decides if DTX should be turned on (=1) or off (=0) */ static int decide_dtx_mode(float activity_probability, /* probability that current frame contains speech/music */ int

Use the newly added u64_to_user_pointer a bit more frequently. Signed-off-by: Joe Perches <joe at perches.com> --- drivers/gpu/drm/armada/armada_gem.c | 2 +- drivers/gpu/drm/nouveau/nouveau_gem.c | 7 ++++--- drivers/gpu/drm/tegra/drm.c | 15 ++++++++------- drivers/gpu/drm/vc4/vc4_bo.c | 4 ++-- drivers/gpu/drm/vc4/vc4_gem.c | 10 +++++-----

Use the newly added u64_to_user_pointer a bit more frequently. Signed-off-by: Joe Perches <joe at perches.com> --- drivers/gpu/drm/armada/armada_gem.c | 2 +- drivers/gpu/drm/nouveau/nouveau_gem.c | 7 ++++--- drivers/gpu/drm/tegra/drm.c | 15 ++++++++------- drivers/gpu/drm/vc4/vc4_bo.c | 4 ++-- drivers/gpu/drm/vc4/vc4_gem.c | 10 +++++-----

Peter, here is v2 with some improved patch descriptions and some fixes. The previous version has survived one day of linux-next and I only changed small parts. So unless there is some other issue, feel free to pull (or to apply the patches) to tip/locking. The following changes since commit 07d9a380680d1c0eb51ef87ff2eab5c994949e69: Linux 4.9-rc2 (2016-10-23 17:10:14 -0700) are available in

Peter, here is v2 with some improved patch descriptions and some fixes. The previous version has survived one day of linux-next and I only changed small parts. So unless there is some other issue, feel free to pull (or to apply the patches) to tip/locking. The following changes since commit 07d9a380680d1c0eb51ef87ff2eab5c994949e69: Linux 4.9-rc2 (2016-10-23 17:10:14 -0700) are available in

Hello, I don't have advanced on the NHW Project this past month, but I have definitely validated its characteristics and this new version. The NHW Codec preserves or enhances image neatness and sharpness, which translates that on good quality images the NHW Codec is globally better than HEVC, and on degraded (with blur, artifacts) images it is worse than HEVC because it lacks of precision. I

On 11/19/2013 08:16 PM, Ilia Mirkin wrote: > Hello, > > I hope this is an appropriate style of request for this forum. I added > code to support video decoding on the tesla cards that have a > similar-style video decoding engine to fermi cards (i.e. G98, GT21x, > the IGP's -- the falcon-controlled decoding engines, rather than the > xtensa-controlled ones), by using

No need to duplicate the same define everywhere. Since the only user is stop-machine and the only provider is s390, we can use a default implementation of cpu_relax_yield in sched.h. Suggested-by: Russell King <linux at armlinux.org.uk> Signed-off-by: Christian Borntraeger <borntraeger at de.ibm.com> --- arch/alpha/include/asm/processor.h | 1 - arch/arc/include/asm/processor.h

No need to duplicate the same define everywhere. Since the only user is stop-machine and the only provider is s390, we can use a default implementation of cpu_relax_yield in sched.h. Suggested-by: Russell King <linux at armlinux.org.uk> Signed-off-by: Christian Borntraeger <borntraeger at de.ibm.com> --- arch/alpha/include/asm/processor.h | 1 - arch/arc/include/asm/processor.h

The following changes since commit afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc: Linux 4.4 (2016-01-10 15:01:32 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus for you to fetch changes up to 43e361f23c49dbddf74f56ddf6cdd85c5dbff6da: checkpatch: add virt barriers (2016-01-12 20:47:08 +0200)

The following changes since commit afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc: Linux 4.4 (2016-01-10 15:01:32 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus for you to fetch changes up to 43e361f23c49dbddf74f56ddf6cdd85c5dbff6da: checkpatch: add virt barriers (2016-01-12 20:47:08 +0200)