--- Log opened Fri Apr 11 00:00:00 2014 | ||
Limb | well... | 00:18 |
---|---|---|
Limb | I can get openocd to connect if i hold the reset button down | 00:18 |
Limb | wonder if its a driven high button -_- | 00:18 |
julzmb_ | Are there any services where a user pays for ssh access and the server has comercial EDA tools on it? | 02:04 |
julzmb_ | I am mainly looking for VCS access | 02:05 |
Findeton | wow I finally got it working | 05:27 |
Findeton | I'll upload the changes that I had to do so that no one needs to do it again | 05:27 |
stekern | to the old toolchain? | 05:29 |
stekern | for the textinfo problem? | 05:31 |
stekern | -t | 05:32 |
olofk_ | julzmb_: You could see if plunify has VCS | 06:21 |
olofk_ | Limb: I'm writing wb_ram to replace ram_wb. They should be functionally equivalent, but the new one should be more modular | 06:40 |
olofk_ | Has anyone investigated using crosstool-ng for toolchain building? | 07:56 |
stekern | hmm, looking at the mor1kx code, the using the F flag actually makes a lot more sense I think... | 08:29 |
stekern | with the branch prediction, all scary paths are already gone | 08:30 |
stekern | s/the using/using | 08:30 |
stekern | so, I most probably struggled with the or1ksim generator all in vain :( | 08:31 |
stekern | olofk_: is there only a github provider? can't I use a arbitrary git repo? | 08:39 |
olofk_ | stekern: Nope | 08:40 |
olofk_ | I have been thinking all the time that I should make githubprovider a subclass of gitprovider, but so far no one has had any need for a non-github git repo | 08:41 |
olofk_ | And githubprovider doesn't even use git anymore IIRC :) | 08:41 |
olofk_ | But a gitprovider is most welcome | 08:42 |
olofk_ | Preferably, I would like the providers to use the section infrastructure as well, but it's no strict requirement | 08:43 |
stekern | fair enough =) | 08:43 |
stekern | how does command line completion work in bash? | 10:55 |
stekern | or how does it work in general | 10:55 |
stekern | it'd be nice to be able to: fusesoc build de0<tab><enter> | 10:56 |
stekern | ah! ls /etc/bash_completion.d/ | 10:58 |
olofk_ | stekern: I think it's a set of files under /etc/bash-completion that contains functions top return whole words from fragments | 10:58 |
olofk_ | oh | 10:59 |
olofk_ | You already found it | 10:59 |
stekern | my friend Mr Google is quicker than you ;) | 10:59 |
stekern | olofk_: did you hint the moxie guy abut fusesoc or was it just a coincident that he came complaining about missing README files? ;) | 11:08 |
olofk_ | stekern: What? Haven't seen that | 11:09 |
stekern | https://github.com/olofk/fusesoc/issues/19#issuecomment-40067604 | 11:10 |
olofk_ | That was fun :) | 11:13 |
stekern | I've added nop-reporting support in the mor1kx-generic verilator tb now | 12:01 |
stekern | and changed the 'exit(0/error)' message to look like or1ksims | 12:02 |
stekern | oh, and mor1kx now passes the or1ksim atomic tests I modified yesterday to use the F flag instead | 12:05 |
olofk_ | awesome x 3 :) | 12:07 |
* stekern nods | 12:08 | |
stekern | hmm... making the verilator testbench return the error code of the program doesn't fly well with fusesoc | 13:07 |
kyrre_ | Hi, Im struggeling to understand how the sprs array works in or1ksim, from what i can see it is an array of size 32. But when i print it in gdb its 2¹⁶ (65536) large. | 13:11 |
olofk_ | kyrre_: The sprs are stored in the cloud | 13:13 |
kyrre_ | say what? | 13:13 |
olofk_ | When you access an spr in mor1kx, it connect to Amazon and starts up a new Virtual Machine that serves the contents of the SPR | 13:14 |
olofk_ | It's all written with responsive web technologies so it's very fast | 13:14 |
olofk_ | Sorry. Never mind me :) | 13:15 |
kyrre_ | good, cause i was just getting more confused :p | 13:16 |
olofk_ | I think that or1k defines the SPR space to be 2^16, but only a small part of that is actually used | 13:16 |
kyrre_ | ok | 13:18 |
stekern | are you sure that you are not looking at the gpr array? | 13:19 |
stekern | there are definetely more than 32 sprs in or1ksim | 13:20 |
kyrre_ | ye, ive spent the last hour or so looking into this... the "solution" is to read things correctly MAX_GRPS != MAX_SPRS | 13:22 |
kyrre_ | so ye, thngs make sence now ;) | 13:22 |
kyrre_ | more sense * | 13:22 |
stekern | surprisingly compact the changes to mor1kx: https://github.com/skristiansson/mor1kx/commit/bb9ad6e895d84b48414b7e7dd105a60f346dd3f2 | 13:41 |
stekern | most are just signal declarations and interconnect | 13:41 |
stekern | I'm speaking about the new onedrive interface for the sprs here | 13:44 |
stekern | it'll be a part of mor1kx ms-edition, released in ms-pl | 13:46 |
stekern | most of it will be autogenerated from excel scripts | 13:47 |
stekern | all per olofk_'s requests | 13:49 |
Limb | mor1kx reset should be high when you want to reset, correct? | 13:51 |
olofk_ | stekern: That's the spirit :) | 13:52 |
stekern | Limb: yup | 14:04 |
Limb | stekern: wish i had known that... was the cause of my debugger issue -_- | 14:04 |
stekern | Limb: you can comfort yourself that you're probably long behind my wasted hours on reset polarity mistakes | 14:12 |
_franck_web_ | Limb: great ! so it is confirmed that openocd works with xilinx bscan | 14:13 |
stekern | that's very good | 14:13 |
Limb | _franck_web_: well I havent gotten anything to show on the processor yet, so I don't know if I'd say that just yet :P | 14:14 |
Limb | _franck_web_: but it looks like a hopeful yes! | 14:14 |
Limb | openocd mwb doesnt seem to be turning on my leds :( | 14:17 |
Limb | !!!! | 14:18 |
Limb | Had to increment the address by 1 | 14:18 |
Limb | we have lift off! | 14:18 |
_franck_web_ | gpio base is its direction register | 14:18 |
_franck_web_ | base+1 is output value | 14:19 |
Limb | This is the most exciting day so far in my journey haha | 14:19 |
_franck_web_ | :) This is good feeling | 14:19 |
_franck_web_ | nothing better than a lighting led :) | 14:20 |
Limb | _franck_web_: if im uploading your blink elf, should i set the start adress to 0x0 or 0x100 | 14:22 |
_franck_web_ | start at 0x100 | 14:23 |
Limb | I'm gonna have to cherrypick that elf patch you have for openocd -_- | 14:24 |
_franck_web_ | yes. Or you can link my program and use a simple linker script | 14:24 |
_franck_web_ | then the elf file will have a program section | 14:25 |
_franck_web_ | (didn't know that) | 14:25 |
Limb | can you pastebin a example of a simple linker script? :) | 14:25 |
_franck_web_ | http://pastie.org/9073036 | 14:26 |
Limb | hrmmm | 14:27 |
Limb | care to explain a bit more in depth? haha | 14:27 |
Limb | my build tools are or32-linux- is this even the right tool chain? | 14:27 |
_franck_web_ | for this simple kind of program yes | 14:28 |
_franck_web_ | this script will put your .text section at adress 0x100 | 14:28 |
_franck_web_ | then .data after that then .bss after that | 14:29 |
Limb | That part I can understand. I meant more of how do i link it with the rest? | 14:29 |
Limb | my command line compile skills... have never been that great | 14:29 |
_franck_web_ | or1k-elf-gcc -c test.o | 14:29 |
Limb | or32-linux-gcc is the same? | 14:30 |
_franck_web_ | or1k-elf-ld -o test.elf test.o -T $your_linker_script | 14:30 |
_franck_web_ | or32-elf-gcc is for baremetal applications | 14:30 |
_franck_web_ | or32-linux-gcc is for linux applications | 14:30 |
Limb | ah. so i need to get the baremetal toolchain | 14:31 |
Limb | all i have is linux | 14:31 |
_franck_web_ | that will work anyway here | 14:31 |
ysionneau | jeremybennett: hi :) I think you might now a bit about the ARC cpu architecture, am I right ? :) What would be the "killer feature" or interesting advantages of this CPU ? (or can you point me to a document which explains a bit what are the good points ?) thanks :) | 14:48 |
olofk | Limb: Congratulations. Good job! | 15:59 |
olofk | It will be a race between your nexys4, stekern's atlys and my lx9_microboard for which will become the first Xilinx-system in orpsoc-cores :) | 16:22 |
Findeton | olofk: so how fast is your openrisc fpga? | 16:30 |
Findeton | do you think your xilinx system might have hardware-based backdoors for the NSA? | 16:31 |
Limb | blink asm doesnt seem to work :( | 16:43 |
Limb | mwb 0x9000001 255 | 16:45 |
Limb | oh hey, this isnt the terminal :P | 16:45 |
Findeton | uhm | 16:51 |
Findeton | I have a problem with texinfo while compiling the toolchain | 16:52 |
Findeton | basically, I have somethink like @code{ | 16:52 |
Findeton | blah blah | 16:52 |
Findeton | blah} | 16:52 |
Findeton | but it doesn't work, it says that the first line has a closing brace missing and that the last line has a opening brace missing | 16:53 |
Findeton | do I need to do something special to put a multiple lines thing between braces? | 16:53 |
Limb | ... and somehow i reupload the same bitfile and now nothing works | 16:57 |
Limb | wonderful | 16:57 |
Limb | doesnt appear openocd is loading the memory with the program | 17:16 |
stekern | Findeton: do you have a particular need to use th or32 toolchain? | 17:35 |
stekern | +e | 17:35 |
olofk | Limb: What are you using for memory in your system? | 17:36 |
Findeton | uhm stekern no but I'd like to | 17:36 |
Findeton | why? | 17:36 |
olofk | Findeton: I'm running the lx9 at 40MHz right now. Might be able to crank it up a little bit more | 17:37 |
olofk | And no, I don't think there are any NSA back doors in the FPGAs. It would be a fucking pain to extract any kind of information that way | 17:38 |
stekern | just that it seems like a path with less resistance to use the or1k toolchain that doesn't have the problem, but if you like the problem solving, it's all fine | 17:38 |
Findeton | stekern which toolchain doesn't have the problem? | 17:55 |
stekern | or1k- | 18:02 |
Findeton | uhm | 18:03 |
Findeton | I am confused, I believe I am dealing with the or1k- toolchain | 18:04 |
Findeton | am I wrong? lol | 18:04 |
Findeton | also, what is the difference? or1k is the new one and or32 is outdated | 18:06 |
Findeton | ? | 18:06 |
Findeton | In practice this means that the stable toolchain uses the old CPU target or32 (e.g. or32-elf, or32-linux), while the new/developemnt toolchain uses or1k (eg. or1k-elf, or1k-linux) | 18:07 |
stekern | yes, the old toolchain has the or32 prefix and the new uses or1k as the prefix | 18:09 |
Findeton | and stekern, is the new or1ksim called or32-elf-sim? | 18:13 |
Findeton | or that means I have the old thing? | 18:13 |
stekern | the prefix before sim only exists if you compile it together with a toolchain, otherwise it's just sim | 18:15 |
stekern | i.e. or32-elf-sim, or32-linux-sim, or1k-elf-sim, or1k-linux-sim etc can all be the exact same executable | 18:16 |
stekern | if you want the full history, the or32- toolchain was brought to a stable state (passing the gcc regression tests) by jeremybennett's company, embecosm. | 18:20 |
stekern | there was a defiency in the binutils of that port however, it was originally based on cgen, but then the machine generated files had been modified by hand (afair). | 18:21 |
stekern | juliusb then took the cgen based things and fixed things up, and at the same time he changed the name from or32- to or1k-, because the or32- had been a mistake | 18:23 |
stekern | peter gavin then picked that up and updated gcc to the or1k- naming and synced with upstream | 18:23 |
stekern | then I added dynamic linking and blueCmd TLS support, _franck_ brought gdb up to date etc etc | 18:24 |
Findeton | uhm | 18:27 |
Findeton | there's a history there that's for sure | 18:27 |
Limb | olofk: your wb_ram | 18:28 |
Findeton | out of curiosity, what's that attracts you to openrisc stekern | 18:28 |
Findeton | ? | 18:28 |
stekern | the groupies | 18:30 |
stekern | jk | 18:30 |
stekern | there's a lot of fun problems to be solved, and in a lot of fun areas | 18:31 |
stekern | and I'm a kind of learn by doing kind of guy, so I have to do a lot to learn anything | 18:31 |
olofk | Limb: So.. it works then? That's cool | 18:33 |
olofk | Findeton: As stekern said, we're only doing this to get laid | 18:33 |
stekern | yes, and since that haven't happened yet, we just try harder | 18:34 |
olofk | :) | 18:34 |
Findeton | stekern: yeah, like rockstarts | 18:34 |
Limb | olofk: it doesnt work :P | 18:35 |
Findeton | it is for the pussy (or whatever thing you fancy) | 18:35 |
Limb | openocd doesnt seem to write to the actual memory | 18:35 |
Findeton | ok the first set of tools has compiled (newlib/or1k), that's great! | 18:36 |
olofk | Limb: rap :( | 18:36 |
olofk | crap :) | 18:36 |
stekern | olofk: no, not like rapstars, rockstars | 18:36 |
Limb | olofk: do you have a new copy you can send me to try? | 18:37 |
Findeton | I'd like to have a working laptop with free hardware, openrisc might be able to achieve that | 18:37 |
Findeton | with some good fpgas and multiple openrisc cores lol | 18:38 |
olofk | Limb: I just started looking into it. Don't have anything newer yet | 18:38 |
Findeton | Perhaps with that I could get a decent 300Mhz laptop | 18:38 |
olofk | But I'm running my lx9 through simulations to get an idea what's going on | 18:39 |
AndroUser | Hi! Is here anybody who worked with or32-linux-gcc crosscompiler for orsoc system? | 18:45 |
stekern | AndroUser: there might be | 18:49 |
AndroUser | Oh and who?:) | 18:54 |
stekern | hmm, is it a known issue that there are 10 tests failing in the or1ksim or1k-master branch? | 18:55 |
stekern | AndroUser: depends on what you mean with worked with, but if you mean used: stekern olofk juliusb jeremybennett _franck_ Limb LoneTech blueCmd poke53281 and probably many more | 18:57 |
olofk | AndroUser: What kind of info are you looking for? | 18:58 |
AndroUser | Well my problem is that i succeeded to compile the linux kernel for the orsoc but i want a simple program that reads and writes a physical address,a register. | 18:59 |
AndroUser | I found an example program but it includes headers that the compiler dont find,even if i add the path. | 19:00 |
AndroUser | So probably i doing something wrong | 19:00 |
AndroUser | I am really new to this crsscomliping thing | 19:00 |
olofk | AndroUser: Just to avoid confusion in the future, ORSoC is the company that owns OpenCores, ORPSoC is a SoC comprised of or1200 and a few peripheral cores | 19:01 |
olofk | AndroUser: Just trying to fully understand what you're after :) | 19:02 |
olofk | You have compiled the linux kernel for OpenRISC, right? | 19:02 |
AndroUser | Yes | 19:05 |
olofk | So your compiler works fine then I guess | 19:05 |
stekern | AndroUser: can you paste the program that you are trying to compile | 19:05 |
AndroUser | Actully i have downloaded a virtualbox image that have the toolchain working | 19:06 |
olofk | Ah ok. | 19:06 |
AndroUser | Well i cant now cause i am on mobile but i can write the includes that cause the problem | 19:06 |
AndroUser | Module.h,config.h,init.h, | 19:07 |
AndroUser | Wait i rty to find the program | 19:07 |
Limb | olofk: did you see my request for an updated wb_ram? :) | 19:08 |
olofk | Limb: Yes. Ain't got anything better than what you got | 19:10 |
olofk | You could try ram_wb instead | 19:10 |
AndroUser | Well i cant find the program.but i write what i want to eventually do.i made a simple peripheral that contains about 3 registers.i want to compile a program that is reading and writing the registers.and run this program on linux kernel that is running on this orpsoc system.i hope it is understandable:s | 19:16 |
AndroUser | Can u maybe show me a short code that can do this? | 19:17 |
olofk | Read register => value = *addr; | 19:18 |
olofk | Write register => *addr = value; | 19:18 |
AndroUser | Or maybe can somby give me some contact for skype or thing like that? Maybe its easier to describe the situation there:s | 19:19 |
olofk | Haven't got time for that. Sorry | 19:20 |
AndroUser | Theese are working functions? What header do i need for that? | 19:20 |
olofk | No. It's just plain C | 19:20 |
AndroUser | No problem,just tell me what headers do i need for this kind of operations | 19:21 |
olofk | None | 19:21 |
AndroUser | Oh thats not working on linux kernel if i am right | 19:21 |
olofk | Ah yes. Things are probably more complicated under linux | 19:22 |
AndroUser | Yes.in standard c i could write driver and it was working fine | 19:23 |
stekern | AndroUser: normally, when you access hardware in linux, you write a device driver for your hardware. My guess that the example you've found is an example of that. But, if you're going to do that, make your device driver reside in the Linux tree instead. | 19:23 |
AndroUser | Yes it was an example like that. | 19:24 |
AndroUser | But i cant compile it because of the headers | 19:24 |
stekern | if you want to access 'memory' from userspace, you can mmap it | 19:25 |
stekern | as an example https://gist.github.com/mike0/2910170 | 19:26 |
AndroUser | And what header contains the mmap function? | 19:26 |
stekern | sys/mman.h | 19:26 |
stekern | but if you want a driver for your device, why not just do it inside the kernel tree | 19:27 |
AndroUser | Wellaybe this is noobish from me so sry for it but i dont understand what that means:s | 19:28 |
AndroUser | Anyways i want the most simpliest way for now,and i thought it would be a simple program that switches a bit or somethinf like that | 19:30 |
stekern | but it's not a "program", it's a kernel driver that you are trying to do, something that will be closely tied to the kernel | 19:31 |
stekern | a simple program would be "Hello world!" | 19:32 |
AndroUser | Well than how would u write and compile this program/driver? | 19:33 |
stekern | what is it that your hardware does? | 19:33 |
AndroUser | Well at the end it ll be a test enviroent but for now nothing just a register that can be written and read | 19:36 |
olofk | Wouldn't the gpio driver be a good example | 19:41 |
stekern | I'd find a good place for it in the Linux tree and put it there | 19:41 |
Limb | with ram_wb what exactly are wbm0, wmb1 and wbm2 | 19:41 |
olofk | Limb: Three different wishbone ports | 19:43 |
Limb | olofk: what do they need to be connected to? withh data and instruction bus be fine? | 19:44 |
Limb | with = will* | 19:44 |
olofk | Limb: oh. sorry. Forgot to say. You don't have to use ram_wb.v. You can use ram_wb_b3.v directly instead | 19:46 |
olofk | That is only a single port | 19:46 |
Limb | ah. i thought b3 was for simulation? | 19:46 |
olofk | The problem I had was that it wouldn't map to Block RAM, so I started to reimplement it with wb_ram | 19:47 |
stekern | AndroUser: if you really want to build your module outside of the kernel tree, use a Makefile that looks something like this: http://pastie.org/9073629 | 19:47 |
Findeton | stekern: do you prefer the newlib or the uclibc toolchain? | 20:03 |
stekern | I prefer the newlib toolchain over the uclibc toolchain when I compile baremetal and the uclibc toolchain over the newlib toolchain when I compile Linux userspace programs | 20:06 |
Findeton | uh and why is that? | 20:15 |
stekern | because they have those two different purposes | 20:16 |
Findeton | aham | 20:17 |
Findeton | so for example | 20:17 |
Limb | olofk: you werent kidding... ram_wb is utilizing 83% of my slices | 20:18 |
Findeton | if I want to run/develop linux programs on the or1ksim it's better to use uclibc | 20:18 |
stekern | right, you can't use the or1k/or32-elf- toolchain for that | 20:19 |
Findeton | uhm I don't understand that | 20:19 |
Findeton | what's the toolchain actually used then for? | 20:19 |
stekern | to compile baremetal programs, as I said | 20:22 |
Findeton | ah, you mean the newlib ok | 20:22 |
stekern | yes, or1k/or32-elf- == newlib | 20:23 |
Findeton | so for example if I want to create a baremetal assembler, I'd use newlib | 20:23 |
stekern | yes | 20:24 |
Findeton | now I'm trying to build gcc with newlib (it's the last step) but it gives me an error: | 20:25 |
Findeton | checking for the value of EOF... configure: error: computing EOF failed | 20:26 |
Findeton | it's while compiling libstdc++ | 20:26 |
stekern | which toolchain are you now building, or32 or or1k? | 20:27 |
stekern | and can you post the config.log | 20:27 |
Findeton | or1k | 20:30 |
Findeton | uhm | 20:30 |
Findeton | 1 seg | 20:31 |
Findeton | http://pastebin.com/PdaiRtHR | 20:32 |
Limb | What I would give for multicore ISE. Been in PAR phase for half an hour :( | 20:36 |
stekern | Findeton: the fail isn't in there | 20:40 |
Findeton | stekern: oh, I'll put the console output too one sec | 20:41 |
stekern | was that the config.log from the libstdc++ directory? | 20:42 |
Findeton | http://pastebin.com/FN4ZbZWL | 20:46 |
Findeton | uhm no | 20:46 |
Findeton | it's not that lol | 20:47 |
Findeton | while I get to it, this is the console output | 20:47 |
Findeton | http://pastebin.com/v6qRy1NZ | 20:47 |
Findeton | shit I do not see the config.log on libstdc++ directory | 20:52 |
stekern | maybe there aren't one | 20:53 |
Findeton | openrisc@openrisc-VirtualBox:~/openrisc/or1k-gcc/libstdc++-v3$ ls | grep config | 20:54 |
Findeton | config config.h.in configure configure.ac configure.host crossconfig.m4 | 20:55 |
Findeton | basically there isn't | 20:55 |
Findeton | http://sourceware-org.1504.n7.nabble.com/libstdc-configuration-error-ct-ng-v1-16-0-td158065.html | 21:14 |
Findeton | I think it's this | 21:14 |
Findeton | I'll try if that solution works | 21:14 |
Limb | sigh | 21:46 |
Limb | well i got it to upload, and openocd verifies the memory | 21:46 |
Limb | but when i resume... nothing blinks :( | 21:46 |
_franck_ | did you do a: reg npc 0x100 before resume ? | 21:49 |
Limb | no change | 21:50 |
_franck_ | do "halt" and "reg npc" | 21:51 |
Limb | npc (/32): 0x00000708 | 21:51 |
_franck_ | 0x700: Illegal insn exception | 21:51 |
_franck_ | do a mdw 0x100 | 21:52 |
Limb | 0x00000100: 7f454c46 | 21:52 |
_franck_ | I don't have the code in front of my eye but looks bad | 21:53 |
_franck_ | should be 0x18609100 | 21:54 |
Limb | maybe i executed something wrong | 21:54 |
_franck_ | look this is your led blinker with instruction code: http://pastie.org/private/rx0jhh8entv3z5ccyosoq | 21:55 |
Limb | hrmmm | 21:57 |
Limb | my numbers are +100 to yours | 21:57 |
_franck_ | ah I know ! | 21:57 |
_franck_ | remove . 0x100 from the linker script | 21:57 |
_franck_ | (or org 0x100 from the led_blinker.S) | 21:58 |
_franck_ | do the second one | 21:58 |
_franck_ | remove org 0x100 from the led_blinker.S | 21:58 |
Limb | I figured it had something to do with that :) | 21:58 |
Limb | We have blinking lights! | 22:04 |
_franck_ | congrats !! :) | 22:05 |
Limb | took a week to get it working, but its working :) | 22:06 |
Limb | olofk: on your latest wb_ram you had posted I get the following error trying to synthesize ERROR:HDLCompiler:1654 - "/home/limb/Documents/fusesoc-builds/build/nexys4/src/wb_ram/rtl/verilog/wb_ram.v" Line 33: Instantiating <wb_next_adr0> from unknown module <wb_next_adr> | 22:07 |
Limb | olofk: adding wb_funcs.v to the core includes results in an error stating it cant find wb_bfm_params.v | 22:14 |
blueCmd | stekern: Pretty sure he wanted this "module.h": http://lxr.free-electrons.com/source/include/linux/module.h | 22:31 |
blueCmd | stekern: so yes, your assumption about it being a kernel module seems valid | 22:31 |
Limb | olofk: And it appears your original code you had zipped up does not work either :/ openocd fails at verification of the memory | 22:37 |
Limb | olofk: it appears nothing it being written to ram | 22:37 |
--- Log closed Sat Apr 12 00:00:01 2014 |
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!