On 3 December 2014 at 09:27, John Crispin <blo...@openwrt.org> wrote: > On 03/12/2014 07:10, Rafał Miłecki wrote: >> Honestly, I don't know what is this file for. I don't understand >> netifd & wireless well at all. I asked for help in the Request for >> any netifd wireless documentation e-mail thread, but ppl who know >> /things/ ignored me. > > can you narrow down your questions to specific things you don't > understand ? a global "i don't understand it" is hard to resolve. > > in general there are 2 files > > * /lib/wifi/*.sh - the legacy layer used for probing the hw during > "wifi detect" > * /lib/netfid/wireless/*.sh the new netifd wifi layer > > which of the 2 is causing /problems/
There are some questions I posted in the mentioned e-mail: On 18 November 2014 at 12:19, Rafał Miłecki <zaj...@gmail.com> wrote: > I can see multiple files: > /sbin/wifi > /lib/wifi/mac80211.sh > /lib/netifd/wireless/mac80211.sh > /lib/netifd/hostapd.sh > but they mostly don't contain any comments. > > I'm not sure how much it's worth to list unclear parts of that. > > It's confusing to have /lib/netifd/ and /lib/wifi/. It's confusing to > have two APIs (inconsistent callbacks). I can't understand why even > for mac80211.sh we keep detecting code in /lib/wifi/. There isn't > anything documented in the /lib/netifd/netifd-wireless.sh. I have no > idea how netifd <-> scripts communication works. What is handled in > scripts and what in netifd? You say that /lib/wifi/*sh is legacy layer. I can understand we need it for Broadcom or similar. But what's the point of having mac80211 there? Also why do we have something like /lib/netifd/hostapd.sh? Isn't wireless stuff supposed to be in /lib/netifd/wireless/? -- Rafał _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
