search for: tx1

...ctober 2016 at 19:02, Justin Lebar via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Hi, it looks like you're compiling CUDA for an ARM host? This is not > a configuration we have tested, nor is it something we have the > capability of testing at the moment. Hi Justin, NVidia TX1 is the AArch64 Jetson board with proper GPU (we use those). > You may be able to make it work by providing the appropriate -isystem > flags to clang so that it can find your headers, but who knows, it may > be more complicated than that. We don't use them for their GPU, so I don'...

> NVidia TX1 is the AArch64 Jetson board with proper GPU (we use those). Sure, I believe that others use this configuration. I was saying, "we", being, myself and those whom I work closely with, do not. Sorry if that wasn't precise. It is still not clear to me if the original poster is compili...

1. Yes, you both are right. My platform is Jetson TX1, AArch64. 2. And I obtain all the necessary files for TX1 by JetPack from the host(X86) and so `nvcc` can work rightly. 3. Althrough I can compile LLVM3.9 on TX1, I can not compile the CUDA program using `clang` tools. The error is "sys/cedfs.h no such file". 2016-10-28 4:07 GMT+08:00...

On Sun, Oct 16, 2016 at 11:39 PM, C Bergström <cbergstrom at pathscale.com> wrote: > Is there any particular reason you're not using the open source NVIDIA > Tegra drivers? > > This is what is being used for the TX1 (Sorry I don't know if it's the > same for the TK1) > http://nv-tegra.nvidia.com/gitweb/?p=linux-3.10.git;a=summary That's ... not particularly helpful. Presumably non-upstream and the fact that it's ancient are turn-offs. Either way, he seems to have a desire to try to get n...

