search for: platformness

The majority of this series went in a while back, what remains is just the basic platform support and the UART blacklisting. The series has also grown a constcorrectness fix for the other existing platforms too. Still no SATA support from upstream sadly. Bamvor has written some generic docs at http://wiki.xenproject.org/wiki/Xen_ARMv7_with_Virtualization_Extensions/Allwinner Thanks, Ian.

Hello, this patch series adapts the platform drivers below drivers/gpu/drm to use the .remove_new() callback. Compared to the traditional .remove() callback .remove_new() returns no value. This is a good thing because the driver core doesn't (and cannot) cope for errors during remove. The only effect of a non-zero return value in .remove() is that the driver core emits a warning. The device

It provides an initial implementation, LinuxPlatform, which is by default included in the build. Later code will refactor the build process to include the appropriate implementation depending on the target platform. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- src/Makefile.am | 4 ++ src/linux_platform.cpp | 117 ++++++++++++++++++++++++++++++++++++++++++++++++

Dear LLVM community I need some help please. I want to use LLVM's clang and lld within a MacOSX sandboxed app. This is because sandboxing does not allow calls to /usr/bin/clang. The clang binary works fine to compile a file, but ld64.lld comes up with the error "cannot find framework". However similar arguments using /usr/bin/ld instead of ld64.lld works fine. Here are the

These patches implement wxRegion and the ShapedWindow sample. I stole the ruby image from ruby-lang.org. Shamelessly. Maybe someone has a better image we can use for the shaped window. It didn''t seem to make sense to use the Python image. I''d like something even bigger than what I stol^h^h^h^hmade, preferably. Image goes in icons. I had to %ignore one function in wxRegion.

Dear Debian maintainer, The Debian internationalisation team and the Debian English localisation team will soon begin the review of the debconf templates used in xen-api. This review takes place for all packages that use debconf to interact with users and its aims are: - to improve the use of English in all debconf templates; - to make the wording of debconf templates more consistent; - to

Bugs item #16700, was opened at 2007-12-30 02:04 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=16700&group_id=85 Category: win32-api Group: Packaging Status: Open Resolution: None Priority: 3 Submitted By: Luis Lavena (luislavena) Assigned to: Nobody (None) Summary: 1.0.5 x86-mswin32-60 gem is broken Initial Comment: Daniel, The gem you have

Only three entries thus far. Please keep them coming in. -k NAME Martyn Plummer EMAIL plummer@iarc.fr VERSION 0.63.3 PLATFORM i386-unknown-linux SYSTEM Redhat 5.1 CC/FC/MAKE gcc/egcs-g77/make NAME Douglas Bates EMAIL bates@stat.wisc.edu VERSION 0.63.3 PLATFORM i386-unknown-linux SYSTEM Debian 2.1 CC/FC/MAKE egcs/g77/make NAME Thomas

Hello, I'm trying to submit my package to CRAN. When I read the policy, it says: Package authors should make all reasonable efforts to provide cross-platform portable code. Packages will not normally be accepted that do not run on at least two of the major R platforms. What major R platforms does this policy refer to? Currently, my package runs in Ubuntu. If it works on both Ubuntu and

On Wed, Mar 01, 2017 at 07:28:46PM +0100, Viktor Mihajlovski wrote: > On 01.03.2017 16:58, Daniel P. Berrange wrote: > > given a basic Fedora 25 guest, with a virtio-mmio disk added as per the > > guide above... > > > > looking at device '/devices/platform/a003e00.virtio_mmio/virtio3/block/vda': > > KERNEL=="vda" > >

On Wed, Mar 01, 2017 at 07:28:46PM +0100, Viktor Mihajlovski wrote: > On 01.03.2017 16:58, Daniel P. Berrange wrote: > > given a basic Fedora 25 guest, with a virtio-mmio disk added as per the > > guide above... > > > > looking at device '/devices/platform/a003e00.virtio_mmio/virtio3/block/vda': > > KERNEL=="vda" > >

2013/4/3 David Tweed <david.tweed at arm.com>: > Hi, > > As someone working on ARM, we're interested in this sort of issue, to which > there's not yet a complete solution. Some advice below: > > > 2013/4/3 <llvm.buildmaster at lab.llvm.org>: >> The Buildbot has detected a new failure on builder > clang-atom-d2700-ubuntu-rel while building llvm.

From: Pranavkumar Sawargaonkar <pranavkumar@linaro.org> This patch adds initial platform stubs for APM X-Gene. Signed-off-by: Anup Patel <anup.patel@linaro.org> Signed-off-by: Pranavkumar Sawargaonkar <pranavkumar@linaro.org> Drop earlyprintk (split into earlier patch). Only build on ARM64. Drop empty init and reset hooks and enable 1:1 workaround. Signed-off-by: Ian

Hi llvm, it's for sure an obvious idea to use llvm as IR for heterogenous platforms (e.g. CPU+GPU). In theory someone could write plain C/C++ code, which by clang is translated to llvm-IL and then together with JIT-backends packed in an appropriate executable. Thus all the limitations and hassles of openCL or CUDA could be avoided. I wonder if there already is a related project? Of course in

Solaris 8 using forte, I have this error, If anyone has a suggestion, I would apprecaite it. In file included from /usr/include/fcntl.h:23, from ../../src/include/Rinternals.h:34, from ../../src/include/Defn.h:41, from platform.c:25: /usr/include/sys/types.h:149: warning: empty declaration platform.c: In function `do_listfiles':

Hi all, Is there any way to determine which functions are available on which platforms? For example, winProgr essBar (and related functions) are only available on Windows, but what about tkProgressBar and txtProgressBar? Is there any way to figure out which functions are only available on certain platforms, without installing R on that platform and checking? Thanks, Hadley --

Nicholas Piggin <npiggin at gmail.com> writes: > Signed-off-by: Nicholas Piggin <npiggin at gmail.com> > --- > arch/powerpc/include/asm/paravirt.h | 28 ++++++++ > arch/powerpc/include/asm/qspinlock.h | 66 +++++++++++++++++++ > arch/powerpc/include/asm/qspinlock_paravirt.h | 7 ++ > arch/powerpc/platforms/pseries/Kconfig | 5 ++ >

Nicholas Piggin <npiggin at gmail.com> writes: > Signed-off-by: Nicholas Piggin <npiggin at gmail.com> > --- > arch/powerpc/include/asm/paravirt.h | 28 ++++++++ > arch/powerpc/include/asm/qspinlock.h | 66 +++++++++++++++++++ > arch/powerpc/include/asm/qspinlock_paravirt.h | 7 ++ > arch/powerpc/platforms/pseries/Kconfig | 5 ++ >

See attached for new platform timeline; please include platform@fd.o on all proposals/followups/flames/whatever. Oh, and for note's sake, Chris Lee is the other release team member at the moment. ----- Forwarded message from Daniel Stone <daniel@freedesktop.org> ----- Date: Sat, 31 Jul 2004 01:40:19 +1000 From: Daniel Stone <daniel@freedesktop.org> To: platform@freedesktop.org

> Hi, > > > Unfortunately I get the error message: > > isohybrid: slint64-14.1.iso: unable to find mac efi image > > This is probably due to El Torito Platform id "Mac" in > > -eltorito-alt-boot -no-emul-boot -eltorito-platform Mac \ > -eltorito-boot isolinux/macboot.img \ > > This caused in the image >