Date: Sun, 28 Apr 2013 12:49:38 -0700 From: Adrian Chadd <adrian@freebsd.org> To: lev@freebsd.org Cc: freebsd-wireless@freebsd.org Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic Message-ID: <CAJ-VmonJZ0fHfQE%2Bk2Bp-VaYgMhwt7bgGT7r-iCRRWnT6KmZYw@mail.gmail.com> In-Reply-To: <15710249844.20130428234801@serebryakov.spb.ru> References: <2810538978.20130423164137@serebryakov.spb.ru> <CAJ-Vmom4UDoz7EgdnVeQ%2BALuFFXkH9t_Uj7=FwL77S5rKfUD1g@mail.gmail.com> <1813905823.20130423184528@serebryakov.spb.ru> <CAJ-VmomhRaKODxis09MjAhUbAUOw%2B6jWBY48JpZR_JgfZZLKcQ@mail.gmail.com> <184105677.20130424002002@serebryakov.spb.ru> <CAJ-VmokVmHDXwE7S5koSqtFjPXQ_VUPhj8gfMruDM2k-DyUMPw@mail.gmail.com> <1936997795.20130424003555@serebryakov.spb.ru> <CAJ-Vmokx2QhcjcsgA-_kqjX63Vu4CLk7HkuyALautbnzp61ywQ@mail.gmail.com> <886711115.20130424004702@serebryakov.spb.ru> <CAJ-VmoksSTBC7jmC-_hvBeJFSD0k28HoZodaWdHm0AF0d1yZJg@mail.gmail.com> <6010292503.20130426001447@serebryakov.spb.ru> <CAJ-VmomUsPgHTVGaKHZ_YE%2Bu1ZOjGqrVfh2uYmvOs6gKmhnxOw@mail.gmail.com> <CAJ-VmokZBbmHbruKJV-8kvTyOTsiq5_XHnfqUYo3vO68872Q=w@mail.gmail.com> <99510815.20130426122508@serebryakov.spb.ru> <CAJ-VmoktRPbnDRbRuwA4i8w50kExs2pwD4yBawL6iOz7F4Bknw@mail.gmail.com> <CAJ-VmonCao99MOrm97tQS_f1xS9tieQfg-nQUB4APWVmdJJUBg@mail.gmail.com> <CAJ-Vmonpc6rMKfT3qHme4Yzwkcj0zij8dYzXktpbz3bbSmT0=Q@mail.gmail.com> <1467048277.20130428225006@serebryakov.spb.ru> <CAJ-VmokLKdwckXjzH64P=mYm9pZQzkCkJhDV4iojzJehXmJLLA@mail.gmail.com> <15710249844.20130428234801@serebryakov.spb.ru>
index | next in thread | previous in thread | raw e-mail
.. how's this never triggered a clang warning on me before? Just add casts for now or something so it compiles. Adrian On 28 April 2013 12:48, Lev Serebryakov <lev@freebsd.org> wrote: > Hello, Adrian. > You wrote 28 апреля 2013 г., 23:38:20: > > AC> There's some race condition hack that Sam threw in that gets enabled > AC> only if you compile things with TDMA support enabled. Would you mind > AC> compiling in TDMA support (add options IEEE80211_SUPPORT_TDMA) to your > AC> kernel config and rebuild? I'd like to see if that TX queue workaround > AC> is effective at helping us out here. > Oooopps... And, yes, it is really annoying, that there is no good way > to specify (u_)?int\d\d?_t in printf() :( > > cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -nostdinc -I. -I/data/src/sys -I/data/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-omit-frame-pointer -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /data/src/sys/dev/ath/if_ath_tdma.c -I/data/src/sys/dev/ath > /data/src/sys/dev/ath/if_ath_tdma.c:442:42: error: format specifies type 'unsigned long long' but the argument has type 'u_int64_t' (aka 'unsigned long') [-Werror,-Wformat] > (unsigned long long) rs->rs_tstamp, rstamp, tsf, txtime, > ^~~~~~ > /data/src/sys/dev/ath/if_ath_debug.h:97:34: note: expanded from macro 'DPRINTF' > device_printf(sc->sc_dev, fmt, __VA_ARGS__); \ > ^ > /data/src/sys/dev/ath/if_ath_tdma.c:442:50: error: format specifies type 'unsigned long long' but the argument has type 'u_int64_t' (aka 'unsigned long') [-Werror,-Wformat] > (unsigned long long) rs->rs_tstamp, rstamp, tsf, txtime, > ^~~ > /data/src/sys/dev/ath/if_ath_debug.h:97:34: note: expanded from macro 'DPRINTF' > device_printf(sc->sc_dev, fmt, __VA_ARGS__); \ > ^ > /data/src/sys/dev/ath/if_ath_tdma.c:443:6: error: format specifies type 'unsigned long long' but the argument has type 'u_int64_t' (aka 'unsigned long') [-Werror,-Wformat] > nextslot, nextslottu, TSF_TO_TU(nextslot >> 32, nextslot)); > ^~~~~~~~ > /data/src/sys/dev/ath/if_ath_debug.h:97:34: note: expanded from macro 'DPRINTF' > device_printf(sc->sc_dev, fmt, __VA_ARGS__); \ > ^ > /data/src/sys/dev/ath/if_ath_tdma.c:446:6: error: format specifies type 'unsigned long long' but the argument has type 'uint64_t' (aka 'unsigned long') [-Werror,-Wformat] > le64toh(ni->ni_tstamp.tsf), > ^~~~~~~~~~~~~~~~~~~~~~~~~~~ > /data/src/sys/sys/endian.h:80:20: note: expanded from macro 'le64toh' > #define le64toh(x) ((uint64_t)(x)) > ^ > /data/src/sys/dev/ath/if_ath_debug.h:97:34: note: expanded from macro 'DPRINTF' > device_printf(sc->sc_dev, fmt, __VA_ARGS__); \ > ^ > /data/src/sys/dev/ath/if_ath_tdma.c:447:6: error: format specifies type 'unsigned long long' but the argument has type 'uint64_t' (aka 'unsigned long') [-Werror,-Wformat] > le64toh(ni->ni_tstamp.tsf)); > ^~~~~~~~~~~~~~~~~~~~~~~~~~~ > /data/src/sys/sys/endian.h:80:20: note: expanded from macro 'le64toh' > #define le64toh(x) ((uint64_t)(x)) > ^ > /data/src/sys/dev/ath/if_ath_debug.h:97:34: note: expanded from macro 'DPRINTF' > device_printf(sc->sc_dev, fmt, __VA_ARGS__); \ > ^ > /data/src/sys/dev/ath/if_ath_tdma.c:451:6: error: format specifies type 'unsigned long long' but the argument has type 'u_int64_t' (aka 'unsigned long') [-Werror,-Wformat] > nexttbtt, > ^~~~~~~~ > /data/src/sys/dev/ath/if_ath_debug.h:97:34: note: expanded from macro 'DPRINTF' > device_printf(sc->sc_dev, fmt, __VA_ARGS__); \ > ^ > /data/src/sys/dev/ath/if_ath_tdma.c:545:7: error: format specifies type 'unsigned long long' but the argument has type 'uint64_t' (aka 'unsigned long') [-Werror,-Wformat] > tsf, > ^~~ > /data/src/sys/dev/ath/if_ath_debug.h:97:34: note: expanded from macro 'DPRINTF' > device_printf(sc->sc_dev, fmt, __VA_ARGS__); \ > ^ > 7 errors generated. > *** [if_ath_tdma.o] Error code 1 > 1 error > *** [buildkernel] Error code 2 > 1 error > *** [buildkernel] Error code 2 > 1 error > > > > -- > // Black Lion AKA Lev Serebryakov <lev@FreeBSD.org> >help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonJZ0fHfQE%2Bk2Bp-VaYgMhwt7bgGT7r-iCRRWnT6KmZYw>