...s the differential signal components then you're right about the wiring. In either case you're wrong with respect to the pairing. :-) Sorry, I am used to the way NEC documents their PBXs and this is what they call it. The Zytrax website documents it like this: Pin: Signal: 1 Rx1 2 Rx2 4 Tx1 5 Tx2 (http://www.zytrax.com/tech/layer_1/cables/tech_rs232.htm - bottom of page) So my question about a "real" T1 cable isn't specifically about a crossover cable, although the principle will still apply. I was talking about using Cat5/5e 4-pair cable (*not* a pre-made Ethernet pat...

Hi all, I compiled the *llvm3.9* source code on the *Nvidia TX1* board. And now I am following the document in the docs/CompileCudaWithLLVM.rst to compile cuda program with clang++. However, when I compile `axpy.cu` using `nvcc`, *nvcc* can generate the correct the binary; while compiling `axpy.cu` using clang++, the detailed command is `clang++ axpy.cu -o ax...

...,0,4095) nx2<-runif(nnoise,0,4095) ny1<-runif(nnoise,0,4095) ny2<-runif(nnoise,0,4095) #generate signal dots sx1<-runif(nsignal,0,4095) sx2<-sx1 sy1<-runif(nsignal,0,4095) sy2<-sy1+jump sy2<-ifelse(sy2>4095, sy2-4096,sy2) #wrap around #put noise and signal dots together tx1<-c(nx1,sx1) tx2<-c(nx2,sx2) ty1<-c(ny1,sy1) ty2<-c(ny2,sy2) #compute distance to nearest neighbour (x and y) in frame 2 #for each dot in frame 1 for(i in 1:ntotal) { rbest<-2*(4096^2) for(j in 1:ntotal) { xd<-tx2[i]-tx1[j] yd<-ty2[i]-ty1[j] rr<-xd^2 + yd^2 if(...

...P_DATA) >> 32); + PUSH_DATA (push, (pNv->scratch->offset + PVP_DATA)); + BEGIN_1IC0(push, NVC0_3D(CB_POS), 3 * (4 + 2 + 2) + 1); + PUSH_DATA (push, 0x80); + + PUSH_DATAf(push, sx1); + PUSH_DATAf(push, sy1); + PUSH_DATAf(push, 0); + PUSH_DATAf(push, 1); + PUSH_DATAf(push, tx1); + PUSH_DATAf(push, ty1); + PUSH_DATAf(push, 0); + PUSH_DATAf(push, 0); + + PUSH_DATAf(push, sx2+(sx2-sx1)); + PUSH_DATAf(push, sy1); + PUSH_DATAf(push, 0); + PUSH_DATAf(push, 1); + PUSH_DATAf(push, tx2+(tx2-tx1)); + PUSH_DATAf(push, ty1); + PUSH_DATAf(push, 0); + PUSH_DATAf(...

...P_DATA) >> 32); + PUSH_DATA (push, (pNv->scratch->offset + PVP_DATA)); + BEGIN_1IC0(push, NVC0_3D(CB_POS), 3 * (4 + 2 + 2) + 1); + PUSH_DATA (push, 0x80); + + PUSH_DATAf(push, sx1); + PUSH_DATAf(push, sy1); + PUSH_DATAf(push, 0); + PUSH_DATAf(push, 1); + PUSH_DATAf(push, tx1); + PUSH_DATAf(push, ty1); + PUSH_DATAf(push, 0); + PUSH_DATAf(push, 0); + + PUSH_DATAf(push, sx2+(sx2-sx1)); + PUSH_DATAf(push, sy1); + PUSH_DATAf(push, 0); + PUSH_DATAf(push, 1); + PUSH_DATAf(push, tx2+(tx2-tx1)); + PUSH_DATAf(push, ty1); + PUSH_DATAf(push, 0); + PUSH_DATAf(...

...h, (pNv->scratch->offset + PVP_DATA)); > + BEGIN_1IC0(push, NVC0_3D(CB_POS), 3 * (4 + 2 + 2) + 1); > + PUSH_DATA (push, 0x80); > + > + PUSH_DATAf(push, sx1); > + PUSH_DATAf(push, sy1); > + PUSH_DATAf(push, 0); > + PUSH_DATAf(push, 1); > + PUSH_DATAf(push, tx1); > + PUSH_DATAf(push, ty1); > + PUSH_DATAf(push, 0); > + PUSH_DATAf(push, 0); > + > + PUSH_DATAf(push, sx2+(sx2-sx1)); > + PUSH_DATAf(push, sy1); > + PUSH_DATAf(push, 0); > + PUSH_DATAf(push, 1); > + PUSH_DATAf(push, tx2+(tx2-tx1)); > + PUSH_DATAf(pu...

Hello everyone, recently I've found something I consider a bug. Correct me if I'm wrong, but I always thought that Linux' EOL is 0x0A. Imagine my surprise when I saw that all messages that are being output on to the stderr (on any Linux I've tested - Fedora and Ubuntu) are terminated with 0x0D, 0x0A. Maybe that's standard behaviour of all stderr messages in all Linux

...priate -isystem flags to clang so that it can find your headers, but who knows, it may be more complicated than that. Regards, -Justin On Wed, Oct 26, 2016 at 9:59 PM, 李阳 via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Hi all, > > I compiled the llvm3.9 source code on the Nvidia TX1 board. And now I am > following the document in the docs/CompileCudaWithLLVM.rst to compile cuda > program with clang++. > > However, when I compile `axpy.cu` using `nvcc`, nvcc can generate the > correct the binary; > > while compiling `axpy.cu` using clang++, the detailed com...

...irkin <imirkin at alum.mit.edu> wrote: > On Sun, Oct 16, 2016 at 11:39 PM, C Bergström <cbergstrom at pathscale.com> wrote: >> Is there any particular reason you're not using the open source NVIDIA >> Tegra drivers? >> >> This is what is being used for the TX1 (Sorry I don't know if it's the >> same for the TK1) >> http://nv-tegra.nvidia.com/gitweb/?p=linux-3.10.git;a=summary > > That's ... not particularly helpful. Presumably non-upstream and the > fact that it's ancient are turn-offs. Either way, he seems to have a...

...w-1/t*x_t #x_tilde ist auch eine Matrix ####X_aus=matrix(X_ausgew) V1=R%*%(S%*%y_aus-x_tilde%*%beta) V11=t(V1) V2=V11%*%J_n V_tilde=V2%*%V1 sumterm=sumterm+V_tilde a=b+1 } -((n*t)/2)*log(2*pi*sigm_sq)+t*(log(det_S)+log(det_R))-1/(2*sigm_sq)*sumterm } where beta is a matrix (2x1), X is a matrix (n*tx1) and y is numeric with length nt. My error message is: X_ausgew%*%beta - non-conformable arguments Can anybody help me? THANKS -- View this message in context: http://n4.nabble.com/error-in-a-function-tp1585792p1585792.html Sent from the R help mailing list archive at Nabble.com.

I hope this is a good mailing list for this problem. I have a Jetson TK1 board and I am trying to get the nouveau drivers running on it without success. I am using the following: Nouveau linux kernel 4.8.0-rc4+ Nouveau DRM git master xf86-video-nouveau git master Gnurou xserver git branch GK20A My base system is Debian. When I try to start X I get: X: drmmode_display.c:783:

Dear R users, I have a linear model of the kind outcome ~ treatment + covariate where 'treatment' is a factor with three levels ("0", "1", and "2"), and the covariate is continuous. Treatments "1" and "2" both have regression coefficients significantly different from 0 when using treatment contrasts with treatment "0" as the

...know why it is not working. I even tried a similar example in UCLA webpage: http://www.ats.ucla.edu/stat/R/faq/sort.htm :it also does not seem to work. "*sort1.hsb2 <- hsb2[order(read) , ]"* Do you have any idea how to deal with this problem?? Thank you so much. -Hyo > colnames(ttx1) [1] "longitude 1" "longitude 2" "longitude 3" "longitude 4" "longitude 5" [6] "longitude 6" "longitude 7" "longitude 8" "longitude 9" "longitude 10" [11] "longitude 11" "lon...

...dea to have an extra tab character after the last column - except for the header line. As explained in the help page, read.delim now assumes that the first column contains the row.names (which is not even wrong) but now and all col.names get shiftet by one column. Example: infile <- 'sample\tx1\n1\tA\t\n2\tB\t\n3\tA\t' read.delim(textConnection(infile)) sample x1 1 A NA 2 B NA 3 A NA So I set row.names to NULL because the man page said "Using ?row.names = NULL? forces row numbering.". Now the row.names really are numbered automatically but I get a &...

...> > > > #plus router > > > > > > licznik=$[$licznik+1] > > > > > > > > > > > > echo number of users to $licznik > > > > > > #counting rate > > > > > > rx1=$[$rxmax-10] > > > > > > tx1=$[$txmax-10] # dla klasy domyslnej > > > > > > rxmin=$[$rx1/$licznik] > > > > > > txmin=$[$tx1/$licznik] > > > > > > echo rx $rxmin tx $txmin > > > > > > #echo $rxmin > > > > > > #root classes > > > &...

I have a pdf file that I would like to parse into R: http://www.williams.edu/Registrar/geninfo/faculty.pdf For now, I open the file in Acrobat by hand, then save it "as text" and then use readLines(). That works fine but a) I am concerned that some information may be lost and b) I may be doing this a lot, so I would rather have R grab the information from the pdf file directly. So: is