From: Christian Lamparter <chunkeey@web.de>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH 2/2 v2] p54spi: fix p54spi_upload_firmware
Date: Wed, 25 Mar 2009 14:42:58 +0100 [thread overview]
Message-ID: <200903251442.58712.chunkeey@web.de> (raw)
In-Reply-To: <73aaf0dd0903250550x37e6847x38be1f0dcc4b1bb3@mail.gmail.com>
On Wednesday 25 March 2009 13:50:44 Max Filippov wrote:
> >> Sorry, I haven't been used to checkpatch.
> > But your PATCH 1/2 sailed through without any complains. ;-)
> Mere coincidence (:
>
> > BTW: does p54spi really work now?
> I haven't tested your patch yet, but with the one that I sent it does
> work in IBSS mode.
> My aim is to wind it up in mesh mode. This doesn't work, it cannot
> establish peer link.
> I'm going to investigate it. Does mesh mode work on conventional pci/usb p54?
hmm, yes... at least with wireless-testing from yesterday. (beaconing works too)
[ 9862.704138] mesh: running mesh housekeeping
[ 9906.580204] phy3: Allocated STA 00:14:a5:45:33:ff
[ 9906.581566] phy3: Inserted STA 00:14:a5:45:33:ff
[ 9906.581581] Mesh plink: starting establishment with 00:14:a5:45:33:ff
[ 9906.634055] Mesh plink (peer, state, llid, plid, event): 00:14:a5:45:33:ff 1 28312 0 1
[ 9906.636888] Mesh plink (peer, state, llid, plid, event): 00:14:a5:45:33:ff 2 28312 55519 4
[ 9906.636895] Mesh plink with 00:14:a5:45:33:ff ESTABLISHED
64 bytes from 10.0.0.2: icmp_seq=449 ttl=64 time=1.81 ms
64 bytes from 10.0.0.2: icmp_seq=450 ttl=64 time=1.41 ms
64 bytes from 10.0.0.2: icmp_seq=451 ttl=64 time=3.52 ms
...
both peers have a p54 (one is pci, the other one usb)... I'll see if I can
get my old ath5k back to verify that it works with other devices as well.
Regards,
Chr
next prev parent reply other threads:[~2009-03-25 13:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 5:30 [PATCH 1/2] p54spi: mask value read from SPI_ADRS_DMA_WRITE_CTRL in p54spi_wait_bit Max Filippov
2009-03-25 5:30 ` [PATCH 2/2] p54spi: fix p54_upload_firmware Max Filippov
2009-03-25 11:21 ` Christian Lamparter
2009-03-25 12:00 ` Max Filippov
2009-03-25 12:45 ` [PATCH 2/2 v2] p54spi: fix p54spi_upload_firmware Christian Lamparter
2009-03-25 12:50 ` Max Filippov
2009-03-25 12:56 ` Johannes Berg
2009-03-26 2:26 ` Max Filippov
2009-03-25 13:42 ` Christian Lamparter [this message]
2009-03-25 14:34 ` Christian Lamparter
2009-03-26 6:22 ` p54spi - mesh mode summary Max Filippov
2009-03-26 8:12 ` Johannes Berg
2009-03-27 5:03 ` Max Filippov
2009-03-27 14:06 ` Christian Lamparter
2009-03-28 3:21 ` Max Filippov
2009-03-28 21:51 ` Christian Lamparter
2009-03-29 4:41 ` Max Filippov
2009-03-29 13:49 ` Christian Lamparter
2009-03-30 4:38 ` Max Filippov
2009-03-26 1:15 ` [PATCH 2/2 v2] p54spi: fix p54spi_upload_firmware Max Filippov
2009-03-25 10:55 ` [PATCH 1/2] p54spi: mask value read from SPI_ADRS_DMA_WRITE_CTRL in p54spi_wait_bit Christian Lamparter
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=200903251442.58712.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=jcmvbkbc@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 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).