*** tpb has joined #timvideos | 00:00 | |
mithro | _florent_: sorry need to concentrate on finishing this stuff - maybe tomorrow? | 01:07 |
---|---|---|
*** rohitksingh has joined #timvideos | 01:25 | |
CarlFK | mithro: you proly mean me ;P | 01:47 |
CarlFK | I packaged gstreamer1.0-dvswitch and dvsource-v4l2-other and they are in my PPA | 01:48 |
CarlFK | bb in 20 | 01:48 |
CarlFK | back | 02:01 |
mithro | CarlFK: https://github.com/timvideos/HDMI2USB/wiki/EDID-Related-Code | 02:10 |
tpb | Title: EDID Related Code · timvideos/HDMI2USB Wiki · GitHub (at github.com) | 02:10 |
mithro | CarlFK: actually - https://github.com/timvideos/HDMI2USB/wiki/EDID-Related-Code#debugging-tips | 02:10 |
tpb | Title: EDID Related Code · timvideos/HDMI2USB Wiki · GitHub (at github.com) | 02:11 |
mithro | Enable that and then plug / unplug the connector | 02:11 |
mithro | CarlFK: that might give more information about what is going on with the hotplug line | 02:11 |
mithro | CarlFK: If that doesn't shine any light on the issue you are going to need an oscilloscope I think | 02:12 |
CarlFK | the info is in dmesg, right ? | 02:13 |
mithro | CarlFK: yeah | 02:13 |
mithro | CarlFK: you might see something about disabling / enabling interrupts or something | 02:13 |
CarlFK | mithro: every 10 seconds I see: | 02:16 |
CarlFK | [11042.816502] [drm:intel_tv_detect], [CONNECTOR:25:SVIDEO-1] force=0 | 02:16 |
CarlFK | and now this just one: [11056.985696] [drm:i965_irq_handler], pipe A underrun | 02:16 |
CarlFK | un/plugging now | 02:16 |
CarlFK | unplug, dmesg new: http://paste.ubuntu.com/12259525/ | 02:18 |
tpb | Title: Ubuntu Pastebin (at paste.ubuntu.com) | 02:18 |
CarlFK | mithro: pluged in, dmesg: http://paste.ubuntu.com/12259534/ [11274.559615] [drm:i915_hotplug_work_func], Connector HDMI-A-1 (pin 4) received hotplug event. | 02:21 |
tpb | Title: Ubuntu Pastebin (at paste.ubuntu.com) | 02:21 |
mithro | CarlFK: so - I think the lines which say "NACK" are the cause of the issue | 02:22 |
mithro | and actually - it might be something similar to issue described at https://plus.google.com/+StephenWarren/posts/7SH3Dn4y4go - "The main bug I had was not having implemented support for I2C writes; I'd assumed the PC would simply read the EEPROM once and be done with it, but it looks like it does a couple 1-byte reads, then a write to set the EDID EEPROM | 02:24 |
mithro | address followed by a read of the full content" | 02:24 |
mithro | _florent_: ping - are you able to confirm that the EDID code in misoc deals with the address write issue mentioned above? | 02:25 |
mithro | _florent_: I also thing really need to get a message echoed on the serial console when EDID operations occur on a port. | 02:26 |
mithro | CarlFK: brb | 02:27 |
CarlFK | k | 02:27 |
mithro | back | 02:29 |
mithro | CarlFK: Can you document somewhere your laptop information and how it is connected to the computer? | 02:29 |
CarlFK | mithro: github issue? | 02:30 |
mithro | Yes, you can use one if you want | 02:31 |
*** rohitksingh has quit IRC | 02:40 | |
*** rohitksingh has joined #timvideos | 02:54 | |
CarlFK | mithro: having a monitor hooked up to the output shouldn't matter right ? | 02:58 |
CarlFK | mithro: https://github.com/timvideos/HDMI2USB-misoc-firmware/issues/38 | 03:06 |
tpb | Title: laptop not seeing valid display device · Issue #38 · timvideos/HDMI2USB-misoc-firmware · GitHub (at github.com) | 03:06 |
mithro | CarlFK: correct | 03:44 |
CarlFK | mithro: given that is the only thing I can think of... should I bother unpacking one, or spend the time poking other things> | 03:46 |
CarlFK | ? | 03:46 |
mithro | CarlFK: You could go and have a poke around the EDID code in the firmware and see if you see anything | 03:47 |
mithro | CarlFK: you've tried a whole lot of other devices right? | 03:48 |
CarlFK | mithro: I did last night. including this laptop | 03:49 |
mithro | Do you have a different adapter you can try? This is a mini-DP to HDMI right? | 04:27 |
mithro | CarlFK: can you try the other HDMI input too? | 04:28 |
mithro | BTW Did you get the raspberry pi working in the end? | 04:29 |
mithro | CarlFK: If you get a moment, you should see if you can fix the fpgalink error that comes up when flashing. That is just some simple Python code that should be pretty easy to fix by adding the right try/except bits... | 04:31 |
CarlFK | mithro: hdmi0, no work, but different dmesg I think? http://paste.ubuntu.com/12260503/ | 04:31 |
tpb | Title: Ubuntu Pastebin (at paste.ubuntu.com) | 04:31 |
mithro | 9:25 pm <@mithro> Do you have a different adapter you can try? This is a mini-DP to HDMI right? | 04:32 |
CarlFK | mithro: I never got the pi to do 720p | 04:33 |
CarlFK | no - full size hdmi | 04:33 |
mithro | Was the HDMI2USB detecting the low resolution? | 04:33 |
CarlFK | 640 | 04:34 |
CarlFK | er.. | 04:34 |
CarlFK | not tonight. | 04:34 |
CarlFK | let me try again to be sure | 04:34 |
CarlFK | mithro: pi xrandr default connected 640x480+0+0 0mm x 0mm | 04:36 |
CarlFK | hdmi_in0: 0x0 | 04:36 |
CarlFK | hdmi_in1: 0x0 | 04:36 |
CarlFK | hdp_toggle doesn't have any affect on the Atlys right? | 04:37 |
mithro | It shouldn't | 04:55 |
mithro | Make sure you try both inputs to be certain. | 04:55 |
mithro | BTW you made very sure that your jumpers on the board are configured correctly, right? | 04:56 |
CarlFK | mithro: would it work if they were not? | 04:57 |
CarlFK | I checked a few weeks ago. I was surprised that the 2 jumpers were next to each other. I expected one by each hdmi port | 04:58 |
mithro | It would work unreliable | 04:59 |
CarlFK | oh oh.. I only checked 2. I see there are 3.. | 05:02 |
CarlFK | mithro: is JP2 next to 6 and 7? | 05:05 |
CarlFK | mithro: any idea where a map of the board is so I can look up where JP2 is? | 05:19 |
mithro | CarlFK: I sure there was a screenshot or something in the wiki | 05:20 |
CarlFK | mithro: k - silly me was looking at all the docs like http://www.digilentinc.com/Data/Products/ATLYS/Atlys_rm_V2.pdf | 05:20 |
mithro | CarlFK: the docs should also have it | 05:20 |
CarlFK | mithro: https://github.com/timvideos/HDMI2USB/wiki/Cabling best picture I have found.. any idea where JP2 is? | 05:22 |
tpb | <http://ln-s.net/-DPL> (at github.com) | 05:22 |
mithro | IIRC the jumpers you care about are | 05:24 |
mithro | * Up in the top corner near the HDMI In 0 and the Ethernet port | 05:24 |
mithro | * Down in the bottom corner near HDMI In 2 and the PMOD header | 05:25 |
mithro | They should be marked on the board | 05:26 |
CarlFK | the hdmi in 0 and 1 labels are reversed of what the misoc firmware calls them right ? | 05:27 |
mithro | No idea, sorry | 05:28 |
CarlFK | is JP2 one of the 3 in the lower left? | 05:29 |
CarlFK | on my board, all 3 jumpers are in place, just like the picture | 05:30 |
CarlFK | mithro: what is "HDMI In 2" ? | 05:31 |
CarlFK | found a better image. Still can't find JP2 https://www.terraelectronica.ru/files/ATLYS-top-1200.jpg | 05:33 |
CarlFK | mithro: do you have an Atlys handy? | 05:39 |
mithro | CarlFK: not at this moment | 05:39 |
CarlFK | I can not find JP2 | 05:39 |
CarlFK | nor can I find any doc describing what all the jumpers do. | 05:40 |
CarlFK | mithro: JP2/SDA (which connects the EDID lines from J1/HDMI IN to JA/HDMI OUT). | 05:41 |
CarlFK | I am 1/2 thinking that might be causing the problem I am having tonight with no lcd hooked up | 05:42 |
*** rohitksingh has quit IRC | 05:42 | |
CarlFK | mithro: I give up. | 05:52 |
mithro | CarlFK: So, the only two devices you haven't been able to get working are your RPi and your laptop? | 05:53 |
mithro | CarlFK: can you try other devices you have? | 05:53 |
CarlFK | mithro: I have 4 hdmi sources: | 05:54 |
CarlFK | negk , pi, twist (my laptop) yogi (Sheila's laptop) | 05:54 |
CarlFK | negk is what I have been successfully testing with the last 3 days | 05:55 |
CarlFK | last night when I was trying people's laptops, these two didn't work right away, so I gave up and went on to the next: twist (my laptop) yogi (Sheila's laptop) | 05:56 |
mithro | negk doesn't work now? | 05:56 |
*** rohitksingh has joined #timvideos | 05:56 | |
CarlFK | mithro: correct | 05:57 |
mithro | But it worked yesterday? | 05:57 |
CarlFK | mithro: correct | 05:58 |
mithro | And the Pi worked yesterday? | 05:58 |
CarlFK | not really - I think I saw hdmi_in1: 640x480 but never set that vga_mode and for sure didn't see it displayed on the hdmi out or usb uvc | 05:59 |
CarlFK | I am not sure when I will get another chance to do talks, so I think you should help me get this working tomorrow else there may not be another good chance right away | 06:03 |
CarlFK | mithro: I found SDA... "JP2/SDA (which connects the EDID lines from J1/HDMI IN to JA/HDMI OUT)." | 06:04 |
CarlFK | but it is 2 jumpers, and no JPx label anywhere | 06:04 |
CarlFK | do you know where the "JP2/SDA" instructions came from? | 06:05 |
mithro | There is one jumper which is a 2x2 | 06:05 |
mithro | There are two 1x2 jumpers | 06:06 |
CarlFK | is there some reason you don't say "there are 2 jumpers" ? | 06:07 |
CarlFK | "one jumper" to me sounds like there is only 1. not 2. just 1. | 06:08 |
mithro | Ryan wrote those lines I think | 06:08 |
CarlFK | what were you just trying to tell me about how many jumpers there are? | 06:09 |
mithro | There are three sets of pins which should have a total of 4 little jumpers | 06:39 |
mithro | CarlFK: you understand that each jumper electrically connects one signal | 06:40 |
mithro | CarlFK: there are 4 signals | 06:40 |
CarlFK | sounds like 2 jumpers to me | 06:41 |
CarlFK | anyway, I am too tired now. I asked Ryan what JP2 was. I suspect it is a typo. | 06:42 |
mithro | No, there are 4 of these -> http://www.mcmcse.com/glossary/images/jumper.gif | 06:46 |
mithro | one per signal | 06:46 |
mithro | Two of them go on one 2x2 pin header, the other two go on two separate 1x2 pin headers | 06:53 |
*** MaZderMind has quit IRC | 08:15 | |
*** MaZderMind has joined #timvideos | 08:17 | |
CarlFK | "It's labelled SDA on our boards." swell. | 13:22 |
CarlFK | mithro: pulled jumpers, plugged in, negk sees display ! | 14:42 |
CarlFK | and now I can;t seem to get a /dev/video1 | 14:54 |
CarlFK | juser@dc10b:~$ lsusb | 14:54 |
CarlFK | Bus 002 Device 011: ID 04e2:1410 Exar Corp. | 14:54 |
CarlFK | Bus 002 Device 016: ID 1d50:602b OpenMoko, Inc. FPGALink | 14:54 |
CarlFK | encoder: 1280x720 @ 30fps (22Mbps) from hdmi_in1 (q: 85) | 14:56 |
CarlFK | HDMI1 connected 1280x720+0+0 (normal left inverted right x axis y axis) 200mm x 112mm | 14:56 |
CarlFK | _florent_: mithro ... help... why am I not getting a /dev/video1? | 14:57 |
_florent_ | the fx2 firmware is loadedN | 14:57 |
_florent_ | ? | 14:57 |
CarlFK | _florent_: I think so. how can I check? | 14:58 |
_florent_ | try to do make load-fx2-firmware to be sure | 14:59 |
CarlFK | [76763.270655] uvcvideo: Found UVC 1.00 device HDMI2USB (1d50:60b7) | 15:01 |
CarlFK | thanks | 15:01 |
_florent_ | np, so for the issue with the video input, it was a bad configuration of the jumpers on the Atlys? | 15:09 |
CarlFK | yep | 15:14 |
_florent_ | ok thanks | 15:18 |
*** sb0 has joined #timvideos | 15:28 | |
*** sb0 has quit IRC | 16:04 | |
*** sb0 has joined #timvideos | 16:17 | |
CarlFK | _florent_: well.. something still wonky. | 16:23 |
CarlFK | hdmi_in1: 0x0 | 16:24 |
CarlFK | with 3 different hdmi sources | 16:25 |
CarlFK | negk = hdmi laptop that seems fine when things are working fine. | 16:25 |
CarlFK | _florent_: I want to power cycle and reflash. anything I should check first? | 16:37 |
*** sb0 has quit IRC | 16:40 | |
CarlFK | rebooted all the boxes. | 17:04 |
CarlFK | now I cant get /dev/ttyV* | 17:05 |
CarlFK | sudo m-a b-i vizzini | 17:10 |
CarlFK | got it. | 17:10 |
CarlFK | but negk still no display device | 17:11 |
CarlFK | _florent_: help ;) | 17:14 |
CarlFK | woo. pi ... hdmi_in1: 640x480 | 17:21 |
CarlFK | woo, pi working. mostly. | 17:22 |
CarlFK | about 4 hours left before I head to the meeting and try to use this | 17:30 |
CarlFK | currently in bad shape | 17:31 |
CarlFK | (08:06:42 PM) mithro: _florent_: sorry need to concentrate on finishing this stuff - maybe tomorrow? | 17:36 |
CarlFK | mithro: do you have any time in the next 4 hours? | 17:36 |
mithro | CarlFK: I'm just getting up now | 18:21 |
CarlFK | lol - good morning mithro | 18:21 |
mithro | CarlFK: I only got to bed 4 hours ago | 18:21 |
mithro | CarlFK: you need to figure out what you are doing differently from the times it worked and times it didn't. | 18:22 |
CarlFK | mithro: it would help if I knew what was expected so I could report when what I see deviates from expected | 18:23 |
mithro | I don't understand what you mean | 18:24 |
CarlFK | mithro: I do this: HDMI2USB>video_mode 9 | 18:25 |
CarlFK | Setting video mode to 1280x720 @60Hz | 18:25 |
CarlFK | un/plug pi | 18:25 |
CarlFK | hdmi_in1: 640x480 | 18:25 |
mithro | It is expected that the RPI would output 1280x720 | 18:27 |
CarlFK | that's what I thought | 18:27 |
mithro | So..... | 18:28 |
CarlFK | what video mode is misoc in when it first boots? | 18:28 |
mithro | I don't know of the top of my head. What does the status show when you boot it up? | 18:29 |
CarlFK | hdmi_in0: 0x0 | 18:29 |
CarlFK | hdmi_in1: 0x0 | 18:29 |
CarlFK | hdmi_out0: 1280x720 from hdmi_in0 | 18:29 |
CarlFK | hdmi_out1: 1280x720 from hdmi_in0 | 18:29 |
CarlFK | encoder: off | 18:29 |
CarlFK | ddr: read: 1767Mbps write: 0Mbps all: 1767Mbps | 18:29 |
mithro | Looks like 1280x720 | 18:30 |
CarlFK | so 1280x720 should be the only supported res in the EDID when I plug in a source, right? | 18:30 |
mithro | Yes | 18:30 |
CarlFK | ok. that is one less thing for me to set when I am experimenting | 18:31 |
mithro | You can even go look at the code which generates the EDID if you want to be very sure what the exact content should be. | 18:31 |
CarlFK | I realize it may not be working that way.. but it lets me prioritize what tings I fiddle with | 18:31 |
mithro | CarlFK: I don't know if setting the video mode works different from the state the board comes up in first boot | 18:32 |
CarlFK | nothing I do at the HDMI2USB> prompt should cause the laptop to react, right ? | 18:33 |
CarlFK | given Atlys | 18:33 |
CarlFK | with the exception of reboot - I can see that being a special case | 18:34 |
mithro | Not quite true | 18:35 |
CarlFK | what might cause the laptop to react? | 18:35 |
mithro | Things at the HDMI2USB> prompt change the internal state of the Atlya | 18:35 |
mithro | The laptop could decide to reread that state for any number of reasons outside the Atlys control | 18:36 |
CarlFK | I would not consider that reacting | 18:37 |
mithro | In theory the laptop should only reread the state when the HPD line changes | 18:37 |
mithro | The HPD isn't under software control | 18:37 |
CarlFK | right. | 18:37 |
CarlFK | and that is the only thing that would cause the laptop to do anything, right ? | 18:38 |
CarlFK | like changing res with HDMI2USB>video_mode shouldn't cause the laptop to even be aware of it, right ? | 18:38 |
mithro | If you ran xrandr on the laptop that might force a reread of state | 18:38 |
mithro | CarlFK: At the moment we don't know when a laptop rereads state - so we should assume it happens randomly without warning | 18:39 |
CarlFK | right. the laptop isn't reacting to the video_mode change. | 18:40 |
CarlFK | I am trying to focus on doing things that should work | 18:40 |
CarlFK | sheila just plugged her laptop in - no display device seen | 18:45 |
mithro | The laptop could appear to react to video-mode change if the OS was polling the EDID data | 18:46 |
CarlFK | I am seeing the NAK lines: negk [ 6450.448588] [drm:gmbus_xfer], GMBUS [i915 gmbus dpb] NAK for addr: 0050 w(1) | 18:47 |
mithro | On Sheila's laptop? | 18:47 |
CarlFK | no. she only had time for a quick "plug in, nothing, ok done" and she got back to work | 18:48 |
CarlFK | negk | 18:48 |
CarlFK | also, moving the pi between hdmi0 and 1, I only see hdmi_in1: 640x480 | 18:50 |
CarlFK | no change on hdmi_in0 | 18:51 |
mithro | CarlFK: please explain exactly what you did - I assume "I unpluged the cable going from the RPi to the Atlys port XX and move it to Atlys Port YY and rebooted the Pi" | 18:51 |
CarlFK | when plugged into 0: hdmi_in0: 0x0 | 18:51 |
CarlFK | hdmi_in1: 0x0 | 18:51 |
CarlFK | no rebooting. | 18:52 |
CarlFK | 2 cables, one in 0, the other in 1. move the pi from 0 to 1 back to 0, back to 1.. a bunch of times. maybe 5 times. | 18:54 |
CarlFK | when connected to 1 I see hdmi_in1: 640x480 | 18:54 |
CarlFK | hdmi_in0: 0x0 | 18:54 |
CarlFK | connecting to hdmi_in0 or not connected: hdmi_in0: 0x0 | 18:55 |
CarlFK | hdmi_in1: 0x0 | 18:55 |
mithro | CarlFK: okay - Can you try using the *same* cable? | 18:56 |
mithro | I'm just heading to work | 18:56 |
mithro | will be back in 15-20 | 18:56 |
mithro | Back | 19:12 |
mithro | CarlFK: when changing things, change exactly one thing at a time. In your above example the cable plugged into one of the ports could be dodgy. | 19:13 |
mithro | BTW are you using your crazy in a box thing which has like a ton of cables and connectors? | 19:15 |
CarlFK | mithro: yes. It adds 2 hdmi connections to hdmi_in1 | 19:18 |
CarlFK | and it keeps the same cables held in place. | 19:18 |
CarlFK | so I would call it my sane box thing ;) | 19:19 |
CarlFK | I used the same cable that worked from pi to the cables that lead to hdmi_in1, moved it to hdmi_in0 (on the Atlys) still hdmi_in0: 0x0 | 19:20 |
CarlFK | mithro: I am pretty good about testing cables by plugging into hdmi lcd. they all seem to be in good shape. | 19:22 |
CarlFK | mithro: are you back? (I need to spend 20 min now and then gathering gear for tonight | 19:23 |
mithro | The problem is if the signal integrity is poor or something the LCD might be better at picking it up then the Atlys | 19:23 |
mithro | Less variables! | 19:23 |
mithro | I'm at lunch | 19:24 |
mithro | I also don't have a Atlys board on me | 19:25 |
mithro | I'd really like to help you figure out the problem but it's probably going to take a very systematic approach with as minimal set up as possible until we can get the extra debug stuff I want. | 19:29 |
mithro | I'd really like to help you figure out the problem but it's probably going to take a very systematic approach with as minimal set up as possible until we can get the extra debug stuff I want. | 19:29 |
mithro | I'd really like to help you figure out the problem but it's probably going to take a very systematic approach with as minimal set up as possible until we can get the extra debug stuff I want. | 19:33 |
mithro | Gah. | 19:34 |
CarlFK | new cable - full size -- micro? (whatever my dev laptop uses) getting similar NAKs when plugging in | 19:35 |
CarlFK | http://paste.ubuntu.com/12266005/ [187077.419743] [drm:gmbus_xfer] GMBUS [i915 gmbus dpb] NAK for addr: 0050 w(1) | 19:36 |
tpb | Title: Ubuntu Pastebin (at paste.ubuntu.com) | 19:36 |
mithro | Gah | 19:56 |
mithro | You didn't say my nick so I got distracted. | 19:56 |
CarlFK | mithro: we should have the same boards to test with | 20:06 |
mithro | CarlFK: I have multiple Atlys boards with me - but I didn't get home until 5am this morning so didn't get a chance to try and get things working | 20:11 |
CarlFK | mithro: it wold have saved me an hour or two trying to figure out what J2 meant | 20:12 |
CarlFK | "there is no J2" and take a picture of what you consider correct | 20:12 |
mithro | CarlFK: https://drive.google.com/file/d/0B5VlNZ_Rvdw6UWFGTGJ5RWpoZ1k/view?usp=sharing | 20:15 |
tpb | Title: IMG_8688.JPG - Google Drive (at drive.google.com) | 20:15 |
CarlFK | mithro: that is just the upper left, ? | 20:15 |
mithro | HDMI Out - J2 | 20:16 |
CarlFK | ah. sorry. whatever the jumper*S* were that I was looking for | 20:16 |
CarlFK | little late now | 20:17 |
CarlFK | if you want to connect to the dc10b box that has the 2 usb connections: ssh -p 22174 [email protected] | 20:18 |
CarlFK | mithro: ^^ | 20:20 |
CarlFK | mithro: JP2/SDA (which connects the EDID lines from J1/HDMI IN to JA/HDMI OUT). | 20:20 |
CarlFK | that line needs help. | 20:20 |
CarlFK | I did find SDA, seems to refer to 2 jumpers, I removed them both. | 20:21 |
mithro | https://drive.google.com/file/d/0B5VlNZ_Rvdw6dUtRWnlza0k1MTA/view?usp=sharing | 20:21 |
tpb | Title: IMG_8687.JPG - Google Drive (at drive.google.com) | 20:21 |
mithro | https://drive.google.com/file/d/0B5VlNZ_Rvdw6anZEYjMzaWxfc3M/view?usp=sharing | 20:22 |
tpb | Title: IMG_8692.JPG - Google Drive (at drive.google.com) | 20:22 |
CarlFK | mithro: you have SDA jumpered | 20:23 |
mithro | CarlFK: Have you seen the diagram at -> https://reference.digilentinc.com/atlys:atlys:refmanual#video_input_and_output_hdmi_ports | 20:23 |
tpb | Title: atlys:atlys:refmanual [Reference.Digilentinc] (at reference.digilentinc.com) | 20:23 |
mithro | CarlFK: I just found those pictures | 20:23 |
mithro | https://reference.digilentinc.com/_detail/atlys:atlys:hdmi.png?id=atlys%3Aatlys%3Arefmanual | 20:23 |
tpb | Title: atlys:atlys:hdmi.png [Reference.Digilentinc] (at reference.digilentinc.com) | 20:24 |
CarlFK | mithro: JP2/SDA I see JP2 in that last one. I can't find it on the Atlys board | 20:25 |
mithro | CarlFK: so looking at that diagram - for J1 (HDMI IN) to work correctly with EDID the two jumpers must be *on* JP2 | 20:29 |
CarlFK | oh boy. | 20:31 |
CarlFK | mithro: A) wher is JP2? B) Ryans readme says: | 20:31 |
CarlFK | As the HDMI2USB firmware manipulates the EDID information the following jumpers must be removed; JP2/SDA (which connects the EDID lines from J1/HDMI IN to JA/HDMI OUT). | 20:31 |
mithro | CarlFK: so - there should be two groups of jumpers labelled something like SDA/SCL | 20:36 |
CarlFK | mithro: no more time to work on this today | 20:37 |
CarlFK | please make sure Ryans' read me is correct, and add a picture showing where these jumpers are | 20:37 |
mithro | CarlFK: I'm going to go through the exact same process you are to do the above | 20:38 |
CarlFK | mithro: the following jumpers must be removed; JP2/SDA | 20:39 |
CarlFK | mithro: you said "the two jumpers must be *on* JP2" | 20:39 |
CarlFK | so... | 20:39 |
CarlFK | do what I asked :) | 20:39 |
mithro | CarlFK: so I'm going to look at the code and the diagram and get out a multimeter and try and figure out what the problem is | 20:39 |
CarlFK | that works too | 20:40 |
mithro | CarlFK: but I'm not going to get a chance to do that right now | 20:40 |
mithro | CarlFK: and your smart enough to do this too | 20:40 |
CarlFK | thats fine. I am guessing it is to late to learn anything for tonights talks | 20:40 |
CarlFK | mithro: I am not smart enough to find JP2. | 20:41 |
CarlFK | maybe some day you will help me with that. ;) | 20:41 |
mithro | CarlFK: You should *understand* what is going on - not just try and follow the instructions blindly | 20:41 |
CarlFK | omg | 20:41 |
mithro | CarlFK: Otherwise you'll have to wait for me to do everything | 20:42 |
CarlFK | you told me to follow Ryans | 20:42 |
CarlFK | I have been asking everyone "where is JP2>?" | 20:43 |
CarlFK | even Ryan couldn't really answer that. | 20:43 |
CarlFK | so yes, I am wating on you. | 20:43 |
CarlFK | if you can't fingre it out, then we should all just give up. | 20:43 |
mithro | CarlFK: You are a smart guy - I *know that. Can you try and figure out how you think it *should* work and see if that matches how it does work and then ask questions where things don't match, cross check things in the source code, in the manual, with a multimeter. That is exactly what I will end up doing, I don't have some extra magic.... | 20:51 |
CarlFK | mithro: for tonight, should I put those jumpers back or leave them off? | 20:53 |
mithro | CarlFK: I have NFI - the wiki says off, that diagram indicates on | 20:54 |
CarlFK | lol | 20:54 |
CarlFK | I'll put them back. I think I got beetter results | 20:54 |
mithro | CarlFK: We need to figure out the way we think they should be | 20:55 |
mithro | CarlFK: there also look to be other jumpers which might be relavent | 20:56 |
CarlFK | too late. box is packed. | 20:57 |
*** CarlFK has quit IRC | 21:30 |
Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!