search for: aths

Displaying 20 results from an estimated 454 matches for "aths".

Did you mean: paths
2011 Jan 16
1
Atheros AR9287 PCI passthrough issue
Hi, i''m trying to use PCI passthrough feature on Xen 4.0 but it fails on my Wireless card. I use Xen 4.0 on a Debian 6.0 (package from repo) and try to passthrough the following PCI device root@omega:~# dpkg -l | grep xen ii libxenstore3.0 4.0.1-1 Xenstore communications library for Xen ii linux-image-2.6.32-5-xen-amd64 2.6.32-30 Linux 2.6.32 for 64-bit PCs, Xen dom0 support ii
1999 Aug 25
1
Vorbis/Lame
Hi, I think that it would be a good thing to know more about those 2 projects (and also the future patent free format). I think that many people as me know about Lame, but not about Vorbis, and vice-versa. It would be fine that someone (perhaps the maintainer) of every project would introduce to both group of people those projects. 2 things would be interesting (to my mind): - to know about the
2009 Mar 23
3
Replacing a few variable values within a DataFrame...
I would like to replace a few varaibles within a data frame. For example, in the dataframe below (contrived) I would like to replace the current housesize value only if the Location is HSV. However, I would like to leave the other values intact. I tried "ifelse", but I don't really need the else condition. test_data2_df<-data.frame(Variables=c("SQR
2020 Feb 24
3
[RESEND PATCH v2 9/9] ath5k: Constify ioreadX() iomem argument (as in generic implementation)
On Thu, Feb 20, 2020 at 10:48:33AM +0100, Jiri Slaby wrote: > On 19. 02. 20, 18:50, Krzysztof Kozlowski wrote: > > The ioreadX() helpers have inconsistent interface. On some architectures > > void *__iomem address argument is a pointer to const, on some not. > > > > Implementations of ioreadX() do not modify the memory under the address > > so they can be
2010 Aug 25
1
Can't compile ath(4) into kernel
My laptop's kernel config file reads: device wlan # 802.11 support device ath device ath_ar5212 device ath_rate_onoe Config raises no objections and the compilation succeeds, but linking the kernel breaks: ... linking kernel.debug ah.o(.text+0x218): In function `ath_hal_rfprobe':
2008 Nov 02
5
Issue with domains
I am running Dovecot 1.0.10 and have it working great on ender.ath.cx (my free DynDNS.com subdomain), but recently I registered lemcoe.com and pointed it to the same IP address as ender.ath.cx. The problem is, only e-mail sent to the @ender.ath.cx works. If it is send it to @lemcoe.com, I don't know where it goes. I get no errors either. How can I get Dovecot to recognize both domains? TIA.
2020 Feb 19
1
[RESEND PATCH v2 9/9] ath5k: Constify ioreadX() iomem argument (as in generic implementation)
The ioreadX() helpers have inconsistent interface. On some architectures void *__iomem address argument is a pointer to const, on some not. Implementations of ioreadX() do not modify the memory under the address so they can be converted to a "const" version for const-safety and consistency among architectures. Signed-off-by: Krzysztof Kozlowski <krzk at kernel.org> Acked-by:
2015 Oct 30
2
Vectorizing structure reads, writes, etc on X86-64 AVX
I am a first time poster, so I apologize if this is an obvious question or out of scope for LLVM. I am an LLVM user. I don't really know anything about hacking on LLVM, but I do know a bit about compilation generally. I am on x86-64 and I am interested in structure reads, writes, and constants being optimized to use vector registers when the alignment and sizes are right. I have created a
2006 Jun 02
1
ath(4) for D-Link G520M on 5.5-R?
I just got the D-Link DWL-G520M PCI wireless card. I'm not interested in super-G or any other post-802.11b feature in particular; the reason I got it was because the marketing materials hinted that (at least some revision of it) had the Atheros chipset. It isn't recognized at all by ath(4) on 5.5. Here is the pciconf -lv section: none0@pci0:14:0: class=0x020000 card=0x3a681186
2009 Apr 11
1
kernel: problems compiling if_ath.c
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I did a cvsup for RELENG_7 earlier today. # uname -a FreeBSD polo.example.org 7.1-STABLE FreeBSD 7.1-STABLE #8: Sat Apr 11 18:50:17 EDT 2009 dan@polo.example.org:/usr/obj/usr/src/sys/PHENOM amd64 No idea what went wrong here. Clues please. cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g - -Wall -Wredundant-decls
2015 Nov 03
2
Vectorizing structure reads, writes, etc on X86-64 AVX
Thank you for your reply. FWIW, I wrote the .ll by hand after taking the C program, using clang to emit the llvm and seeing the memcpy. The memcpy version that clang generates gets compiled into assembly that uses the large sequence of movs and does not use the vector hardware at all. When I started debugging, I took that clang produced .ll and started to write it different ways trying to get
2009 Aug 17
1
Multiple comparison on lme model with 2 fixed factors
Hi! I'm a bit lost while performing multiple comparisons on a lme model of that type: lmeglu=lme(glucose~Ath*tim,random=~1|Vol,na.action=na.omit,data=data) multc = glht(lmeglu, linfct = mcp(Ath = "Tukey", tim = "Tukey")) This works fine for identifying the effect of each factor. However, when I look for their interactions, l only obtain error messages. For example this
2020 Feb 24
0
[RESEND PATCH v2 9/9] ath5k: Constify ioreadX() iomem argument (as in generic implementation)
On Mon, Feb 24, 2020 at 01:54:00PM +0100, Geert Uytterhoeven wrote: > Hi Krzysztof, > > On Mon, Feb 24, 2020 at 1:47 PM Krzysztof Kozlowski <krzk at kernel.org> wrote: > > On Thu, Feb 20, 2020 at 10:48:33AM +0100, Jiri Slaby wrote: > > > On 19. 02. 20, 18:50, Krzysztof Kozlowski wrote: > > > > The ioreadX() helpers have inconsistent interface. On some
2020 Feb 24
0
[RESEND PATCH v2 9/9] ath5k: Constify ioreadX() iomem argument (as in generic implementation)
Hi Krzysztof, On Mon, Feb 24, 2020 at 1:47 PM Krzysztof Kozlowski <krzk at kernel.org> wrote: > On Thu, Feb 20, 2020 at 10:48:33AM +0100, Jiri Slaby wrote: > > On 19. 02. 20, 18:50, Krzysztof Kozlowski wrote: > > > The ioreadX() helpers have inconsistent interface. On some architectures > > > void *__iomem address argument is a pointer to const, on some not. >
2009 Feb 23
3
Recommended wireless card (or is there a chance to get either iwi or ath fixed)?
Hi, after some time without FreeBSD I installed 7.1 on an IBM Thinkpad T30 (with ZFS root on encrypted geli, works great). Config is: FreeBSD hasking.alashan.nongo 7.1-STABLE FreeBSD 7.1-STABLE #3: Thu Feb 5 21:10:45 CET 2009 root@hasking.alashan.nongo:/usr/obj/usr/src/sys/HASKING i386 I tried using my ath based D-Link DWL G650, which still seems to have some issues in regard to interrupt
2015 Nov 03
2
Vectorizing structure reads, writes, etc on X86-64 AVX
----- Original Message ----- > From: "Sanjay Patel via llvm-dev" <llvm-dev at lists.llvm.org> > To: "Jay McCarthy" <jay.mccarthy at gmail.com> > Cc: "llvm-dev" <llvm-dev at lists.llvm.org> > Sent: Tuesday, November 3, 2015 12:30:51 PM > Subject: Re: [llvm-dev] Vectorizing structure reads, writes, etc on X86-64 AVX > > If the
2020 Feb 24
0
[RESEND PATCH v2 9/9] ath5k: Constify ioreadX() iomem argument (as in generic implementation)
From: Geert Uytterhoeven > Sent: 24 February 2020 12:54 > To: Krzysztof Kozlowski <krzk at kernel.org> ... > > > > diff --git a/drivers/net/wireless/ath/ath5k/ahb.c b/drivers/net/wireless/ath/ath5k/ahb.c > > > > index 2c9cec8b53d9..8bd01df369fb 100644 > > > > --- a/drivers/net/wireless/ath/ath5k/ahb.c > > > > +++
2008 May 26
0
ath network (wifi) driver (Fujitsu Siemens Amilo Pro V3515 laptop)
Hello Sam, I've got a Fujitsu Siemens Amilo Pro V3515 laptop, with a builtin autheros-wifi card, but I can't get it working. I am running FreeBSD 7.0-STABLE, I don't know whether it works in -CURRENT. Over here I have the dmesg: http://junk.quis.cx/VNViVksv/blackbox.dmesg.txt I haven't compiled it in, it didn't boot that way (kernel panic iirc). When I kldload if_ath I get
2008 May 13
1
Hard(?) lock when reassociating ath with wpa_supplicant on RELENG_7
I seem to be able to lock my machine by going into wpa_cli and asking it to 'reassoc'. The reason for question mark after "hard" is that debug information (caused by wlandebug and athdebug) is being printed on the console. The only way to get machine's attention is to hold power button for 8 seconds. Note: manual reassociation is just the handy way to reproduce the problem
2015 Nov 04
2
Vectorizing structure reads, writes, etc on X86-64 AVX
Hi Jay - I see the slow, small accesses using an older clang [Apple LLVM version 7.0.0 (clang-700.1.76)], but this looks fixed on trunk. I made a change that comes into play if you don't specify a particular CPU: http://llvm.org/viewvc/llvm-project?view=revision&revision=245950 $ ./clang -O1 -mavx copy.c -S -o - ... movslq %edi, %rax movq _spr_dynamic at GOTPCREL(%rip),