From what I can gather the original reporter was concerned about the excessive number of messages in their syslog regarding the wl driver. There is in fact a patch for this here:
++ if (err != -EINVAL) {
++ // Don't fill syslog with EINVAL error
++ WL_ERR(("Could not get rssi (%d)\n", err));
Generally, when there multiple issues in one bug report we stick with the original issue and ask other people experiencing different issues to submit new bug reports. As such it'd be great if Adam Porter could submit a new bug report regarding his issue of the incorrect driver being used. Once a new bug report has been created I'll personally ensure that someone looks at it.
From what I can gather the original reporter was concerned about the excessive number of messages in their syslog regarding the wl driver. There is in fact a patch for this here:
http:// pkgbuild. com/git/ aur-mirror. git/commit/ broadcom- wl?id=e87e8290a 6d1abd88c064d51 cc94f19b137bae1 1
here are the relevant bits:
++ if (err != -EINVAL) {
++ // Don't fill syslog with EINVAL error
++ WL_ERR(("Could not get rssi (%d)\n", err));
Generally, when there multiple issues in one bug report we stick with the original issue and ask other people experiencing different issues to submit new bug reports. As such it'd be great if Adam Porter could submit a new bug report regarding his issue of the incorrect driver being used. Once a new bug report has been created I'll personally ensure that someone looks at it.