search for: st7

...one from the same brand (TS-Shara) and it uses a USB cable. I found the following: T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 3 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0483 ProdID=0035 Rev= 2.00 S: Manufacturer=STMicroelectronics S: Product=ST7 RS232 USB BRIDGE C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 20mA I:* If#= 0 Alt= 0 #EPs= 2 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms E: Ad=02(O) Atr=03(Int.) MxPS= 8 Ivl=10ms And lsusb -v: Bus 001 Device 003: ID 0483:0035 SGS Thomson Microelectronics Devi...

...ot;NI","OL"),InVoice =c("4","Y")))) 4 list(ConID=c("2","7","IO"),ConRes = c("Res","Qty"),ConVal =c("Wno", "ip")) list(PassID =1,Name ="RT",Name1 ="RR",PassIt="st7,st9") list(Trnid=c("1", "3"),Trncont=c("yt","re"),EmpAddInfo=list(list(CohID =c("Ly","qp"),InVoice =c("2","P")))) Expected data frame. ID ConID ConRes ConVal PassID PassIt Name Na...

Right. But there are 8 registers on the floating point stack from ST0 to ST7 and I think llvm is only using ST0 to ST6 in some code fragments. Could this be because of the assumption that X86::FP registers run from X86::FP0 to X86:FP6 ? --Aparna On Wed, May 25, 2011 at 2:28 PM, Jakob Stoklund Olesen <stoklund at 2pi.dk>wrote: > > On May 25, 2011, at 11:09...

...data, representative of my experiment. Instrument soft had no problem fitting it: x <- structure(list(SPL = structure(c(1L, 1L, 2L, 2L, 3L, 3L, 4L, 4L, 5L, 5L, 6L, 6L, 7L, 7L), .Label = c("St1", "St2", "St3", "St4", "St5", "St6", "St7"), class = "factor"), MFI = c(10755.5, 9839, 5142.5, 4857, 1510.5, 1505, 502.5, 451, 215, 195.5, 58, 57, 15, 15), nom = c(206, 206, 125, 125, 68, 68, 38, 38, 24, 24, 13, 13, 6.5, 6.5), weights = c(0.0013946353028683, 0.00152454517735542, 0.00291686922702965, 0.00308832612723904, 0.00...

On May 25, 2011, at 12:08 PM, aparna kotha wrote: > Right. But there are 8 registers on the floating point stack from ST0 to ST7 and I think llvm is only using ST0 to ST6 in some code fragments. Could this be because of the assumption that X86::FP registers run from X86::FP0 to X86:FP6 ? Yes. My guess it that the code converting from FP to ST registers sometimes needs the extra stack slot. /jakob

On May 25, 2011, at 11:09 AM, aparna kotha wrote: > Hi Guys, > > I was working on some floating point intensive benchmarks and realize that the floating point register allocation in llvm assumes that there are only 7 floating point registers in X86, whereas the hardware has 8. > > Line number > 00266 assert(Reg >= X86::FP0 && Reg <= X86::FP6 &&

Hi Aries, Thank you for your reply. I understand that the registers you mentioned should not be used at will. The problem I don't understand is why not make these registers *unallocatable*. Since in X86RegisterInfo.td, only floating point stack registers ST0 to ST7 and status flag registers are defined as not allocatable, while special registers such as ESP/EIP/EBP are defined as *allocatable but reserved *(in X86RegisterInfo.cpp). Since these registers also have special usage, why not specify them as *unallocatable, instead of allocatable but reserved?* I h...

Hi, after installing centos 4.2 I've noticed that my internal Seagate scsi DAT 72GB tape drive hasn't been recognised in /media or doesn't show up in gnome when putting in a tape. Do I need to edit fstab first or load additional modules in the kernel during startup? regards, Geert -------------- next part -------------- An HTML attachment was scrubbed... URL:

...ed the latest (v8.02.14) drivers from Qlogic for the HBA The issue I have is I am missing 2 of the 4 SDLT drives provided by the M1800 Library. The DX30 provides 6 drives, which are listed in dmesg and assigned /dev/st0->5. I would expect the SDLT's to be st6->10 but I only see up to st7 and dmesg only lists 2 Using the QLoigic SAN Surfer software all the LUN's/devices are visible to the host. FYI, I also have an old Sun220R connected to this same switch with a qlogic card; Solaris 9 has no trouble seeing all LUNs and devices. I've "googled" for a fair while...

...ting point stack registers (these are not allocatable by the // register allocator - the floating point stackifier is responsible // for transforming FPn allocations to STn registers) def RST : RegisterClass<"X86", [f64], 32, [ST0, ST1, ST2, ST3, ST4, ST5, ST6, ST7]> { let MethodProtos = [{ iterator allocation_order_end(const MachineFunction &MF) const; }]; let MethodBodies = [{ RSTClass::iterator RSTClass::allocation_order_end(const MachineFunction &MF) const { return begin(); } }]; } Is the "begin()&...

Hi Guys, I was working on some floating point intensive benchmarks and realize that the floating point register allocation in llvm assumes that there are only 7 floating point registers in X86, whereas the hardware has 8. Line number 00266 assert(Reg >= X86::FP0 && Reg <= X86::FP6 && "Expected FP register!"); of X86FloatingPoint.cpp. Is there any reason for

...USB transport layer for Megatec protocol driver [megatec_usb] Andrey Lelikov (c) 2006, Alexander Gordeev (c) 2006-2007, Jon Gough (c) 2007 debug level is '2' Checking device (0483/0035) (/dev/usb//dev/ugen2.2) - VendorID: 0483 - ProductID: 0035 - Manufacturer: STMicroelectronics - Product: ST7 RS232 USB BRIDGE - Serial Number: unknown - Bus: /dev/usb Trying to match device Device does not match - skipping Checking device (0000/0000) (/dev/usb//dev/ugen4.1) - VendorID: 0000 - ProductID: 0000 - Manufacturer: Intel - Product: EHCI root HUB - Serial Number: unknown - Bus: /dev/usb Trying to...

Hi! I don't know how I missed it before, but "bestups" seems to implement mostly the same protocol as megatec. Is anybody out there using this driver willing to try "megatec" to see if it works? AFAIK, the only difference seems to be the command that gets the UPS identification data ("I" on "megatec", "ID" on "bestups"), but

Hi! I don't know how I missed it before, but "bestups" seems to implement mostly the same protocol as megatec. Is anybody out there using this driver willing to try "megatec" to see if it works? AFAIK, the only difference seems to be the command that gets the UPS identification data ("I" on "megatec", "ID" on "bestups"), but

...quot;); switch (IntTok.getIntVal()) { case 0: RegNo = X86::ST0; break; case 1: RegNo = X86::ST1; break; @@ -401,30 +463,30 @@ bool X86ATTAsmParser::ParseRegister(unsigned &RegNo, case 5: RegNo = X86::ST5; break; case 6: RegNo = X86::ST6; break; case 7: RegNo = X86::ST7; break; - default: return Error(IntTok.getLoc(), "invalid stack index"); + default: return Parser->Error(IntTok.getLoc(), "invalid stack index"); } - if (getParser().Lex().isNot(AsmToken::RParen)) - return Error(Parser.getTok().getLoc(), "expecte...