From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1OANTY-0006em-12 for qemu-devel@nongnu.org; Fri, 07 May 2010 09:20:20 -0400 Received: from [140.186.70.92] (port=46810 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OANTN-0005km-1O for qemu-devel@nongnu.org; Fri, 07 May 2010 09:20:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OALzP-0003fO-Gp for qemu-devel@nongnu.org; Fri, 07 May 2010 07:45:08 -0400 Received: from david.siemens.de ([192.35.17.14]:17192) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OALzP-0003eo-88 for qemu-devel@nongnu.org; Fri, 07 May 2010 07:45:07 -0400 Message-ID: <4BE3FD3F.4070606@siemens.com> Date: Fri, 07 May 2010 13:45:03 +0200 From: Jan Kiszka MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Registering buffers with a qdict List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Luiz Capitulino Cc: qemu-devel Hi Luiz, what is the recommended way of pushing larger buffers (up to 64K so far) into a qdict? QLIST of QINT (one per byte) looks a bit heavy. I thought about hex-encoding the content first (series of "%02X"), then registering it as QSTRING. Or should we introduce a new type, QBUFFER? Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux