Release goals for 22.XX
hauke at hauke-m.de
Wed Oct 13 15:41:43 PDT 2021
On 10/14/21 12:03 AM, Sergey Ryazanov wrote:
> On Mon, Oct 11, 2021 at 12:12 AM Hauke Mehrtens <hauke at hauke-m.de> wrote:
>> On 10/10/21 2:44 AM, Sergey Ryazanov wrote:
>>> On Fri, Oct 8, 2021 at 4:40 PM Rui Salvaterra <rsalvaterra at gmail.com> wrote:
>>>> On Fri, 8 Oct 2021 at 11:09, Rui Salvaterra <rsalvaterra at gmail.com> wrote:
>>>>> Nothing in this target has more than 32 MiB of RAM (most devices have
>>>>> 16 MiB) . Just put it out of its misery. :)
>>>> Scratch that. After chatting with dangole, there may be some life in
>>>> it, after all. I have an ath25 device (FON2200) and didn't even
>>>> remember it.
>>> I am in the process of migrating ath25 to the 5.10 kernel. Initial
>>> build was trivial. But I need to restore the Marvel swconfig driver
>>> that was lost during the initial 5.10 kernel introduction, and
>>> carefully run-time test it.
>> Does it make sense to directly convert this board to the upstream DSA
>> driver for the Marvell 88E6060 switch:
>> It looks like our swconfig driver creates a bridge over all ports and
>> the DSA driver only allows communication between the individual port and
>> the CPU port.
>> I do not know how much effort this is and if you have the device for
> I do not think that migration to DSA without DT support will be a
> practical step. Let's keep it as is until we are able to run new
> kernels with it.
You are right as ath25 doesn't use device tree using DSA drivers would
be hard. It is probably easier to stay with the swconfig driver.
More information about the openwrt-devel