Port-arm archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Cortex-A9 boot problems with d-cache on Zynq



Nick Hudson <nick.hudson%gmx.co.uk@localhost> wrote:
>On 08/06/2019 14:09, Robert Swindells wrote:
>>
>> Nick Hudson <nick.hudson%gmx.co.uk@localhost> wrote:
>>>> On 8 Jun 2019, at 12:53, Robert Swindells <rjs%fdy2.co.uk@localhost> wrote:
>>>>
>>>> Nick Hudson <nick.hudson%gmx.co.uk@localhost> wrote:
>>>>>> On 02/06/2019 00:07, Robert Swindells wrote:
>>>>>>
>>>>>> Alexander Nasonov <alnsn%yandex.ru@localhost> wrote:
>>>>>>> Nick Hudson wrote:
>>>>>>>> ...
>>>>>>>> Can I convince you guys to work on FDTizing the ZYNQ7000 stuff? :)
>>>>>>>
>>>>>>> Please tell me what I need to do. I added
>>>>>>
>>>>>> The diffs that I posted a while ago compile, I don't think anything has
>>>>>> changed in my tree since then.
>>>>>>
>>>>>> Someone still needs to write a clock driver for it.
>>>>>>
>>>>>
>>>>> I'll commit something to sys/arch/arm/xilinx so the FDTisation can
>>>>> happen without breaking existing kernels
>>>>
>>>> I don't feel that we should break an existing port, even if it is only
>>>> for a short time.
>>>>
>>>> If you are proposing to write a clock/reset driver then great.
>>>>
>>>> I think it would be good to keep a separate PARALLELLA config even after
>>>> the xilinx code is using FDT so that we don't need to update u-boot.
>>>
>>> Sorry if I wasn’t clear. The point of the new directory is to keep the
>>> PARALLELLA (and other) config working
>>
>> Not sure I see the point, if someone writes a clock/reset driver then
>> we can switch over to using FDT for all Zynq boards.
>
>The point is so development can progress with code in CVS, rather than
>having incomplete patches passed around.

I'm not checking in an incomplete port, so we end up with two
directories containing identical code ?

There haven't been any new patches.


Home | Main Index | Thread Index | Old Index