From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.228]) by ozlabs.org (Postfix) with ESMTP id 579D8DDF21 for ; Mon, 8 Oct 2007 23:48:20 +1000 (EST) Received: by wx-out-0506.google.com with SMTP id h27so1187940wxd for ; Mon, 08 Oct 2007 06:48:19 -0700 (PDT) Message-ID: <18a15270710080648x3b5f1135meea3d7b048a1a543@mail.gmail.com> Date: Mon, 8 Oct 2007 14:48:19 +0100 From: "Ranulf Doswell" Sender: ralferoo@gmail.com To: "geoffrey.levand@am.sony.com" Subject: Re: [patch 6/6] PS3: Add os-area database routines In-Reply-To: <20071006213542.954029915@am.sony.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1097_11495186.1191851299095" References: <20071006213542.311447584@am.sony.com> <20071006213542.954029915@am.sony.com> Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , ------=_Part_1097_11495186.1191851299095 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 06/10/2007, geoffrey.levand@am.sony.com wrote: > enum os_area_db_owner { > OS_AREA_DB_OWNER_ANY = -1, > OS_AREA_DB_OWNER_NONE = 0, > OS_AREA_DB_OWNER_PROTOTYPE = 1, > OS_AREA_DB_OWNER_LINUX = 2, > OS_AREA_DB_OWNER_PETITBOOT = 3, > OS_AREA_DB_OWNER_MAX = 32, >}; > >enum os_area_db_key { > OS_AREA_DB_KEY_ANY = -1, > OS_AREA_DB_KEY_NONE = 0, > OS_AREA_DB_KEY_RTC_DIFF = 1, > OS_AREA_DB_KEY_VIDEO_MODE = 2, > OS_AREA_DB_KEY_MAX = 8, >}; How do we go about claiming one of these OS_AREA_DB_OWNER_ keys? I'd very much like to use this functionality in my python-ps3 games library. My requirement is to be able to persist various options such as player names and rankings. I had already been thinking about generating a unique token and storing it somewhere at the end of the flash area so that when my game connects to a game server, it can identify itself and be provided with all the previous settings. Obviously, just claiming a random area of flash isn't ideal, so your standardised solution would be perfect for this. I would like, therefore, to reserve a single key to hold a 64-bit sized token in order to identify the machine across reboots. I don't mind particularly whether it's private to my application or a generally available field, but certainly having an identifier I can rely on would be very useful. Cheers, Ralf. ------=_Part_1097_11495186.1191851299095 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
On 06/10/2007, geoffrey.levand@am.sony.com <geoffrey.levand@am.sony.com > wrote:

> enum os_area_db_owner {
> 	OS_AREA_DB_OWNER_ANY = -1,
> 	OS_AREA_DB_OWNER_NONE = 0,
>	OS_AREA_DB_OWNER_PROTOTYPE = 1,
>	OS_AREA_DB_OWNER_LINUX = 2,

>	OS_AREA_DB_OWNER_PETITBOOT = 3,
>	OS_AREA_DB_OWNER_MAX = 32,
>};
>
>enum os_area_db_key {
>	OS_AREA_DB_KEY_ANY = -1,
>	OS_AREA_DB_KEY_NONE = 0,
>	OS_AREA_DB_KEY_RTC_DIFF = 1,

>	OS_AREA_DB_KEY_VIDEO_MODE = 2,
>	OS_AREA_DB_KEY_MAX = 8,
>};
How do we go about claiming one of these OS_AREA_DB_OWNER_ keys? I'd very much like to use this functionality in my python-ps3 games library.

My requirement is to be able to persist various options such as player names and rankings. I had already been thinking about generating a unique token and storing it somewhere at the end of the flash area so that when my game connects to a game server, it can identify itself and be provided with all the previous settings. Obviously, just claiming a random area of flash isn't ideal, so your standardised solution would be perfect for this.

I would like, therefore, to reserve a single key to hold a 64-bit sized token in order to identify the machine across reboots. I don't mind particularly whether it's private to my application or a generally available field, but certainly having an identifier I can rely on would be very useful.

Cheers,
    Ralf.
------=_Part_1097_11495186.1191851299095--