All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [RFC] Serialization of writes
Date: Wed, 4 Feb 2009 14:06:09 -0800	[thread overview]
Message-ID: <20090204220608.GG5581@tesla> (raw)
In-Reply-To: <2B06C052-3C1E-4D4D-BEFD-4778F17DA6CB@groovy.org>

On Wed, Feb 04, 2009 at 01:02:06PM -0800, Chris Kennedy wrote:
> 
> On Feb 4, 2009, at 2:49 PM, W. van den Akker wrote:
> 
> > On Wednesday 04 February 2009, W. van den Akker wrote:
> >> On Wednesday 04 February 2009, Luis R. Rodriguez wrote:
> >>> On Tue, Feb 3, 2009 at 5:12 PM, Luis R. Rodriguez
> >>>
> >>> <lrodriguez@atheros.com> wrote:
> >>>> Some devices requires serialization of writes, this is required
> >>>> for AR5416 and AR9280 PCI devices. This was not implemented in
> >>>> ath9k
> >>>> though. Here's an attempt, but I have no way of testing this as I
> >>>> haven't had issues with my systems or cards. I am not sure if this
> >>>> should fix some of the current issues being reported but it may
> >>>> help.
> >>>>
> >>>> Those who have issues on SMP systems with hostapd locking up --
> >>>> please give this a whirl, let me know if it helps.
> >>>>
> >>>> This has 3 patches in 1 file, the one that counts it the third one
> >>>> but just apply it all together, 'patch -p1 serialize.patch' (
> >>>> for compat-wireless users or testers) or 'git am serialize.patch'
> >>>> for git users.
> >>>>
> >>>> Feedback on results is appreciated.
> >>>>
> >>>> http://www.kernel.org/pub/linux/kernel/people/mcgrof/patches/
> >>>> ath9k/tmp/
> >>>> se rialize.patch
> >>>
> >>> On second thought, this should be pretty useless since because we
> >>> have
> >>> only one tasklet and tasklets are not re-entrant on different CPUs.
> >>> Hm,,,
> >>
> >> I will test this and will report back..
> >>
> >
> > I have updated the git and applied the patch. But hostapd cannot
> > start the
> > adapter to work:
> >
> > xxx:/home/xx# hostapd -dd /etc/hostapd/hostapd.conf
> > Configuration file: /etc/hostapd/hostapd.conf
> > ctrl_interface_group=0
> > Opening raw packet socket for ifindex 1688
> > BSS count 1, BSSID mask ff:ff:ff:ff:ff:ff (0 bits)
> > Failed to set country code
> > wlan0: Unable to setup interface.
> > rmdir[ctrl_interface]: No such file or directory
> >
> > I am using hostapd 0.6.7.
> 
> I'm not sure why this happened on my system, because i have
> two duplicated identical systems and one works without the
> patch without needing this.  The one doing the same thing as
> yours I just put a card in though so I was thinking maybe it was
> something I did, but if yours is doing it too then that's odd.
> On mine, for the time being till I figure it out, I get it to work by
> doing the following (which is odd because I'm basically jump-starting
> udev, but udev should be working and does the second reg set)...
> 
> export COUNTRY=CO
> /sbin/crda
> hostapd -dd /etc/hostapd/hostapd.conf
> 
> For some reason I just have to run crda manually (I have udev script
> setup in proper place),

I've now have heard a few issues with crda udev stuff.
Please test the udev rule by writing a bash script for your /sbin/crda
with something like this:

#!/bin/bash
LOG=/tmp/crda.log
echo $(date) >> $LOG
echo $COUNTRY >> $LOG
echo ------ >> $LOG
/sbin/crda

Please keep in mind the old crda used to put the udev rule into
/etc/udev/rules.d/regulatory.rules -- this can be removed and the
new place is /lib/udev/rules.d/85-regulatory.rules

Note that restarting udev is not required as udev has an inotify for
the daemon on the directories IIRC.

  Luis

  reply	other threads:[~2009-02-04 22:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-04  1:12 [ath9k-devel] [RFC] Serialization of writes Luis R. Rodriguez
2009-02-04  4:47 ` Luis R. Rodriguez
2009-02-04  9:20   ` Chris Kennedy
2009-02-04 17:27   ` W. van den Akker
2009-02-04 20:49     ` W. van den Akker
2009-02-04 21:02       ` Chris Kennedy
2009-02-04 22:06         ` Luis R. Rodriguez [this message]
2009-02-04 22:43           ` Chris Kennedy
2009-02-04 22:52             ` Luis R. Rodriguez
2009-02-05 11:49               ` W. van den Akker
2009-02-05 18:28                 ` W. van den Akker
2009-02-05 19:42                   ` Luis R. Rodriguez
2009-02-05 20:44                     ` W. van den Akker
2009-02-05 21:33                       ` Luis R. Rodriguez
2009-02-05 21:44                         ` W. van den Akker
2009-02-05 22:13                           ` Luis R. Rodriguez
2009-02-05 22:27                             ` W. van den Akker
2009-02-07 13:51                               ` W. van den Akker
2009-02-08 17:18                                 ` W. van den Akker
2009-02-08 23:49                                   ` Luis R. Rodriguez
2009-02-05 20:47                     ` W. van den Akker
2009-02-05 21:34                       ` Luis R. Rodriguez

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=20090204220608.GG5581@tesla \
    --to=lrodriguez@atheros.com \
    --cc=ath9k-devel@lists.ath9k.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 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.