From: "voncken" <cedric.voncken@acksys.fr>
To: 'Michal Kazior' <michal.kazior@tieto.com>
Cc: 'linux-wireless' <linux-wireless@vger.kernel.org>,
ath10k@lists.infradead.org
Subject: RE: ath10k firmware crash
Date: Mon, 13 Oct 2014 16:06:50 +0200 [thread overview]
Message-ID: <025c01cfe6ee$efed3960$cfc7ac20$@acksys.fr> (raw)
In-Reply-To: <CA+BoTQnQkDjkMMu5x-c69s1THf7SQfet2vsOPWs++PtyEHEeTw@mail.gmail.com>
> >>
> >> >> Are you perhaps trying to run STA with 4addr bridging? If so then
> >> >> make sure you use recent ath10k as this was known to be a problem.
> >> >>
> >> > Yes I'm testing with 4 addr bridging because I need to bridge this
> >> interface. I' ll try without this option.
> >> > I'm testing with commit number
> >> > 38eeda3ae6f90fde5546bdd48ee4ff3090f238c0
> >> from kernel.org/pub/scm/linux/kernel/git/firmare/linux-firmware. It
> >> is the latest version in openwrt.
> >> >
> >> >> Can you also provide ath10k traces or debug logs, please?
> >> >>
> >> > I'll send a trace.
> >>
> > I'm using the compat wireless from Openwrt.
> > Compat wireless version 2014-05-22, but we updated the
> > firmware with the latest version provided by openwrt (commit number
> > 38eeda3ae6f90fde5546bdd48ee4ff3090f238c0 from
> > kernel.org/pub/scm/linux/kernel/git/firmare/linux-firmware)
>
> The fix for 4addr STA bridging is in the driver, not the firmware.
>
> The compat version you're using doesn't contain the required fix. I'm pretty
> sure openwrt compat 2014-09-26 contains it.
It fix my issue. Thanks for your help.
Cedric Voncken
>
>
> Michał
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: "voncken" <cedric.voncken@acksys.fr>
To: "'Michal Kazior'" <michal.kazior@tieto.com>
Cc: <ath10k@lists.infradead.org>,
"'linux-wireless'" <linux-wireless@vger.kernel.org>
Subject: RE: ath10k firmware crash
Date: Mon, 13 Oct 2014 16:06:50 +0200 [thread overview]
Message-ID: <025c01cfe6ee$efed3960$cfc7ac20$@acksys.fr> (raw)
In-Reply-To: <CA+BoTQnQkDjkMMu5x-c69s1THf7SQfet2vsOPWs++PtyEHEeTw@mail.gmail.com>
> >>
> >> >> Are you perhaps trying to run STA with 4addr bridging? If so then
> >> >> make sure you use recent ath10k as this was known to be a problem.
> >> >>
> >> > Yes I'm testing with 4 addr bridging because I need to bridge this
> >> interface. I' ll try without this option.
> >> > I'm testing with commit number
> >> > 38eeda3ae6f90fde5546bdd48ee4ff3090f238c0
> >> from kernel.org/pub/scm/linux/kernel/git/firmare/linux-firmware. It
> >> is the latest version in openwrt.
> >> >
> >> >> Can you also provide ath10k traces or debug logs, please?
> >> >>
> >> > I'll send a trace.
> >>
> > I'm using the compat wireless from Openwrt.
> > Compat wireless version 2014-05-22, but we updated the
> > firmware with the latest version provided by openwrt (commit number
> > 38eeda3ae6f90fde5546bdd48ee4ff3090f238c0 from
> > kernel.org/pub/scm/linux/kernel/git/firmare/linux-firmware)
>
> The fix for 4addr STA bridging is in the driver, not the firmware.
>
> The compat version you're using doesn't contain the required fix. I'm pretty
> sure openwrt compat 2014-09-26 contains it.
It fix my issue. Thanks for your help.
Cedric Voncken
>
>
> Michał
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-10-13 14:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 14:46 ath10k firmware crash Cedric VONCKEN
2014-10-10 14:46 ` Cedric VONCKEN
2014-10-13 5:46 ` Michal Kazior
2014-10-13 5:46 ` Michal Kazior
2014-10-13 7:35 ` voncken
2014-10-13 7:35 ` voncken
2014-10-13 7:54 ` Michal Kazior
2014-10-13 7:54 ` Michal Kazior
2014-10-13 9:20 ` voncken
2014-10-13 9:20 ` voncken
2014-10-13 9:25 ` Michal Kazior
2014-10-13 9:25 ` Michal Kazior
2014-10-13 12:00 ` voncken
2014-10-13 12:00 ` voncken
2014-10-13 14:06 ` voncken [this message]
2014-10-13 14:06 ` voncken
2014-10-13 9:23 ` voncken
2014-10-13 9:23 ` voncken
2014-10-13 9:30 ` Michal Kazior
2014-10-13 9:30 ` Michal Kazior
2014-10-13 12:06 ` voncken
2014-10-13 12:06 ` voncken
2014-10-15 12:13 ` Bartosz Markowski
2014-10-15 12:13 ` Bartosz Markowski
2014-10-15 13:05 ` voncken
2014-10-15 13:05 ` voncken
-- strict thread matches above, loose matches on Subject: below --
2025-01-02 20:19 Ath10k " Jamie
2025-01-09 13:08 ` Kalle Valo
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='025c01cfe6ee$efed3960$cfc7ac20$@acksys.fr' \
--to=cedric.voncken@acksys.fr \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.