*** tpb has joined #timvideos | 00:00 | |
*** CarlFK has joined #timvideos | 00:22 | |
*** ChanServ sets mode: +v CarlFK | 00:22 | |
*** CarlFK has quit IRC | 01:55 | |
*** CarlFK has joined #timvideos | 02:01 | |
*** ChanServ sets mode: +v CarlFK | 02:01 | |
*** aom_ has joined #timvideos | 02:35 | |
*** sb0 has joined #timvideos | 03:36 | |
*** sb0 has quit IRC | 04:18 | |
*** sb0 has joined #timvideos | 04:44 | |
*** nueces has quit IRC | 05:10 | |
*** puck has quit IRC | 05:16 | |
*** puck has joined #timvideos | 05:19 | |
*** ssk1328 has joined #timvideos | 05:39 | |
*** aom_ has quit IRC | 05:40 | |
ssk1328 | Neuron1k: Thanks for the link, very detailed description. Actually, in my case I had started reading about cache and memory before I started doing any serious programming. | 05:42 |
---|---|---|
*** sab_123 has joined #timvideos | 05:42 | |
sab_123 | mithro, sent an email | 06:23 |
ssk1328 | mithro/_florent_ | 07:37 |
ssk1328 | I just sent a pull request for float16 csc conversion | 07:37 |
ssk1328 | https://github.com/enjoy-digital/litevideo/pull/5 | 07:38 |
tpb | Title: Adding float16 conversion by ssk1328 · Pull Request #5 · enjoy-digital/litevideo · GitHub (at github.com) | 07:38 |
*** sb0 has quit IRC | 07:44 | |
*** sb0 has joined #timvideos | 07:45 | |
*** vystrela_ has quit IRC | 08:37 | |
*** jea has quit IRC | 08:38 | |
*** vystrela has joined #timvideos | 08:45 | |
*** jea has joined #timvideos | 08:46 | |
_florent_ | ssk1328: I commented your pul request | 09:29 |
ssk1328 | _florent_: Thanks! | 09:29 |
ssk1328 | _florent_: Do you have time to look at an error I am getting? | 09:29 |
_florent_ | ssk1328: but in the commit message you have to say why you need that, where you are going to use that | 09:29 |
_florent_ | ssk1328: no what's the error? | 09:30 |
ssk1328 | http://paste.ubuntu.com/18510701/ | 09:30 |
tpb | Title: Ubuntu Pastebin (at paste.ubuntu.com) | 09:30 |
ssk1328 | I get this when run make rgb16f2rgb_tb, but don't get this when I run the other make rgb2rgb16f_tb | 09:31 |
_florent_ | strange, I'm not able to locate the error but looking at the code | 09:35 |
_florent_ | what's the reason for introducing floating point here? | 09:35 |
_florent_ | (just trying to understand) | 09:36 |
ssk1328 | For my GSoC project, I need to gamma correct and do other operations on rgb pixel values | 09:36 |
ssk1328 | some of the color correction operations can cause values to temporarily become greater than 1.0 or less than 0.0 and we need to be able to preserve that actual value | 09:37 |
ssk1328 | [0.0-1.0] in float maps to [0-255] in unsigned int | 09:39 |
_florent_ | ok, so this is specific to your project for now | 09:39 |
_florent_ | can we keep that in your project for now and eventually integrate that later? | 09:40 |
ssk1328 | Yes | 09:40 |
_florent_ | ok | 09:41 |
ssk1328 | Actually mithro said that its easier to comment and review code by following this | 09:41 |
_florent_ | since thing are still experimental, it's better keeping it in a reparate repo | 09:50 |
_florent_ | we should maybe create a repo for you on https://github.com/timvideos | 09:51 |
tpb | Title: Tim Videos Conference Recording Systems · GitHub (at github.com) | 09:51 |
_florent_ | we are working like this with aom: https://github.com/enjoy-digital/hdmi-extenders-gsoc | 09:52 |
tpb | Title: GitHub - enjoy-digital/hdmi-extenders-gsoc: HDMI Extenders GSoC project with TimVideos.us (at github.com) | 09:52 |
ssk1328 | Okay, lets see what mithro suggests | 09:52 |
_florent_ | also, I'm wondering if it would not be better to just use 2 look up table to do int to floating point/floating point to int conversion | 09:54 |
_florent_ | 16 bits floating point to 8 bits int: 65536x8bits lut / 8 bits int to 16 bits floating point: 256x16bits lut | 09:55 |
_florent_ | and fill this by software | 09:55 |
ssk1328 | _florent_: This can surely be done if we have sufficient memory space and bandwidth to carry out this | 09:56 |
ssk1328 | _florent_: I am not too sure about that | 09:57 |
*** sb0 has quit IRC | 10:13 | |
mithro | ssk1328: https://github.com/mithro/HDMI2USB-mixing-mask/pull/2 | 11:38 |
tpb | Title: Example RLE code by mithro · Pull Request #2 · mithro/HDMI2USB-mixing-mask · GitHub (at github.com) | 11:38 |
mithro | _florent_: I'd like to keep it in a pull request for litevideo as this functions will become fundamental to doing all types of proper video mixing, scaling and transforming | 11:40 |
ssk1328 | mithro: Just looking at the code right now | 11:41 |
mithro | ssk1328: It might be possible to do the int8 to float16 with the gamma correction using one 256 entry lookup table | 11:42 |
mithro | a 65536*16bit lookup table for the reverse seems kind of expensive | 11:42 |
ssk1328 | mithro: Okay. And what about the other way round? | 11:42 |
ssk1328 | mithro: Okay | 11:42 |
mithro | ssk1328: actaully, it might be okay - because anything below 0 should be mapped to 0 and anything above 1.0 should be mapped to 255 | 11:43 |
_florent_ | mithro/ssk1328: do you really need 16 bits floating point? | 11:43 |
_florent_ | mabe you can reduce to 12 bits or less | 11:44 |
_florent_ | mithro: ok to have pull request to litevideo but not for experimental things | 11:44 |
ssk1328 | We are actually not using the complete range provided by float16 | 11:44 |
mithro | _florent_: for color accurate blending, 16bit floating point gives less than -30db noise introduction | 11:44 |
_florent_ | mithro: once things are proven on hardware / with simulation, then ok to integrate that | 11:45 |
mithro | _florent_: a WIP pull request and stay around for a while why we add comments and stuff to it | 11:46 |
mithro | _florent_: I guess I can get him to send the pull request to my repo, but we will still need your comments on the code | 11:46 |
_florent_ | if it stay as a pull request until we fix things and get things done correctly then ok | 11:46 |
mithro | _florent_: yes, the pull request is just a place to keep comments all together | 11:47 |
_florent_ | ok, no problem then | 11:48 |
mithro | _florent_: great! | 11:50 |
mithro | _florent_: ssk1328 has a bunch of documentation on how 16bit floats will end up being implemented in the FPGA | 11:51 |
mithro | ssk1328: do you want to share them? | 11:51 |
ssk1328 | _florent_: Here it is https://docs.google.com/document/d/1684Tn4aeWxeelCvrJ5maKJoShtlIRolC2oq0c4_4A7k/edit# | 11:51 |
tpb | Title: Design Document on 16bit Floating Point - Google Docs (at docs.google.com) | 11:51 |
*** Bertl_zZ is now known as Bertl_oO | 11:51 | |
ssk1328 | Still work in progress | 11:51 |
_florent_ | ssk1328: thanks | 12:01 |
mithro | sab_123: you do know you can view the diff that I will view at https://github.com/mithro/fx2lib/pull/17/files right? | 12:04 |
tpb | Title: Created a UART API definition by RacingTornado · Pull Request #17 · mithro/fx2lib · GitHub (at github.com) | 12:04 |
sab_123 | mithro, yes | 12:05 |
mithro | sab_123: so you can view that and then see if there is anything I might find wrong with it too | 12:06 |
sab_123 | mithro, forgot to remove that | 12:06 |
sab_123 | I checked it now | 12:06 |
sab_123 | :-) | 12:06 |
sab_123 | I compile it to test if the header is okay | 12:06 |
sab_123 | In the sense, does it compile | 12:06 |
sab_123 | Usually I remove it | 12:06 |
mithro | sab_123: Also, I'd like you to think more about the consequences of your comments in documentation | 12:07 |
mithro | sab_123: If you saw something like "Enum values greater than 0 are supported.", you could get the impression that all uarts support all the enum values | 12:08 |
mithro | sab_123: you also need to think about the context, is something system level, uart level, api level or implementation level, etc | 12:09 |
mithro | sab_123: Think of all the different ways people might misinterpret your comments too | 12:09 |
sab_123 | mithro, ok | 12:09 |
mithro | ssk1328: it looks like you haven't pushed updated commits for the heartbeat yet? | 12:33 |
mithro | sab_123: "Unless you know what you doing" is a useless thing to say | 12:34 |
sab_123 | mithro, how would you like me to word it then | 12:35 |
mithro | sab_123: Explain to me why they shouldn't use them? | 12:35 |
sab_123 | mithro, basically the end user shoudnt use those values | 12:35 |
mithro | sab_123: then why do they exist? | 12:35 |
sab_123 | Mainly because the baud rate is not standard | 12:35 |
mithro | sab_123: so? | 12:36 |
mithro | sab_123: If the user requested a non-standard baud rate and it is documented that you might get a non-standard baud rate, then everything is good | 12:36 |
sab_123 | And you would have to setup software in the system(ex: minicom doesnt support anything other than standard ones) | 12:36 |
sab_123 | gtkterm doesnt either | 12:36 |
mithro | sab_123: So, what is the issue you are trying to prevent then? | 12:37 |
sab_123 | The only way to see those rates is to hook up those lines using a scope .. | 12:37 |
sab_123 | Or some software which I havent yet used which supports non standard baud | 12:37 |
mithro | sab_123: BAUD_FASTEST will give you the fastest baud rate the UART can operate, this may be a non-standard baud rate, you can use XYZ to get the actual set BAUD rate. | 12:38 |
mithro | sab_123: Or | 12:38 |
mithro | sab_123: BAUD_FASTEST will give you the fastest baud rate the UART can operate at. WARNING: This is allowed to be a non-standard baud rate. | 12:39 |
sab_123 | mithro, I will put that in | 12:39 |
mithro | sab_123: You should be now thinking, "should BAUD_ANY give you a non-standard baud rate"? | 12:39 |
mithro | sab_123: should there be a "BAUD_FASTEST_STANDARD" which gives the fastest standard baud rate? | 12:40 |
mithro | sab_123: The API only currently lets you get standard baud rates, but a non-standard baud rate can be set via BAUD_FASTEST, do we need an API function which returns the actual baud rate as an uint16_t or something? | 12:41 |
sab_123 | mithro, it returns BAUD_FASTEST | 12:41 |
sab_123 | setting and returning are the same enum | 12:41 |
mithro | sab_123: do you see a problem there then? | 12:41 |
mithro | sab_123: Calling "set_baud_rate(BAUD_FASTEST)" and then having "get_baud_rate()" return BAUD_9600 seems like a pretty reasonable and useful API | 12:42 |
sab_123 | mithro, I dont get that | 12:43 |
sab_123 | BAUD_FASTEST would be mapped to one of the bauds | 12:43 |
sab_123 | in the enum | 12:43 |
sab_123 | I just return that | 12:43 |
sab_123 | ex: | 12:43 |
sab_123 | BAUD_FASTEST in uart0 gets mapped to 9600 | 12:43 |
sab_123 | so the enum is automatically set to 9600 | 12:44 |
mithro | sab_123: yes | 12:44 |
sab_123 | yes | 12:44 |
mithro | sab_123: but you can't redefine BAUD_FASTEST to the same value as 9600 as that would affect giving uart1 | 12:44 |
sab_123 | it wont | 12:45 |
sab_123 | they are no different enums | 12:45 |
sab_123 | *two | 12:45 |
mithro | sab_123: that isn't how the API is define right now | 12:45 |
mithro | there is one BAUD_FASTEST define in the api code | 12:46 |
sab_123 | yes | 12:46 |
sab_123 | that just the enum | 12:46 |
mithro | I have to go | 12:47 |
mithro | sab_123: show me how it works, your documentation can't be up to scratch because we don't seem to be understanding each other | 12:47 |
sab_123 | https://github.com/RacingTornado/fx2lib/blob/82ae21829baf26985656fb57c67761c5ca48a721/include/uart/soft_uart.h#L18 | 12:47 |
tpb | Title: fx2lib/soft_uart.h at 82ae21829baf26985656fb57c67761c5ca48a721 · RacingTornado/fx2lib · GitHub (at github.com) | 12:47 |
sab_123 | For every uart which is created, I create that enum | 12:49 |
sab_123 | The just return that same enum | 12:49 |
sab_123 | so if uart0 is used, the uart0 enum will return | 12:49 |
sab_123 | for uart1, the uart1 enum will return | 12:49 |
sab_123 | https://github.com/RacingTornado/fx2lib/blob/82ae21829baf26985656fb57c67761c5ca48a721/include/uart/soft_uart.h#L57 | 12:50 |
tpb | Title: fx2lib/soft_uart.h at 82ae21829baf26985656fb57c67761c5ca48a721 · RacingTornado/fx2lib · GitHub (at github.com) | 12:50 |
sab_123 | I will set the baud rate there | 12:50 |
*** shenki has quit IRC | 13:27 | |
*** shenki has joined #timvideos | 13:39 | |
*** ChanServ sets mode: +v shenki | 13:39 | |
*** nueces has joined #timvideos | 13:46 | |
*** ssk1328 has quit IRC | 14:34 | |
*** G33KatWork has quit IRC | 14:37 | |
mithro | _florent_: quick ping? I'm just heading to bed but wanted to share something with you before I did | 14:51 |
_florent_ | yes I'm here | 14:52 |
mithro | https://docs.google.com/drawings/d/1O5TvKCoEzt4yY4O3urvT5bD3mFzAWVD7pIDa4SngjxA/edit | 14:53 |
tpb | Title: lite ecosystem - Google Drawings (at docs.google.com) | 14:53 |
mithro | _florent_: I was thinking about how to do the CI for all your lite stuff | 14:53 |
mithro | _florent_: and that is my proposal for how you should structure things | 14:54 |
mithro | _florent_: also interested in making it easier to share stuff from the HDMI2USB-misoc-firmware and "upstream" | 14:54 |
_florent_ | mithro, thanks, that's interesting :) | 14:55 |
mithro | _florent_: Have a thing about it and we can discuss details more later in the week | 14:56 |
_florent_ | yes | 14:56 |
cr1901_modern | I wonder what the minimal component liteSATA board is... | 14:56 |
_florent_ | not sure we should split litesoc/litevideosoc/litesoclinux | 14:56 |
_florent_ | this can simply be litesoc | 14:57 |
mithro | _florent_: But I'm obviously invested in getting lite modules into the position that you have other contributors and always improving code quality+productivity :) | 14:57 |
_florent_ | but what I see is that it seems to solve some of the inter-dependency | 14:57 |
cr1901_modern | mithro: I'm familiar with litescope FWIW | 14:57 |
mithro | I think litesoclinux would just be litesoc + the linux tooling side of things (IE linux kernel, linux user space, etc) | 14:58 |
_florent_ | yes but we can probably have all that in a single repo I think, no? | 14:58 |
mithro | _florent_: well, it depends on if people are going to continue to use litesoc without Linux | 14:59 |
mithro | _florent_: It's more attractive if you don't have all this extra stuff lying around which you don't use | 14:59 |
_florent_ | yes I can understand, let's think about that and discuss that later | 15:00 |
mithro | It might make sense to merge litesoc and litevideosoc - I was thinking that litevideosoc would be a reduced set of boards with more functionality - IE if a board is in litevideosoc it will minimally do a set of things | 15:00 |
mithro | I can imagine someone wanting a litesoc-rtems maybe :) | 15:01 |
_florent_ | cr1901_modern: for LiteSATA, a nexys_video | 15:01 |
_florent_ | or KC705 | 15:01 |
_florent_ | or the opsis | 15:01 |
mithro | _florent_: There is SATA on the nexys_video? | 15:01 |
cr1901_modern | That later one is $3000!! | 15:01 |
mithro | _florent_: or an FMC board? | 15:01 |
cr1901_modern | The KC705* | 15:01 |
_florent_ | you only need a transceiver | 15:02 |
_florent_ | and find a way to connect it to a SATA cable | 15:02 |
_florent_ | yes the KC705 is expensive | 15:02 |
cr1901_modern | What prevents someone from making a PMOD Sata connector? | 15:02 |
mithro | cr1901_modern: The GTP transceivers are not broken out to the PMOD connectors normally... | 15:04 |
_florent_ | I haven't seen PMOD connectors connected to transceivers | 15:04 |
cr1901_modern | Oh, the required transceivers are on specific pins... | 15:04 |
mithro | Although, SATA 1.0 is only 1.5 Gbit/s -- the Artix-7 can do that on its normal pins with a bit of coaxing.... | 15:05 |
cr1901_modern | I don't think I have any boards/FPGAs with the proper transceivers... I thought it was LVDS for some reason | 15:05 |
cr1901_modern | Unless minispartan can do SATA 1.0 | 15:06 |
mithro | cr1901_modern: It is LVDS, just very high speed LVDS | 15:06 |
mithro | SATA 2.0 is 3Gbit/s - SATA revision 3.2 is 16 Gbit/s! | 15:07 |
cr1901_modern | So Xilinx et al provides a special LVDS transceivers? As opposed to HMDI which can get away with a "basic" LVDS setting? | 15:07 |
mithro | cr1901_modern: the high speed transceivers - GTP and GTX | 15:08 |
mithro | cr1901_modern: the Opsis has them, broken out on the DisplayPort connectors | 15:08 |
cr1901_modern | I guess minispartan doesn't need them/use them | 15:09 |
mithro | cr1901_modern: yeah, it's why it can only do 720p60 or 1080p30 | 15:09 |
cr1901_modern | Oh, I thought that was b/c of the shitty SDRAM bandwidth :P | 15:09 |
mithro | cr1901_modern: https://docs.google.com/document/d/1noNqTdLYlEru_6gWOlFqFvYe-vctUE23Tp42oRoKKKo/pub | 15:10 |
tpb | Title: Numato Opsis - Video Information FAQ (at docs.google.com) | 15:10 |
mithro | cr1901_modern: no, that is how fast the IO pins can toggle | 15:10 |
cr1901_modern | _florent_: Perhaps I got confused by what you meant by minispartan's "SDRAM woes"? | 15:11 |
mithro | cr1901_modern: it also has SDRAM woes :P | 15:11 |
mithro | anyway | 15:12 |
mithro | I should be asleep | 15:12 |
cr1901_modern | Is GTP enabled by placing the correct constraint in the UCF? | 15:12 |
cr1901_modern | Oh sorry... too many q;s | 15:12 |
mithro | _florent_: I'll try and reply to your other email tomorrow | 15:12 |
cr1901_modern | no worries, I'll figure it out later | 15:12 |
mithro | cr1901_modern: go read my FAQ | 15:13 |
mithro | cr1901_modern: any luck with the frequency counter? | 15:13 |
mithro | gnight -- I'l read the scrollback :) | 15:13 |
cr1901_modern | mithro: No, I've been swapping between your work and m-labs work | 15:14 |
cr1901_modern | mithro: I have a few things I haven't tried, but I won't be able to get much done if my display driver keeps crashing b/c it doesn't like the board. | 15:15 |
cr1901_modern | I'll probably try hamsterwork's minimum-component demo as a last resort. If that crashes my display driver, then my machine/driver is at fault. I'll need to buy a separate machine for testing then. | 15:16 |
*** sab_123 has quit IRC | 15:17 | |
cr1901_modern | mithro: Current status report... I'm under the impression that the freq counter works, but my machine doesn't like the minispartan and is refusing to send it good data/clk. | 15:17 |
cr1901_modern | mithro: I'll probably buy (another :P- got PocketCHIP as a bday gift) one of these as a last resort (with an HDMI daughterboard) https://getchip.com/pages/chip | 15:19 |
tpb | Title: Get C.H.I.P. - The World's First Nine Dollar Computer (at getchip.com) | 15:19 |
*** G33KatWork has joined #timvideos | 15:31 | |
*** ssk1328 has joined #timvideos | 16:37 | |
ssk1328 | mithro: heartbeat pull request was already updated with all the necessary changes made | 16:59 |
ssk1328 | mithro: Also logged an issue for volatile usage https://github.com/timvideos/HDMI2USB-misoc-firmware/issues/267 | 17:00 |
tpb | Title: Clean up the usage of volatile in the lm32 firmware · Issue #267 · timvideos/HDMI2USB-misoc-firmware · GitHub (at github.com) | 17:00 |
ssk1328 | mithro: Not sure how to add labels here, maybe I don't have the permissions | 17:00 |
*** ssk1328 has quit IRC | 20:24 | |
*** Bertl_oO is now known as Bertl_zZ | 21:50 | |
*** nueces has quit IRC | 21:51 | |
*** nueces has joined #timvideos | 22:23 | |
*** nueces has quit IRC | 22:35 | |
mithro | morning people | 22:50 |
mithro | Didn't actually sleep at all last night :( | 22:50 |
mithro | cr1901_modern: maybe get a RPi? | 22:50 |
mithro | cr1901_modern: They are cheap and tends to ignore EDID information even when you want them to read it :P | 22:51 |
*** nueces has joined #timvideos | 23:33 | |
nueces | mithro, hi, I'm testing the camera output with a hdmi tv and it works at 720p | 23:34 |
nueces | http://dpaste.com/3T37N39 | 23:34 |
tpb | Title: dpaste: 3T37N39 (at dpaste.com) | 23:34 |
CarlFK | nueces: I would test with the most recent firmware | 23:39 |
nueces | I'm compiling it to test | 23:40 |
CarlFK | nueces: https://github.com/timvideos/HDMI2USB-firmware-prebuilt | 23:41 |
tpb | Title: GitHub - timvideos/HDMI2USB-firmware-prebuilt: Prebuilt firmware for the HDMI2USB devices (such as the Numato Opsis and the Digilent Atlys board) and OS drivers. (at github.com) | 23:41 |
CarlFK | I hear the same source code doesn't produce the same binary, so it is probably better to use the same binary (right? who thing seems kinda wonky to me) | 23:42 |
*** nueces has quit IRC | 23:48 | |
*** nueces has joined #timvideos | 23:49 | |
cr1901_modern | Oh I do have an RPi... come to think of it. But no wifi dongle :( (It's a model A) | 23:57 |
nueces | I compiled and load the latest firmware and the output in the tv now is displaying an image | 23:57 |
nueces | but with the same problem that the other dat | 23:57 |
nueces | day | 23:57 |
nueces | http://dpaste.com/2SPV21K | 23:58 |
tpb | Title: dpaste: 2SPV21K (at dpaste.com) | 23:58 |
Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!