[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEyMn7Z-4apxxSns+eJDv6nHqGz6UvGCWa4+MmFTv4NXHyYiqw@mail.gmail.com>
Date: Thu, 23 Feb 2023 11:44:02 +0100
From: Heiko Thiery <heiko.thiery@...il.com>
To: Johannes Berg <johannes@...solutions.net>
Cc: Dan Williams <dcbw@...hat.com>, Ajay.Kathat@...rochip.com,
kvalo@...nel.org, michael@...le.cc, kuba@...nel.org,
Claudiu.Beznea@...rochip.com, linux-wireless@...r.kernel.org,
netdev@...r.kernel.org, Amisha.Patel@...rochip.com,
thaller@...hat.com, bgalvani@...hat.com,
Sripad.Balwadgi@...rochip.com
Subject: Re: wilc1000 MAC address is 00:00:00:00:00:00
Hi Ajay,
Am Mi., 15. Feb. 2023 um 21:14 Uhr schrieb Johannes Berg
<johannes@...solutions.net>:
>
> On Fri, 2023-02-10 at 15:28 -0600, Dan Williams wrote:
> > >
> > > In wilc1000, the bus interface is up in probe but we don't have
> > > access
> > > to mac address via register until the driver starts the wilc firmware
> > > because of design limitation. This information is only available
> > > after
> > > the MAC layer is initialized.
> >
> > So... initialize the MAC layer and read the address, then stop the card
> > until dev open which reloads and reinits? That's what eg Atmel does
>
> For a more modern example, iwlwifi also ;-)
>
> You should also load the firmware async, so it becomes:
>
> probe
> -> load firmware
>
> firmware success callback
> - boot device
> - read information
> - register with mac80211
> - shut down device
>
> mac80211 start callback
> - boot device again
> - etc.
Do you have a meaning about that? That sounds like a viable solution.
What do you think?
--
Heiko
> johannes
Powered by blists - more mailing lists