b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: chris at martin.cc <chris@martin.cc>
To: b43-dev@lists.infradead.org
Subject: Switching to 4.174.64.19 firmware for G-PHY cards?
Date: Thu, 3 Mar 2011 14:44:19 +1100	[thread overview]
Message-ID: <AANLkTi=yn7f487ZJMpEOUJESYVj--JOHK3FBgWs4qPf_@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=9HiTE47FSoJzngG5HdbsbrYnjdxMRT0E-qKg8@mail.gmail.com>

2011/3/2 chris at martin.cc <chris@martin.cc>
>
> 2011/3/2 Rafa? Mi?ecki <zajec5@gmail.com>:
> >> b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
> >> b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
> >
> > Did you brought interface up, then down, then again up? I try to check
> > if there is reason for loading firmware twice.
> >
> > Did you get the same messages with old (stable) firmware?
> >
>
> No, not deliberately, it is done by the network start script, so it may.
> It does the same when I us the "Stable" version.
> Tomorrow I will manually bring up the interface and add it to the bridge.

I have had a look at the script. and it appear that the interface is
brought up twice.
The first time to test that it is there and perform some configuration
against it.
The second time when it is passed to hostapd - looks like it resets the device.

----------------------------------------------------------
Chris Martin
m: +61 419 812 371
----------------------------------------------------------

      reply	other threads:[~2011-03-03  3:44 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07 12:21 Switching to 4.174.64.19 firmware for G-PHY cards? Rafał Miłecki
2010-12-07 12:28 ` Rafał Miłecki
2010-12-07 15:32   ` Larry Finger
2010-12-07 19:21     ` Hauke Mehrtens
2011-03-01 13:33       ` Rafał Miłecki
2011-03-02  0:11         ` chris at martin.cc
2011-03-02  0:20           ` Rafał Miłecki
2011-03-02  3:30           ` chris at martin.cc
2011-03-02  9:58             ` Rafał Miłecki
2011-03-02 10:52               ` Rafał Miłecki
2011-03-02 11:22                 ` Jonas Gorski
2011-03-02 12:20                 ` chris at martin.cc
2011-03-02 22:00                   ` Larry Finger
2011-03-02 23:02                     ` chris at martin.cc
2011-03-03  4:43                     ` chris at martin.cc
2011-03-03  7:58                       ` Rafał Miłecki
2011-03-03 11:50                         ` Rafał Miłecki
2011-03-03 23:49                           ` chris at martin.cc
2011-03-07 12:35                             ` Rafał Miłecki
2011-03-04  0:37                           ` chris at martin.cc
2011-03-07 12:26                             ` Rafał Miłecki
2011-03-08  1:12                               ` chris at martin.cc
2011-03-07 13:12                             ` Rafał Miłecki
2011-03-07 16:41                               ` Rafał Miłecki
2011-03-08  1:25                               ` chris at martin.cc
2011-03-08 13:26                                 ` Rafał Miłecki
2011-03-09  0:44                                   ` chris at martin.cc
2011-03-09  0:47                                     ` Rafał Miłecki
2011-03-09  0:47                                     ` chris at martin.cc
2011-03-03  4:55                     ` chris at martin.cc
2011-03-02 23:00                   ` chris at martin.cc
2011-03-02 12:14               ` chris at martin.cc
2011-03-02 13:12                 ` Rafał Miłecki
2011-03-02 23:12                   ` Jonas Gorski
2011-03-03  3:40                   ` chris at martin.cc
2011-03-03  7:55                     ` Rafał Miłecki
2011-03-03 15:52                       ` Larry Finger
2011-03-03  5:34                   ` chris at martin.cc
2011-03-03  4:23                 ` chris at martin.cc
2011-03-02 10:08             ` Rafał Miłecki
2011-03-02 12:17               ` chris at martin.cc
2011-03-03  3:44                 ` chris at martin.cc [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTi=yn7f487ZJMpEOUJESYVj--JOHK3FBgWs4qPf_@mail.gmail.com' \
    --to=chris@martin.cc \
    --cc=b43-dev@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).