Il 12/03/2013 07:48, Richard Henderson ha scritto:
> On 2013-03-11 04:17, Paolo Bonzini wrote:
>> == hw/pci ==
>> hw/alpha_typhoon.c hw/pci/host-typhoon.c
>
> Why wouldn't this go into hw/alpha/, really?
Sure. I think the Alpha-specific interrupt delivery parts should b
On 2013-03-11 04:17, Paolo Bonzini wrote:
== hw/pci ==
hw/alpha_typhoon.c hw/pci/host-typhoon.c
Why wouldn't this go into hw/alpha/, really?
r~
On Mon, Mar 11, 2013 at 12:17:20PM +0100, Paolo Bonzini wrote:
> hw/dataplane/Makefile.objs hw/block/dataplane/Makefile.objs
> hw/dataplane/hostmem.c hw/block/dataplane/hostmem.c
> hw/dataplane/ioq.c hw/block/dataplane/ioq.c
> hw/dat
Peter Maydell writes:
> On 11 March 2013 11:54, Paolo Bonzini wrote:
>> Il 11/03/2013 12:31, Peter Maydell ha scritto:
>>> On 11 March 2013 11:17, Paolo Bonzini wrote:
hw/arm11mpcore.c hw/arm/arm11mpcore.c
>>>
>>> Two devices but I can split them if you insist.
Il 11/03/2013 14:08, Peter Maydell ha scritto:
>>> These are little more than SoC containers, aren't they?
>>> >>
>>> >> They're container devices, yes. But why should container devices
>>> >> go under hw/$ARCH ?
>> >
>> > Because they don't really implement any logic, ideally a board should b
On 11 March 2013 12:44, Paolo Bonzini wrote:
> Il 11/03/2013 13:39, Peter Maydell ha scritto:
>> On 11 March 2013 11:54, Paolo Bonzini wrote:
>>> These are little more than SoC containers, aren't they?
>>
>> They're container devices, yes. But why should container devices
>> go under hw/$ARCH ?
>
Il 11/03/2013 13:39, Peter Maydell ha scritto:
> On 11 March 2013 11:54, Paolo Bonzini wrote:
>> Il 11/03/2013 12:31, Peter Maydell ha scritto:
>>> On 11 March 2013 11:17, Paolo Bonzini wrote:
hw/arm11mpcore.c hw/arm/arm11mpcore.c
>>>
>>> Two devices but I can spl
Il 11/03/2013 12:31, Peter Maydell ha scritto:
> On 11 March 2013 11:17, Paolo Bonzini wrote:
>> - Files go in hw/ARCH/ if they used to be in hw/ARCH/Makefile.objs and
>> they define multiple devices (example: hw/arm/tc6393xb.c)
>
> Why are multiple devices in one file a bad thing (or at least,
On Mon, Mar 11, 2013 at 12:17:20PM +0100, Paolo Bonzini wrote:
> The general ideas are (earlier rules override the later, and exceptions
> are of course possible):
>
> - Board files go in hw/ARCH/ (already done).
>
> - Files go in hw/ARCH/ if they reference that arch's CPUState (already done)
>
On 11 March 2013 11:17, Paolo Bonzini wrote:
> - Files go in hw/ARCH/ if they used to be in hw/ARCH/Makefile.objs and
> they define multiple devices (example: hw/arm/tc6393xb.c)
Why are multiple devices in one file a bad thing (or at least, a
thing that should determine where a file lives)? Sho
The general ideas are (earlier rules override the later, and exceptions
are of course possible):
- Board files go in hw/ARCH/ (already done).
- Files go in hw/ARCH/ if they reference that arch's CPUState (already done)
- Files already in a subdirectory are not moved (examples: some PPC/S390
fi
11 matches
Mail list logo
