On Thu, Oct 1, 2015 at 1:13 PM, Max Filippov wrote:
> On Thu, Oct 1, 2015 at 10:18 PM, Peter Crosthwaite
> wrote:
>> On Thu, Oct 1, 2015 at 11:25 AM, Max Filippov wrote:
>>> On Thu, Oct 1, 2015 at 9:06 PM, Peter Crosthwaite
>>> wrote:
What is your intended user command lines? E.g. how do I
On Thu, Oct 1, 2015 at 10:18 PM, Peter Crosthwaite
wrote:
> On Thu, Oct 1, 2015 at 11:25 AM, Max Filippov wrote:
>> On Thu, Oct 1, 2015 at 9:06 PM, Peter Crosthwaite
>> wrote:
>>> What is your intended user command lines? E.g. how do I boot with
>>> ml605 no-mmu and then with mmu.
>>
>> '-M ml60
On Thu, Oct 1, 2015 at 11:25 AM, Max Filippov wrote:
> On Thu, Oct 1, 2015 at 9:06 PM, Peter Crosthwaite
> wrote:
>> On Wed, Sep 30, 2015 at 3:42 PM, Max Filippov wrote:
>>> On Thu, Oct 1, 2015 at 1:23 AM, Peter Crosthwaite
>>> wrote:
On Wed, Sep 30, 2015 at 3:07 PM, Max Filippov wrote:
>
On Thu, Oct 1, 2015 at 9:06 PM, Peter Crosthwaite
wrote:
> On Wed, Sep 30, 2015 at 3:42 PM, Max Filippov wrote:
>> On Thu, Oct 1, 2015 at 1:23 AM, Peter Crosthwaite
>> wrote:
>>> On Wed, Sep 30, 2015 at 3:07 PM, Max Filippov wrote:
On Thu, Oct 1, 2015 at 12:02 AM, Peter Crosthwaite
w
On Wed, Sep 30, 2015 at 3:42 PM, Max Filippov wrote:
> On Thu, Oct 1, 2015 at 1:23 AM, Peter Crosthwaite
> wrote:
>> On Wed, Sep 30, 2015 at 3:07 PM, Max Filippov wrote:
>>> On Thu, Oct 1, 2015 at 12:02 AM, Peter Crosthwaite
>>> wrote:
Which makes MMU vs noMMU a board level property, not a
On Wed, Sep 30, 2015 at 3:07 PM, Max Filippov wrote:
> On Thu, Oct 1, 2015 at 12:02 AM, Peter Crosthwaite
> wrote:
>> On Wed, Sep 30, 2015 at 1:54 PM, Max Filippov wrote:
>>> On Wed, Sep 30, 2015 at 11:45 PM, Peter Maydell
>>> wrote:
Because for QEMU the CPU is really just the CPU. Your ot
On Thu, Oct 1, 2015 at 1:23 AM, Peter Crosthwaite
wrote:
> On Wed, Sep 30, 2015 at 3:07 PM, Max Filippov wrote:
>> On Thu, Oct 1, 2015 at 12:02 AM, Peter Crosthwaite
>> wrote:
>>> Which makes MMU vs noMMU a board level property, not a CPU property.
>>> It should appear in QEMU as such.
>>
>> Ok,
On Wed, Sep 30, 2015 at 3:23 PM, Peter Crosthwaite
wrote:
> On Wed, Sep 30, 2015 at 3:07 PM, Max Filippov wrote:
>> On Thu, Oct 1, 2015 at 12:02 AM, Peter Crosthwaite
>> wrote:
>>> On Wed, Sep 30, 2015 at 1:54 PM, Max Filippov wrote:
On Wed, Sep 30, 2015 at 11:45 PM, Peter Maydell
wr
On Thu, Oct 1, 2015 at 12:02 AM, Peter Crosthwaite
wrote:
> On Wed, Sep 30, 2015 at 1:54 PM, Max Filippov wrote:
>> On Wed, Sep 30, 2015 at 11:45 PM, Peter Maydell
>> wrote:
>>> Because for QEMU the CPU is really just the CPU. Your other
>>> random devices don't live in the CPU, even if you're
>
On Wed, Sep 30, 2015 at 1:54 PM, Max Filippov wrote:
> On Wed, Sep 30, 2015 at 11:45 PM, Peter Maydell
> wrote:
>> On 30 September 2015 at 21:17, Max Filippov wrote:
>>> On Tue, Sep 29, 2015 at 11:42 PM, Peter Maydell
>>> wrote:
On 29 September 2015 at 11:34, Max Filippov wrote:
> Cha
On Tue, Sep 29, 2015 at 11:42 PM, Peter Maydell
wrote:
> On 29 September 2015 at 11:34, Max Filippov wrote:
>> Changing address space layout according to CPU type is what happens
>> in actual hardware. There are no user-controllable settings that would
>> allow mismatching address space layout an
On Wed, Sep 30, 2015 at 11:45 PM, Peter Maydell
wrote:
> On 30 September 2015 at 21:17, Max Filippov wrote:
>> On Tue, Sep 29, 2015 at 11:42 PM, Peter Maydell
>> wrote:
>>> On 29 September 2015 at 11:34, Max Filippov wrote:
Changing address space layout according to CPU type is what happen
On 30 September 2015 at 21:17, Max Filippov wrote:
> On Tue, Sep 29, 2015 at 11:42 PM, Peter Maydell
> wrote:
>> On 29 September 2015 at 11:34, Max Filippov wrote:
>>> Changing address space layout according to CPU type is what happens
>>> in actual hardware. There are no user-controllable setti
On Tue, Sep 29, 2015 at 10:20 PM, Peter Crosthwaite
wrote:
> You want some sort of container that can serve as this higher level
> configurable object. The drop down menus in your cad tools then map to
> QOM props on the container level (not the CPU level). Currently you
> don't have a SoC/Machine
On 29 September 2015 at 11:34, Max Filippov wrote:
> On Mon, Sep 28, 2015 at 12:59 AM, Peter Crosthwaite
> wrote:
>> On Sun, Sep 27, 2015 at 2:48 PM, Max Filippov wrote:
>>> On Mon, Sep 28, 2015 at 12:28 AM, Peter Crosthwaite
>>> wrote:
To clarify, can you tell me the QEMU command line dif
On Tue, Sep 29, 2015 at 3:34 AM, Max Filippov wrote:
> On Mon, Sep 28, 2015 at 12:59 AM, Peter Crosthwaite
> wrote:
>> On Sun, Sep 27, 2015 at 2:48 PM, Max Filippov wrote:
>>> On Mon, Sep 28, 2015 at 12:28 AM, Peter Crosthwaite
>>> wrote:
To clarify, can you tell me the QEMU command line d
On Mon, Sep 28, 2015 at 12:59 AM, Peter Crosthwaite
wrote:
> On Sun, Sep 27, 2015 at 2:48 PM, Max Filippov wrote:
>> On Mon, Sep 28, 2015 at 12:28 AM, Peter Crosthwaite
>> wrote:
>>> To clarify, can you tell me the QEMU command line difference between
>>> MMU and noMMU?
>>
>> There is no differe
On Sun, Sep 27, 2015 at 2:48 PM, Max Filippov wrote:
> On Mon, Sep 28, 2015 at 12:28 AM, Peter Crosthwaite
> wrote:
>> On Sun, Sep 27, 2015 at 12:01 PM, Max Filippov wrote:
>>> On Sun, Sep 27, 2015 at 9:43 PM, Peter Crosthwaite
>>> wrote:
On Sun, Sep 27, 2015 at 11:13 AM, Max Filippov wro
On Mon, Sep 28, 2015 at 12:28 AM, Peter Crosthwaite
wrote:
> On Sun, Sep 27, 2015 at 12:01 PM, Max Filippov wrote:
>> On Sun, Sep 27, 2015 at 9:43 PM, Peter Crosthwaite
>> wrote:
>>> On Sun, Sep 27, 2015 at 11:13 AM, Max Filippov wrote:
On Sun, Sep 27, 2015 at 8:38 PM, Peter Crosthwaite
>>
On Sun, Sep 27, 2015 at 12:01 PM, Max Filippov wrote:
> On Sun, Sep 27, 2015 at 9:43 PM, Peter Crosthwaite
> wrote:
>> On Sun, Sep 27, 2015 at 11:13 AM, Max Filippov wrote:
>>> On Sun, Sep 27, 2015 at 8:38 PM, Peter Crosthwaite
>>> wrote:
On Sun, Sep 27, 2015 at 10:16 AM, Max Filippov wro
On Sun, Sep 27, 2015 at 9:43 PM, Peter Crosthwaite
wrote:
> On Sun, Sep 27, 2015 at 11:13 AM, Max Filippov wrote:
>> On Sun, Sep 27, 2015 at 8:38 PM, Peter Crosthwaite
>> wrote:
>>> On Sun, Sep 27, 2015 at 10:16 AM, Max Filippov wrote:
int n;
>>>
>>> Blank line.
>>
>> Why?
>>
> Just a
On Sun, Sep 27, 2015 at 11:13 AM, Max Filippov wrote:
> On Sun, Sep 27, 2015 at 8:38 PM, Peter Crosthwaite
> wrote:
>> On Sun, Sep 27, 2015 at 10:16 AM, Max Filippov wrote:
>>> Cores with and without MMU have system RAM and ROM at different locations.
>>> Also with noMMU cores system IO region i
On Sun, Sep 27, 2015 at 8:38 PM, Peter Crosthwaite
wrote:
> On Sun, Sep 27, 2015 at 10:16 AM, Max Filippov wrote:
>> Cores with and without MMU have system RAM and ROM at different locations.
>> Also with noMMU cores system IO region is accessible through two physical
>> address ranges.
>>
>> Sig
On Sun, Sep 27, 2015 at 10:16 AM, Max Filippov wrote:
> Cores with and without MMU have system RAM and ROM at different locations.
> Also with noMMU cores system IO region is accessible through two physical
> address ranges.
>
> Signed-off-by: Max Filippov
> ---
> hw/xtensa/xtfpga.c | 49 +++
Cores with and without MMU have system RAM and ROM at different locations.
Also with noMMU cores system IO region is accessible through two physical
address ranges.
Signed-off-by: Max Filippov
---
hw/xtensa/xtfpga.c | 49 +
1 file changed, 41 inser
25 matches
Mail list logo
