similar to: Wireless USB adaptor recommendation

Displaying 20 results from an estimated 300 matches similar to: "Wireless USB adaptor recommendation"

2010 Apr 06
3
wifi
Hi folks I'm trying to use a Netgear WG111-2 USB-wifi adapter on a Centos 5.3 Box. Someone has done it? It seems not to be supported by the kernel. Thanks David -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20100406/5e7e2f3d/attachment-0003.html>
2014 Jan 14
2
Laptop recommendation
Hello, I am looking for a laptop with the following specs: Built-in GSM module Trusted platform module Support for these modules, as for the network (Ethernet + WiFi) for RHEL/Centos6. I tested Lenovo W540, and the WiFi is not detected. lspci shows: 03:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device 818b I came across
2011 Sep 02
4
[LLVMdev] Some questions on SelectionDAG
Hi, all I am studying the ARM backend on SelectionDAG, I have some following questions: 1. Each operator of SDNode in SelectionDAG is required to be defined by SDNode<ISD::XXX,XXX,XXX> in .td file, right? But several operators are not defined in .td file, why? (e.g., ISD::BR_CC, ISD::CopyToReg, ISD::AssertSext) 2. The MVT::glue value is used to ensure two nodes are scheduled
2006 Dec 30
7
howto give DomU the pcmcia wlan card from Dom0 ?
hi list members, my goal is to make one of my DomU''s act as a wireless accesspoint... So, i need it to have access to the pcmcia wlan card attached to dom0. But how ? when i give the pci=[] option to the domU config file its shows up with lspci but i cant use it... (on debian with module-assistent get rt2x00 in de DomU) Is it possible or would it be better to use a more direct interface
2020 Jan 15
2
Encode target-abi into LLVM bitcode for LTO.
David Blaikie <dblaikie at gmail.com> 於 2020年1月14日 週二 上午2:15寫道: > > > On Mon, Jan 13, 2020 at 6:12 AM Zakk <zakk0610 at gmail.com> wrote: > >> >> >> David Blaikie via llvm-dev <llvm-dev at lists.llvm.org> 於 2020年1月11日 週六 >> 上午2:03寫道: >> >>> Ah, OK - thanks for walking me through that. >>> >>> Fair enough, I
2020 Jan 07
2
Encode target-abi into LLVM bitcode for LTO.
> On Jan 6, 2020, at 14:29, David Blaikie via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > > On Mon, Jan 6, 2020 at 5:58 AM Zakk <zakk0610 at gmail.com <mailto:zakk0610 at gmail.com>> wrote: > > > David Blaikie <dblaikie at gmail.com <mailto:dblaikie at gmail.com>> 於 2020年1月6日 週一 下午2:23寫道: > If this is something that can vary per
2012 Jan 07
1
Problems with AWUS036H usb wirless nic under CentOS 6.2
Hi all, I have problems with a wireless usb adapter (AWUS036H) under CentOS 6.2 x86_64 machine. Sometimes, randomly, it loses wireless connection and never back. I need to do an ifdown and then an ifup, but sometimes works and sometimes not. If I am not wrong this adapter uses rtl8187 chip ... Somebody knows what can I do?? Under Windows 2008 R2 server works perfect ... Thanks. -- CL
2020 Jan 27
2
Encode target-abi into LLVM bitcode for LTO.
On Mon, Jan 20, 2020 at 8:05 AM Sam Elliott via llvm-dev < llvm-dev at lists.llvm.org> wrote: > To follow up on this issue: > > Our plan is still to encode `target-abi` into the module flags for RISC-V > LLVM IR modules. As was pointed out earlier in this thread, the function > lowering in Clang is slightly different for the ABIs which support hardware > floating point.
2007 May 15
3
Introduction
Hi, I'm a 40-year old sysadmin living in Montpezat, a small village in the sunny south of France. I'm a Linux user since 2001, when I made my first steps on a 486 with a Slackware 7.1 CD. I've tried maybe two dozen distributions, but I've stayed mostly with Slackware and Debian. Since last summer, I work as a sysadmin for our "Communaut? de Communes", a group of 16
2013 Oct 16
3
[LLVMdev] MI scheduler produce badly code with inline function
Hi Andy, thanks for your help!! The scheduled code by method A is same as B when using the new machine model. it's make sense, but there is the another problem, the scheduled code is badly. load/store instruction always reuse the same register Source: #define N 2000000 static double b[N], c[N]; void Scale () { double scalar = 3.0; for (int j=0;j<N;j++) b[j] =
2020 Jan 06
2
Encode target-abi into LLVM bitcode for LTO.
David Blaikie <dblaikie at gmail.com> 於 2020年1月6日 週一 下午2:23寫道: > If this is something that can vary per file in a compilation and resolve > correctly when one object file is built with one ABI and another object > file is built with a different ABI (that seems to be antithetical to the > concept of "ABI" Though) - then it should be a subtarget feature. > > ABI is
2020 Jan 27
2
Encode target-abi into LLVM bitcode for LTO.
On Mon, Jan 27, 2020 at 3:04 PM Eric Christopher <echristo at gmail.com> wrote: > > > On Mon, Jan 27, 2020 at 2:56 PM David Blaikie via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> >> >> On Mon, Jan 20, 2020 at 8:05 AM Sam Elliott via llvm-dev < >> llvm-dev at lists.llvm.org> wrote: >> >>> To follow up on this issue:
2013 Oct 16
0
[LLVMdev] MI scheduler produce badly code with inline function
On Oct 15, 2013, at 9:28 PM, Zakk <zakk0610 at gmail.com> wrote: > Hi Andy, thanks for your help!! > The scheduled code by method A is same as B when using the new machine model. > it's make sense, but there is the another problem, the scheduled code is badly. > > load/store instruction always reuse the same register I filed PR17593 with this information. However, I
2020 Jan 13
2
Encode target-abi into LLVM bitcode for LTO.
David Blaikie via llvm-dev <llvm-dev at lists.llvm.org> 於 2020年1月11日 週六 上午2:03寫道: > Ah, OK - thanks for walking me through that. > > Fair enough, I think I understand the issue/tradeoff now - and that the > other module level metadata don't currently influence the target > configuration at this level? > > I'm not sure, I only know that the target-abi is decided
2020 Jan 10
2
Encode target-abi into LLVM bitcode for LTO.
I also work on the RISC-V backend, and have been doing a little work on the ELF psABI document for RISC-V. I agree that, conceptually, the psABI choice should be in the module metadata. Zakk, however, has discovered a phase ordering issue within LLVM that relates to this approach. The phase ordering problem is that the LTO backend is currently setup without interrogating the current module for
2015 May 11
1
Packet compression benchmark
On Sun, May 10, 2015 at 08:16:54PM -0400, Darik Horn wrote: > > LZ4 is supposed > > to be a very fast compression algorithm, especially when it comes to > > decompression. I did a quick benchmark with zlib, LZO and LZ4. Now, > > there are many benchmarks you can find online, but most of them deal > > with compressing large files. Tinc on the other hand has to
2020 Jan 09
2
Encode target-abi into LLVM bitcode for LTO.
Right. I think that's what we ended up doing rather than a more general attribute on the module itself. *shrugs* Probably ok? I'd probably prefer not to have to have target code to do the evaluation if possible, but everything is weird and an edge case - mips abis more than some :) -eric On Wed, Jan 8, 2020 at 8:58 AM David Blaikie <dblaikie at gmail.com> wrote: > Oh, I should
2020 Jan 07
2
Encode target-abi into LLVM bitcode for LTO.
> On Jan 7, 2020, at 13:57, David Blaikie <dblaikie at gmail.com> wrote: > > > > On Mon, Jan 6, 2020 at 6:05 PM Daniel Sanders <daniel_l_sanders at apple.com <mailto:daniel_l_sanders at apple.com>> wrote: > > >> On Jan 6, 2020, at 14:29, David Blaikie via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
2020 Jan 08
3
Encode target-abi into LLVM bitcode for LTO.
On Tue, Jan 7, 2020 at 5:27 PM Eric Christopher <echristo at gmail.com> wrote: > > > On Tue, Jan 7, 2020 at 3:18 PM Daniel Sanders via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> >> >> On Jan 7, 2020, at 13:57, David Blaikie <dblaikie at gmail.com> wrote: >> >> >> >> On Mon, Jan 6, 2020 at 6:05 PM Daniel Sanders
2011 May 03
2
[LLVMdev] Loop-Unroll optimization
Hi, you need to run some optimization passes first. (like -O2) 2011/5/3 Manish Gupta <mgupta.iitr at gmail.com> > I just want to try loop-unroll and see corresponding changes in the bitcode > file. For that any loop will do. Have you been able to test llvm loop-unroll > successfully? > > > On Mon, May 2, 2011 at 10:04 PM, Yuan Pengfei <coolypf at qq.com> wrote: >