[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-arm] [PATCH v3 03/10] aspeed-soc: provide a framework to add n
|
From: |
Cédric Le Goater |
|
Subject: |
Re: [Qemu-arm] [PATCH v3 03/10] aspeed-soc: provide a framework to add new SoCs |
|
Date: |
Mon, 22 Aug 2016 11:07:10 +0200 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 |
Hello Peter,
On 08/12/2016 11:21 AM, Peter Maydell wrote:
> On 12 August 2016 at 09:33, Cédric Le Goater <address@hidden> wrote:
>> On 08/11/2016 12:14 PM, Peter Maydell wrote:
>>> board_id 0 means "I am an EBSA110", which this isn't,
>>> and your silicon rev values are completely out of range.
>>
>> OK. I was not aware of this. I will request new board ids for
>> the ast2400 and ast2500
>
> Why do you need them? Anything new should be device-tree-only,
> and I would expect pushback from the kernel side if you
> try to allocate new stuff.
Sorry for the late answer, I was out in Brittany (and it was
sunny).
I got confused by our aspeed kernel tree which still has some
unmerged oddities. I will use -1 for the board ID.
Thanks,
C.
- Re: [Qemu-arm] [PATCH v3 01/10] ast2400: rename the Aspeed SoC files to aspeed_soc, (continued)
[Qemu-arm] [PATCH v3 04/10] palmetto-bmc: rename the Aspeed board file to aspeed.c, Cédric Le Goater, 2016/08/02
[Qemu-arm] [PATCH v3 05/10] palmetto-bmc: replace palmetto_bmc with aspeed, Cédric Le Goater, 2016/08/02
[Qemu-arm] [PATCH v3 06/10] palmetto-bmc: add board specific configuration, Cédric Le Goater, 2016/08/02