Am 13.11.2009 um 11:59 schrieb Juan Quintela :
Alexander Graf wrote:
On 13.11.2009, at 01:48, Glauber Costa wrote:
Because that would mean I'd have to deal with it in the code later on
and I don't see the point of writing code that's not in the load/save
cycle because of limitations there.
Alexander Graf wrote:
> On 13.11.2009, at 01:48, Glauber Costa wrote:
> Because that would mean I'd have to deal with it in the code later on
> and I don't see the point of writing code that's not in the load/save
> cycle because of limitations there.
Hi
could you take a look at this one?
This
On 13.11.2009, at 01:48, Glauber Costa wrote:
On Thu, Nov 12, 2009 at 09:53:10PM +0100, Alexander Graf wrote:
The fw_cfg interface can only handle up to 16 bits of data for its
streams.
While that isn't too much of a problem when handling integers, we
would
like to stream full kernel image
On Thu, Nov 12, 2009 at 09:53:10PM +0100, Alexander Graf wrote:
> The fw_cfg interface can only handle up to 16 bits of data for its streams.
> While that isn't too much of a problem when handling integers, we would
> like to stream full kernel images over that interface!
>
> So let's extend it to
Alexander Graf wrote:
Juan, I'd really love to learn some new voodoo :-).
This whole new qdev whatever based save format was supposed to make
things like this easy, right? I would've known what to do with the old
code ...
I think Juan's mentioned something about writing a doc explaining how t
On 11.11.2009, at 23:22, Anthony Liguori wrote:
Alexander Graf wrote:
Anthony Liguori wrote:
Alexander Graf wrote:
The fw_cfg interface can only handle up to 16 bits of data for its
streams.
While that isn't too much of a problem when handling integers, we
would
like to stream full kern
Alexander Graf wrote:
Anthony Liguori wrote:
Alexander Graf wrote:
The fw_cfg interface can only handle up to 16 bits of data for its
streams.
While that isn't too much of a problem when handling integers, we would
like to stream full kernel images over that interface!
So let's extend
Anthony Liguori wrote:
> Alexander Graf wrote:
>> The fw_cfg interface can only handle up to 16 bits of data for its
>> streams.
>> While that isn't too much of a problem when handling integers, we would
>> like to stream full kernel images over that interface!
>>
>> So let's extend it to 32 bit le
Alexander Graf wrote:
The fw_cfg interface can only handle up to 16 bits of data for its streams.
While that isn't too much of a problem when handling integers, we would
like to stream full kernel images over that interface!
So let's extend it to 32 bit length variables.
Signed-off-by: Alexande
