From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?windows-1252?Q?Christian_K=F6nig?= Subject: Re: PATCH: radeondrm x86_64 and android32 Date: Mon, 15 Sep 2014 13:54:05 +0200 Message-ID: <5416D35D.4080109@vodafone.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from pegasos-out.vodafone.de (pegasos-out.vodafone.de [80.84.1.38]) by gabe.freedesktop.org (Postfix) with ESMTP id 4EC6A6E331 for ; Mon, 15 Sep 2014 04:54:17 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Sergey Korshunoff , dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org Am 15.09.2014 um 12:09 schrieb Sergey Korshunoff: > Android-x86 4.0-r1 (32 bit) have problems with x86_64 kernel when he > trying to use a radeon kms. The following change correct a problem: > > drivers/gpu/drm/radeon_kms.c (function radeon_info_ioctl): > > - value_ptr = (uint32_t *)((unsigned long)info->value); > + value_ptr = (uint32_t *)((unsigned)info->value); > > Looks like a userspace data in android running under x86_64 is located > above 4 Gb. I don't think so. But after this change android run fine. That's most likely a bug on the userspace side, caused by the upper 32bits of info->value not initialized properly. The kernel patch you show above will most likely just break 64bit userspace. Regards, Christian. > _______________________________________________ > dri-devel mailing list > dri-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/dri-devel