search for: 12883

Displaying 8 results from an estimated 8 matches for "12883".

Did you mean: 1283
2011 Jan 03
1
VoIP PoE phones for restaurant
...yself? In the future we plan to have 7 phones in the house. I'm considering what kind of PoE switch I should purchase. I have 3 PoE access points (for two separate LANs). I've been considering th HP ProCurve 2610-24/12PWR Switch (J9086A) ( http://h10010.www1.hp.com/wwpc/il/en/sm/WF06b/12883-12883-3445275-427605-427605-3751584-3658873.html ) It's got 12 PoE ports, it's managed, and it looks like I can pick one up for under $500. Any help is appreciated. -Andy
2008 Aug 26
1
bug in package chron (PR#12599)
...NULL) (158.182.1.30) Dear Author I have run into a trouble in using chron package The data frame: a date time_fut expiry_day bid ask trade_day 1 2004-09-01 09:45:00 2004-10 12860 12889 38 2 2004-09-01 09:45:01 2004-10 12885 12890 38 3 2004-09-01 09:45:04 2004-10 12883 12887 38 4 2004-09-01 09:45:05 2004-10 12878 12886 38 5 2004-09-01 09:45:06 2004-10 12881 12887 38 6 2004-09-01 09:45:08 2004-10 12881 12882 38 7 2004-09-01 09:45:11 2004-10 12881 12884 38 8 2004-09-01 09:45:12 2004-10 12882 12884 38 9 2004-0...
2013 Nov 12
0
[LLVMdev] Implementing the ldr pseudo instruction in ARM integrated assembler
...the asm parser, so I expect > more detailed comments from others to follow. > > Cheers, > Amara > > -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-PR17769-Initial-implementation-of-ldr-pseudo.patch Type: application/octet-stream Size: 12883 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131112/2200e8ac/attachment.obj>
2013 Nov 12
2
[LLVMdev] Implementing the ldr pseudo instruction in ARM integrated assembler
Hi David, Thanks for your efforts here. I have a few comments on your patch, although I realise it's still a work in progress. +class ConstantPool { + MCSymbol *Label; + typedef std::vector<const MCExpr*> EntryVecTy; Use a SmallVector here? + MCSymbol *getLabel() {return Label;} + size_t getNumEntries() {return Entries.size();} + const MCExpr *getEntry(size_t Num) {return
2004 Jun 21
2
libao NAS compilation and playback issues
...running ./configure with "--enable-nas" in order to get configure to make a correct NAS plugin Makefile. The config.log file showed that the test for NAS was failing due to linking errors regarding dependencies in libaudio: configure:12853: checking for AuOpenServer in -laudio configure:12883: cc -o conftest -xO4 -fast -w -fsimple -native -xcg92 -g -I/users/prazak/.../nas/1.6/usr/openwin/include -I/users/prazak/.../libao/0.8.5/include -I/users/prazak/.../libogg/1.1/include -I/users/prazak/.../libvorbis/1.0.1/include -I/users/prazak/.../curl/7.10.8/include conftest.c -laudio -lXau -L/u...
2004 Jan 15
0
2.2.8a as member server of Win2000?
...esolve_wins: Attempting wins lookup for name papas-server<0x20> resolve_wins: WINS server == <192.168.0.1> bind succeeded on port 0 Sending a packet of len 50 to (192.168.0.1) on port 137 Received a packet of len 62 from (192.168.0.1) port 137 nmb packet from 192.168.0.1(137) header: id=12883 opcode=Query(0) response=Yes header: flags: bcast=No rec_avail=Yes rec_des=Yes trunc=No auth=Yes header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0 answers: nmb_name=PAPAS-SERVER<20> rr_type=32 rr_class=1 ttl=0 answers 0 char `..... hex 6000C0A80001 Got a positive...
2009 Jul 12
13
pv_ops kernel and nvidia binary driver
Just wondering what it will take to get the nvidia binary driver working on a pv_ops kernel. It makes it difficult to debug without the source to the nvidia driver, but I think it should be possible to get it to work without changing the binary driver. If the dom0 kernel had access to all the resources that a bare metal kernel did, then it should work right? I''m using Jeremy''s
2009 Jul 12
13
pv_ops kernel and nvidia binary driver
Just wondering what it will take to get the nvidia binary driver working on a pv_ops kernel. It makes it difficult to debug without the source to the nvidia driver, but I think it should be possible to get it to work without changing the binary driver. If the dom0 kernel had access to all the resources that a bare metal kernel did, then it should work right? I''m using Jeremy''s