similar to: ACPI "blacklist" question

Add support for a new ACPI table that embeds other tables describing a platform's IOMMU topology. Currently the only supported base table is IORT. The VIOT contains an IORT with additional node types, that describe a virtio-iommu. Signed-off-by: Jean-Philippe Brucker <jean-philippe at linaro.org> --- drivers/acpi/Kconfig | 4 ++++ drivers/acpi/Makefile | 1 +

Hi! I'm trying to build lld Microsoft Visual Studio 2012 RC, but it seems the bzero function is not available. Could memset be used instead of bzero? Or maybe define a bzero for msvc using memset. For example: // in-memory matches on-disk, so copy first fields followed by path ::memcpy(to, (uint8_t*)&cmd, 12); ::memcpy(&to[12], _name.data(), _name.size());

On Sat, Jun 16, 2012 at 4:15 PM, Cesar Mello <cmello at gmail.com> wrote: > Hi! > > I'm trying to build lld Microsoft Visual Studio 2012 RC, but it seems the > bzero function is not available. > > Could memset be used instead of bzero? Or maybe define a bzero for msvc > using memset. > > For example: > >       // in-memory matches on-disk, so copy first

Hello, when testing FreeBSD-7.1-BETA i discovered that the floppy disk controller doesn't work correctly. Trying to format a floppy (perhaps with bad blocks) i get: Processing fdformat: ioctl(FD_FORM): Device not configured instead of the normal E letter. I then checked the same problem is present on FreeBSD-6.3 and it has been reported by Beech Rintoul (*) in 2006! Of course the floppy disk

List: This is my first manager client that I've written so please bear with me: I am trying to write a C manager interface client to interface with our CRM software. I am having an issue while reading the data from the manager interface. I am writing this in C and I have the following code: while(1) { bzero(buffer,sizeof(buffer)); readCode = read(socketHandle,buffer,sizeof(buffer));

OK thanks a lot Michael Spencer! After getting your latest commit now everything compiles on Visual Studio 2012 RC. I'm just playing around to learn. Maybe this is the funniest place to start assessing my possibilities of contributing to llvm in the free time: Writer* createWriterPECOFF(const WriterOptionsPECOFF &options) { assert(0 && "PE/COFF support not implemented

On 24/02/15 21:56, Tim Rice wrote: > On Wed, 25 Feb 2015, Damien Miller wrote: > > | On Tue, 24 Feb 2015, Tom G. Christensen wrote: > | > | > I've switched to HEAD in the git repo and it now builds on Solaris > | > 2.6, 7, 8 and 9 but the testsuite still cannot be built due to the > | > missing <err.h>. > > The err.h issue is fixes but there still

Hello All, In reviewing source code for OpenSSH-6.1p1, I found instances of deprecated library calls still within various source code files. Examples of deprecated calls are: bzero() (replaced with memset() which is ANSI compliant), index() (replaced with strchr() which is also ANSI compliant). In file 'auth2-jpake.c', I've replaced all the bzero() calls with the equivalent

I just installed a 6.4-PRERELEASE kernel and tried to boot. The boot failed with a message that my ACPI was blacklisted. I have had 'device acpi' in my kernel for some time now. The boot interruption is new behavior. Is this sort of change a good thing to put in UPDATING? Regards, Jason

Some notebook systems provide the EDID for the internal panel via the _DDC method in ACPI, instead of or in addition to providing the EDID via DDC on LVDS/eDP. Add a DRM helper to search for an ACP _DDC method under the ACPI namespace for each VGA/3D controller, and return the first EDID successfully retrieved via _DDC. Update the i915, nouveau, and radeon DRM-KMS drivers to fall back to

Hi, I have written a C code which would let me connect to the Asterisk Manager Interface. The code compiles successfully but on running the code I get unauthorized login shown in the Asterisk command line console. Here is my C code: #include<stdio.h> #include<netdb.h> #include<unistd.h> #include<string.h> #include<arpa/inet.h> #include<sys/types.h>

I'm seeking feedback on multi-platform support for virtio-iommu. At the moment only devicetree (DT) is supported and we don't have a pleasant solution for other platforms. Once we figure out the topology description, x86 support is trivial. Since the IOMMU manages memory accesses from other devices, the guest kernel needs to initialize the IOMMU before endpoints start issuing DMA.

I'm seeking feedback on multi-platform support for virtio-iommu. At the moment only devicetree (DT) is supported and we don't have a pleasant solution for other platforms. Once we figure out the topology description, x86 support is trivial. Since the IOMMU manages memory accesses from other devices, the guest kernel needs to initialize the IOMMU before endpoints start issuing DMA.

Hello there, sorry - my first mail seems to be lost? Might be I am wrong, but it seems that the behavior of wide link option has been changed since 2.2.7. So we have some problems on our large side to upgrade to 2.2.8a. Here is what I found, but it may be not the intention of samba developer! There ist a new function called readlink_checkin smbd/vfs.c. In this function is a pattern compare

Hello, running Coccinelle (http://coccinelle.lip6.fr/) on the DragonFly source tree with a patch to find issues of this kind turned up this one. Please see the attached diff (against OpenBSD). Regards, Sascha

Hello Liu Jinsong, This is a semi-automatic email about new static checker warnings. The patch 259f201cb7ea: "xen/acpi: ACPI memory hotplug" from Jan 24, 2013, leads to the following Smatch complaint: drivers/xen/xen-acpi-memhotplug.c:198 acpi_memory_get_device() error: we previously assumed 'device' could be null (see line 171) drivers/xen/xen-acpi-memhotplug.c 170

Hello Liu Jinsong, This is a semi-automatic email about new static checker warnings. The patch 259f201cb7ea: "xen/acpi: ACPI memory hotplug" from Jan 24, 2013, leads to the following Smatch complaint: drivers/xen/xen-acpi-memhotplug.c:198 acpi_memory_get_device() error: we previously assumed 'device' could be null (see line 171) drivers/xen/xen-acpi-memhotplug.c 170

Hi guys I've been browsing the code and at many places I found the following odd sequence: char * string=malloc(somesize); ? bzero(string,strlen(string)); free(string); I really don't see why you would zero a string and free the memory immediately afterwards? Any idea why this is done? Thanks! Met vriendelijke groet Best regards Bien ? vous Miguel SANDERS ArcelorMittal Gent UNIX

There's one vulnerability that's bugged me for some time. It applies to nearly all crypto software, including ssh. That's the swapping of sensitive info (such as keys and key equivalents) onto hard drives where they could possibly be recovered later. The Linux kernel provides a system call, mlock(), that inhibits swapping of a specified region of virtual memory. It locks it into real

One line summary: Too many files in a top-level UFS-2 filesystem directory will cause a panic on mount. Kern/Critical/High Priority/SW-Bug Which FreeBSD Release You Are Using: 6.3-STABLE Environment (output of "uname -a" on the problem machine): FreeBSD wahoo.sd67dfl.org 6.3-STABLE FreeBSD 6.3-STABLE #0: Sun Feb 10 21:13:39 CST 2008