03:12 | i4pro | anyone on thats running a distro on their cubox other geexbox something using X? |
03:32 | jmontleo | i4pro, I have fedora working, but with just fbdev; and i guess probably due to that sound is unsurprisingly not working |
03:33 | i4pro | jmontleo: could you try something from a command line? |
03:33 | jmontleo | sure |
03:33 | i4pro | depending on how you are connected |
03:33 | i4pro | DISPLAY=:0 xrandr --verbose |
03:33 | i4pro | or xrandr --verbose |
03:34 | jmontleo | http://ur1.ca/gg0ov |
03:36 | i4pro | heh |
03:36 | i4pro | your connected via DVI huh? |
03:39 | i4pro | is that right? |
03:39 | i4pro | or rather the DVI port on your TV / monitor? |
03:58 | jmontleo | no, was hdmi |
03:58 | jmontleo | when i ran that not connected to anything |
03:58 | jmontleo | i4pro, ^ |
03:59 | i4pro | hmm ok |
07:26 | MikeSeth | mmmhrm |
07:27 | MikeSeth | put together my own debian root fs, with rabeeh's kernel and uboot + spl |
07:28 | MikeSeth | the cubox won't boot, the display shows 'unsupported resolution' |
07:28 | MikeSeth | what did I miss |
08:01 | jnettlet | MikeSeth, probably the kernel commandline options for resolution |
08:01 | jnettlet | i4pro, I didn't. Yesterday I lost hacking time to snow cleanup |
08:02 | MikeSeth | jnettlet: I switched it out to 720p, still same |
08:02 | MikeSeth | but it does mean the kernel tries to boot, right? I mean uboot itself doesn't initialize hdmi? |
08:02 | jnettlet | MikeSeth, is this in u-boot or linux? |
08:02 | jnettlet | u-boot forces a 1024x768 resolution |
08:02 | MikeSeth | jnettlet: I can't tell |
08:03 | jnettlet | the kernel should still load even if u-boot can't initialize hdmi |
08:03 | MikeSeth | i have a -i1, no serial port, so unless I don't know something there isn't a way for me to diagnose if it craps out on uboot stage or linux |
08:03 | jnettlet | is the front LED coming on? |
08:03 | MikeSeth | the one in ir port? |
08:03 | jnettlet | yep |
08:03 | MikeSeth | yeah |
08:04 | jnettlet | okay then it is booting second stage |
08:04 | MikeSeth | second stage as in kernel? |
08:04 | jnettlet | second stage of the u-boot process |
08:04 | MikeSeth | I need to read uboot documentation then |
08:05 | MikeSeth | is it possible to boot uboot console on hdmi output and usb keyboard? |
08:05 | jnettlet | with SPL the first stage is initializing DDR and machine identification. Then it loads the second stage which does addition device loading. I plan on updating our SPL so it can boot directly to the kernel |
08:06 | jnettlet | a uboot console with usb will be loaded if it detects hdmi and usb keyboard. but your hdmi monitor needs to support 1024x768@50hz |
08:06 | jnettlet | it is still on my list to fix that, but the list is long |
08:06 | MikeSeth | but I need to suppress the autobooting somehow, correct? |
08:07 | MikeSeth | if I want to access uboot console that is |
08:07 | MikeSeth | as of resolution, this is a Samsung 27", it *should* support 1024x768 |
08:08 | jnettlet | yeah it should. we have had reports that some monitors still won't work with the timings in u-boot. |
08:09 | jnettlet | but if hdmi is detected you will see the display before the autoboot timeout countdown kicks in |
08:09 | jnettlet | I have it loading very early |
08:10 | MikeSeth | it never happens to me when booting debian; the screen is blank until after the kernel has been loaded |
08:10 | MikeSeth | also maybe the hdmi splitter is causing this |
08:10 | jnettlet | oh that is most likely not helping things |
08:11 | jnettlet | it is possible the hdmi splitter does not support the timings |
08:11 | MikeSeth | if I write just the spi and uboot image on a blank card, no fs/partition table, uboot would still boot, right? |
08:11 | jnettlet | yep |
08:11 | jnettlet | it reads directly off the raw blocks of the sdhc card |
08:12 | MikeSeth | oh another question, the way i create card images is first (0) entry in the partition table is empty, do you know if /dev/mmcxpy would renumber them? |
08:12 | MikeSeth | though it doesn't really matter |
08:13 | MikeSeth | i'll go experiment |
08:17 | MikeSeth | ok, samsung displays don't like 50hz |
08:17 | MikeSeth | their official support response is use 60 |
08:18 | MikeSeth | hack uboot for a 60hz timing? |
08:19 | MikeSeth | i probably hosed the kernel or the root fs somehow, that's why it won't boot, hrm |
12:16 | jnettlet | _rmk_, do you have the device-tree snippet to enable the battery backed rtc handy? |
14:33 | cardiel | i have a horizontal line in the bottom when playing videos that has other aspect ratio than 16:9 ( for ex. 2:39,1:85 ) , is this a geexbox bug or hardware? |
17:15 | jnettlet | _rmk_, did you end up getting the wifi module loading via device-tree before you gave up in a fit of rage ;-) |
17:18 | _505 | rabeeh, do you mind if I publish instructions on how to install Google Play, or would that harm the certification process? |
17:23 | jnettlet | _505, it is probably best if rabeeh doesn't answer that :-) I think I can safely say if you want to post whatever you have accomplished found out on your own blog, or part of the internet and then link to it in the forums/IRC then that is probably fine. |
17:24 | _505 | okay, I'll do that then. thanks |
17:24 | jnettlet | Really the certification process is not like a weird Google is going to spank you kind of process. It is more about verification that your device will run most the apps in the appstore without lots of problems by the users |
17:26 | jnettlet | but thanks for respecting SolidRun and asking first :-) |
17:26 | _505 | yeah, I know Cyanogen had problem with distributing GApps included, so now it is a separate download |
17:27 | jnettlet | yep |
18:05 | matoking | Is there anyone who has had his Cubox-i delivered that had the estimated shipping date of January 15th? |
18:08 | davorin | i never got an estimated shipping date (o; |
18:09 | matoking | Well |
18:09 | davorin | but something was shipped on january 16th |
18:09 | matoking | The thing is, I originally ordered a Cubox-i2Ultra |
18:09 | davorin | at least my i4pros |
18:09 | matoking | I changed the order for a Cubox-i4Pro |
18:09 | matoking | And I received the estimated shipping date after that |
18:09 | davorin | i2u and i2 are difficult right now |
18:09 | davorin | as i heard |
18:09 | matoking | But yeah |
18:09 | matoking | I hope I get it soon |
18:10 | matoking | I'm itching to start working on it :P |
18:10 | davorin | hope i get my 10 i1 and 10 i4pro next week to test with again |
18:10 | matoking | You bought ten of both? |
18:10 | davorin | yepp |
18:10 | matoking | What are you planning on doing with them? |
18:10 | davorin | waiting to order i2s and more i4pros |
18:10 | davorin | reselling here in switzerland |
18:10 | matoking | Oh |
18:11 | davorin | but dumped a10/a20 for i.mx6 ;-) |
18:11 | matoking | I saw a Raspberry Pi based cluster on Youtube |
18:11 | matoking | I was wondering if you were planning on doing something like that with those Cuboxes :P |
18:11 | davorin | ah no (o; |
18:12 | davorin | swiss market is saturated with raspberries..so i.mx6 is next logical step... |
18:12 | matoking | Well I've already made my plans of what I'll do with the Cubox once I get it |
18:12 | davorin | an especial looking forward for the som module |
18:13 | _rmk_ | jnettlet: the wifi module is unsupportable at the moment with DT - there's just no way to do it yet. |
18:13 | davorin | ah, 1 * i4pro will replace my crap popcorn hour (o; |
18:13 | matoking | It feels like 90% of the people are buying it to make a media center |
18:13 | _rmk_ | jnettlet: there's no way at present that DT can specify the GPIO signals to control the resets nor the power to the crystal/wifi module. |
18:13 | davorin | well...ble inside is nice to have to experiment with beacons and stuff |
18:14 | matoking | I'm planning on making it a NAS, BitTorrent client, a local web development server and some other things |
18:14 | _rmk_ | jnettlet: so until that infrastructure is in place, there's no way it can be supported. |
18:14 | matoking | Maybe run a Bitcoin node on it |
18:14 | davorin | or for digital signage, info displays with touchscreens |
18:14 | davorin | i expect to run kivy even better on cubox than on rpi |
18:15 | davorin | but i was surprised even the i1 can handle blurry rip with dts-hd 5.1 software decoding (o; |
18:15 | davorin | s/blurry/blu-ray/ |
18:15 | _rmk_ | jnettlet: I did try rigging up the wifi power control as vmmc for the mmc host, but that doesn't result in it being detectable |
18:17 | davorin | well for has i would recommend a hp n40l or bigger...has 4 data trays and supports an ilo card |
18:17 | davorin | und install nas4free... |
18:25 | matoking | @davorin At the moment I'm only planning on plugging in the external USB HDD I have |
18:26 | davorin | (o; |
18:26 | matoking | @davorin Since it's USB 2.0 it won't get the best speed but the main bottleneck is the router as far as I know |
18:26 | davorin | you get a i4pro, right? |
18:26 | matoking | @davorin That, and it should work faster than running the OS on theSD card |
18:26 | matoking | Yes |
18:26 | davorin | why not use esata? |
18:26 | matoking | I didn't find any HDDs that supported it |
18:26 | davorin | probably you could even boot from it |
18:26 | matoking | At least, not any HDDs from brands I've used it |
18:27 | davorin | ah, i just ordered two esata cases to place my own drive in |
18:27 | jnettlet | _rmk_, hrmph |
18:27 | Thijx | howdy |
18:27 | matoking | @davorin So you are plugging your ordinary SATA drives in a case which allows you to connect them to the Cubox-i using the eSATA connector? |
18:27 | davorin | yepp |
18:28 | matoking | Nice |
18:28 | davorin | lemme check the brand... |
18:28 | matoking | I'll be sure to keep that in mind if I ever need more storage |
18:28 | davorin | well..i just use esata for performance testing (o; |
18:29 | davorin | this one i got: http://www.raidsonic.de/en/products/details.php?we_objectID=7293 |
18:29 | davorin | in my living room then i just use my nas |
18:30 | davorin | and rooms are connected via fibre cables ;-) |
18:30 | davorin | easier to drill holes (o; |
18:31 | _rmk_ | davorin: now, here's the question - does that connect the esata cable directly to the drive, or is there a chip between the esata connector and the drive connector... |
18:31 | _rmk_ | and I don't mean the USB bridge chip |
18:31 | davorin | lemme open the case....if it has a buffer chip in between |
18:31 | _rmk_ | because... this is the one I have on the dove cubox: http://www.raidsonic.de/en/products/external-cases.php?we_objectID=6831 |
18:32 | _rmk_ | and that doesn't have a buffer chip, it just has a Jmicron USB to SATA bridge chip |
18:32 | _rmk_ | ... and it's particularly poor and unreliable when operating in USB mode |
18:37 | davorin | well it has a asm1501 usb/sata bridge and a asm1453 sata muxer |
18:37 | davorin | guess for level correction as esata supports 2m cable length |
18:37 | davorin | so for your question: sata is directly connected via buffer to esata |
18:38 | davorin | should also be in your case |
18:38 | davorin | as i see it has esata as well |
18:38 | davorin | http://www.asmedia.com.tw/eng/e_show_products.php?item=107&cate_index=101 |
18:40 | _rmk_ | lemme shut the cubox down and I'll open it up and take photos... for you, and then you can run away from the 319 with all the facts at hand :) |
18:49 | _rmk_ | http://www.home.arm.linux.org.uk/~rmk/cubox/IMG_1590.JPG |
18:49 | _rmk_ | it also holds the drive in a rather crappy way inside the box: |
18:49 | _rmk_ | http://www.home.arm.linux.org.uk/~rmk/cubox/IMG_1585.JPG |
18:50 | _rmk_ | here's the full bottom-side PCB view: |
18:50 | _rmk_ | http://www.home.arm.linux.org.uk/~rmk/cubox/IMG_1587.JPG |
18:50 | _rmk_ | and top side: |
18:50 | _rmk_ | http://www.home.arm.linux.org.uk/~rmk/cubox/IMG_1586.JPG |
18:50 | _rmk_ | The USB to SATA bridge is a JM20329 |
18:51 | davorin | jmicron... |
18:52 | davorin | looks like straight connection from sata to esata connector |
18:52 | davorin | via capaicors c1 - c4 |
18:52 | davorin | capacitors |
18:52 | _rmk_ | exactly |
18:53 | _rmk_ | it detects the presence of the eSATA cable, and holds the jmicron chip in reset or similar |
18:53 | davorin | so it should work with your i4pro |
18:54 | _rmk_ | yep, provided it's a short esata cable |
18:54 | davorin | do you want a noisy hd in your living room? (o; |
18:54 | _rmk_ | the WD800 is nice and quiet |
18:55 | davorin | not much room for movies though |
18:56 | _rmk_ | true, it's only a local store and rootfs for the cubox (so it's fast)... I found SD too slow... that stuff is on my N2100 :) |
18:57 | davorin | also sdxc slow? |
18:58 | _rmk_ | I may switch over to using SSDs for the cuboxes |
18:58 | davorin | that's why i wait for rabeeh to give me the msata/mini-pcie pinout of the c1 board |
18:58 | _rmk_ | right, while I have the thing off of the cubox, I'll try it on the cubox-i... |
18:59 | davorin | well...you could also mount root over nfs |
18:59 | davorin | or boot even kernel from |
18:59 | davorin | i'm happy with this one: http://www.amazon.de/ProLiant-MicroServer-Hot-Plug-f�hig-Netzteil-Server/dp/B00AHQUX86/ref=pd_cp_computers_0 |
19:00 | davorin | 4 * 4tb as zfs, giving you 12tb |
19:00 | _rmk_ | I do that on the cubox-i and hummingboard, but I didn't want to tie the cubox to my network |
19:00 | _rmk_ | I've taken it away an number of times and demo'd it in places |
19:00 | davorin | well if you have no network, then you also have no movies from your nas |
19:00 | _rmk_ | which is why I copy over the content I want to the local HD :) |
19:01 | davorin | or get this box: http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-kit-dccp847dye.html |
19:02 | _rmk_ | what's the point of the cubox with that :) |
19:02 | davorin | no one (o; |
19:03 | _rmk_ | ok, my dt stuff for esata isn't working |
19:03 | davorin | dt? |
19:03 | _rmk_ | device tree |
19:04 | davorin | #define isn't working |
19:05 | jnettlet | _rmk_, ? mine is being detected but I have misplaced my esata drive so haven't tested functionality. |
19:06 | jnettlet | The hardware is detected and initialized |
19:06 | _rmk_ | yes... |
19:06 | _rmk_ | ahci ahci: SSS flag set, parallel bus scan disabled |
19:06 | _rmk_ | ahci ahci: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode |
19:06 | _rmk_ | ahci ahci: flags: ncq sntf stag pm led clo only pmp pio slum part ccc apst |
19:06 | _rmk_ | scsi0 : ahci_platform |
19:06 | _rmk_ | ata1: SATA max UDMA/133 mmio [mem 0x02200000-0x02203fff] port 0x100 irq 71 |
19:06 | _rmk_ | ... |
19:07 | _rmk_ | ata1: SATA link down (SStatus 1 SControl 300) |
19:07 | _rmk_ | it finds the host interface but not the drive |
19:08 | _rmk_ | hmm |
19:08 | _rmk_ | root@cubox-i4:~# ./devmem2 0x20e0034 |
19:08 | _rmk_ | Value at address 0x20E0034 (0xb6f5f034): 0x593E4A4 |
19:08 | _rmk_ | the phy isn't being enabled |
19:11 | Thijs_ | Hi there, anyone know how to get headless debian going? |
19:12 | jnettlet | well first you need to hold it down and yell run run, then you chop its head off. That should get you going for 30 seconds to a minue |
19:12 | jnettlet | minute |
19:13 | Thijs_ | ok, great Ill try that |
19:13 | Thijs_ | but before the beheading, is there any img I can install? |
19:13 | jnettlet | Thijs_, check the forums. I believe someone posted an image |
19:14 | davorin | btw: what are people using for host os? debian 7.3? |
19:14 | Thijs_ | All I find is a directory structure but I don know what to do with it. The CuBox installer is also nog helping, there is no guide/manual/installation document |
19:14 | davorin | and which xgcc, the eabi package or selfbuilt? |
19:14 | jnettlet | Thijs_, the Cubox installer only works for the original cubox. Do you have a cubox or a cubox-i? |
19:15 | Thijs_ | This: http://www.solid-run.com/mw/index.php/Debian_armhf_server is something but there is no img I can use with dd |
19:15 | Thijs_ | I have the pro |
19:15 | davorin | rabeeh made some images lately |
19:15 | jnettlet | there is a pro for the cubox and cubox-i |
19:15 | davorin | look on the cubox-i wiki pages |
19:16 | Thijs_ | I'm in the Wiki. There is no image. |
19:17 | davorin | http://imx.solid-run.com/wiki/index.php?title=Debian_and_derivatives |
19:17 | davorin | http://download.solid-run.com/pub/solidrun/cubox-i/Debian/Jessi-repackaged-trial/ |
19:18 | Thijs_ | Jessi is with X and had no ethernet/dhcp support |
19:19 | Thijs_ | Ubuntu runs great but it? a full-fledged gui |
19:19 | _rmk_ | nope, can't get it to work on the cubox-i... just moved it back to the cubox, where it works. |
19:21 | Thijs_ | I think I'll give Arch a try |
19:22 | _rmk_ | hmm |
19:22 | _rmk_ | Disable link to save power. An imx ahci port can't be recovered |
19:22 | _rmk_ | without full reset once the pddq mode is enabled making it |
19:23 | _rmk_ | impossible to use as part of libata LPM. |
19:29 | _rmk_ | it's the small things which would make this stuff a little more friendly... such as, when we put a port into an unreversable power down mode, printing a message to say that's been done and how to avoid it. |
19:30 | _rmk_ | eg, printing in this scenario: |
19:30 | _rmk_ | "no device found, disabling link.\n" |
19:30 | _rmk_ | "pass ahci_imx.hotplug=1 to enable hotplug.\n" |
19:32 | _rmk_ | and yes, with the right phy settings... |
19:32 | _rmk_ | scsi 1:0:0:0: Direct-Access ATA WDC WD800JD-00LS 06.0 PQ: 0 ANSI: 5 |
19:34 | davorin | btw: is there like a console video player like omxplayer for rpi? |
19:34 | davorin | or is something in the freescale bsp included? |
19:40 | MikeSeth | jnettlet: yesterday you told me uboot would initialize hdmi to 1024x768@50Hz, did you mean 60 instead of 50? |
19:41 | MikeSeth | Thor___: Jessi image worked for me |
19:43 | Thijs_ | Even Arch does not work :( |
19:43 | Thijs_ | Again no ethernet, maybe I have a broken unit |
19:45 | davorin | have you tested enet works with geexbox? |
19:46 | MikeSeth | Thijs_: does it show in lshw output? |
19:47 | Thijs_ | yes, that? crazy, it updated a scarper so it must be working |
19:48 | Thijs_ | but running only xbmc on my i4pro is not great :D |
19:49 | Thijs_ | Android is also working but I have no clue how to control Android on my non-touch TV :s |
19:49 | MikeSeth | wait, ethernet does work for you in xmbc? |
19:49 | MikeSeth | plug in a mouse |
19:49 | Thijs_ | geexbox seems to handle the eth |
19:49 | Thijs_ | debian and arch not |
19:50 | MikeSeth | Thijs_: in hste's jessi image the network device isn't configured by default |
19:51 | MikeSeth | you need to bring it up manually and run a dhcp client, or configure it in /etc/network, did you do that? |
19:52 | Thijs_ | yes, with ifconfig eth0 up |
19:53 | Thijs_ | and then dhclient eth0 or somthing |
19:53 | Thijs_ | then I got the 'timer error', let me look it up |
19:53 | Thijs_ | "Unable to set up timer" |
19:54 | jas-hacks | jnettlet: hi, with 3.10.17 kernel do you get a hang with hdmi connected to a monitor while kernel boots? |
19:54 | MikeSeth | oh, jas-hacks! you won't happen to be an uboot wizard would you? |
19:55 | jas-hacks | MikeSeth: what is the issue? |
19:55 | MikeSeth | Thijs_: that is.. very bizzare, which kernel version? |
19:55 | MikeSeth | jas-hacks: my monitor doesn't seem to like the timings uboot uses for its hdmi console |
19:56 | MikeSeth | I was wondering how these were derived in uboot cubox code and if it would make sense for me to play with them |
19:57 | jas-hacks | MikeSeth: so it's not displaying the default resolution when uboot boot? |
19:58 | Thijs_ | MIkeS, can't say but it's with this Arch: http://imx.solid-run.com/wiki/index.php?title=ArchLinux and with this Debian: http://download.solid-run.com/pub/solidrun/cubox-i/Debian/Jessi-repackaged-trial/ |
19:58 | MikeSeth | jas-hacks: yeah, it's a samsung 27" smart lcd/tv and it says "Unsupported resolution" |
19:58 | MikeSeth | Thijs_: uname -a |
19:58 | Thijs_ | I know but the box is down and I re-used the microsd for another distro to try.. |
19:58 | jas-hacks | MikeSeth: in the kernel or uboot? |
19:58 | MikeSeth | jas-hacks: when the kernel boots it initializes the video just fine |
19:59 | MikeSeth | but if uboot fails to load the kernel then I can't see it's output |
19:59 | jas-hacks | MikeSeth: in uboot there is a hardcoded resolution |
20:00 | MikeSeth | jas-hacks: yes, I am looking at the code that sets it up, my question was, what is the origin of the timing information for that resolution |
20:01 | MikeSeth | Thijs_: this absolutely did not happen to me :( |
20:01 | hste | Thijs_: You could try the linux installerscript and see if that works. Network should work with it http://stende.no-ip.info/imx6/solidrun-hb/scripts/mk_jessie-lxde_hb.sh |
20:02 | jas-hacks | MikeSeth: should be a standard xga mode (1024x768) |
20:03 | Thijs_ | @hste, I'll try that, thanks. Be back later with an update. |
20:04 | jas-hacks | MikeSeth: You can change it in the code and give it a try |
20:05 | MikeSeth | jas-hacks: I am going to |
20:05 | MikeSeth | jas-hacks: is there support for display probing in uboot? |
20:06 | jas-hacks | MikeSeth: don't think it is implemented |
20:07 | jas-hacks | because the EDID stuff doesn't always work |
20:07 | MikeSeth | you mean in cubox hardware? |
20:08 | jas-hacks | no the uboot code |
20:08 | MikeSeth | oh |
20:08 | MikeSeth | oh right I remember someone mentioning it |
20:09 | MikeSeth | do you know what pixclock value is expressed in in fb_videomode? as hz it doesn't seem to make sense |
20:09 | MikeSeth | though never mind me I'll do calculations |
20:11 | _rmk_ | mikeseth: yes, it's a known bug in uboot |
20:11 | _rmk_ | uboot actually produces something like a 52Hz refresh rate which various TVs absolutely hate |
20:11 | jas-hacks | MikeSeth: most of the modes are defined in the kernel so you should be able to find the values there |
20:12 | _rmk_ | my panasonic tv refuses to display uboot stuff |
20:12 | _rmk_ | but my samsung monitor can display that |
20:13 | MikeSeth | _rmk_: I have the opposite, my samsung monitor won't |
20:14 | _rmk_ | out of interest, which model? |
20:14 | MikeSeth | _rmk_: LT27B300 |
20:16 | MikeSeth | I want to understand though, is there a problem with how uboot interprets mode data? why'd the 60hz mode turn into 53hz? |
20:16 | _rmk_ | mine's an LS24C750PS |
20:17 | _rmk_ | in uboot, it's a hard-coded mode, but there's something not quite right with the clocking |
20:17 | _rmk_ | it's something that jnettlet has on his list of things to look at |
20:18 | jas-hacks | what you could try is to read the EDID from the TV from the uboot cmd line using i2c to see what it sends back. |
20:18 | MikeSeth | this is a -i1 without the serial port |
20:19 | MikeSeth | any other way to access i2c? |
20:19 | MikeSeth | also do note I have very little idea what I'm doing here ;) |
20:23 | _rmk_ | not from uboot, it's a chicken'n'egg problem |
20:24 | jas-hacks | MikeSeth: once the kernel has booted, you can try reading the EDID as well. However I don't have the info at hand, i had a similar issues, with 2 different hdmi-2-vga adapters. They both behaved differently |
20:25 | MikeSeth | okay, here's what I am going to do |
20:25 | MikeSeth | I'll boot into linux, dump and decode edid the monitor serves |
20:25 | MikeSeth | then I'll do the mode calculation with uboot's timings by hand |
20:25 | MikeSeth | then I'll compare the two and see what happens |
20:25 | MikeSeth | makese sense? |
21:27 | MikeSeth | just tried the uboot's mode with fbset, and the display supports it |
21:28 | MikeSeth | which probably means uboot is doing something funny with the numbers |
21:39 | MikeSeth | I am trying to read off edid from /dev/i2c-x using ddccontrol, it says both /dev entries are 'unusable' with -3 |
21:39 | MikeSeth | hints anybody? |
21:44 | jas-hacks | MikeSeth: cat /sys/devices/platform/mxc_hdmi/edid |
21:45 | MikeSeth | jas-hacks: what are /dev/i2c-x for? |
21:47 | jas-hacks | they are i2c devices but you can't read them without i2c protocol |
21:53 | MikeSeth | what do you parse the ascii hex dump with? |
21:53 | MikeSeth | parse-edid doesn't like it |
21:57 | MikeSet | 21:57 * MikeSeth discovers i2cdump |
21:58 | jas-hacks | MikeSeth: just google you will find an edid parser |
21:59 | MikeSeth | jas-hacks: sorry for noob questions |
22:02 | jas-hacks | MikeSeth: http://www.edidreader.com/ |
22:03 | MikeSeth | jas-hacks: yeah, found already |
22:05 | MikeSeth | there appears to be nothing wrong with the video mode in uboot, the same timings work just fine with fbset |
22:06 | MikeSeth | some problem with uboot's hdmi initialization? |
22:08 | jas-hacks | why don't you try a hdmi mode (720/1080p) in uboot |
22:10 | MikeSeth | good idea |
22:13 | MikeSeth | any way to do so w/o editing the timings in source and recompiling uboot? |
22:14 | _rmk_ | mikeseth: yes, and I explained earlier, the uboot mode timings are incorrect. they're being clocked about 10% or 12% slow because of a bug. |
22:15 | _rmk_ | this has nothing to do with edid or anything like that - it's merely that the timing/clock parameters which are being set by uboot are somehow wrong. |
22:15 | _rmk_ | the current thinking is that the timings being programmed into the IPU are correct, but the clock driving the IPU is wrong. |
22:16 | _rmk_ | that results in rather than a refresh rate of 60Hz, we generate something like 52Hz instead |
22:16 | MikeSeth | oh, now that makes perfect sense |
22:18 | _rmk_ | the clock tree which feeds the IPU is really complicated, so tracking down where the problem is isn't easy. |
22:19 | MikeSeth | can I compensate by introducing offsets to cover the gap? |
22:20 | MikeSeth | also, if this is a problem with how the clock is driven then I presume the problem would persist for any mode? |
22:46 | Thecko | Hi, anyone active in here? |
22:51 | MikeSeth | depends on what you consider active |
22:53 | Thecko | heh, fair question :) |
22:54 | Thecko | I've posted the question on the forums but wondered if anyone here might know ... the kernel being built by geexbox at the moment, does it support setting the amount of memory reserved for the gnu? I've modified my boot.scr and /proc/cmdline shows it was passed as a param, but doesn't seem to have increased the userspace memory available :( |
22:54 | _rmk_ | No, we're all sitting around being idle, storing up health problems for the future through lack of exercise. :) |
22:54 | Thecko | that should say gpu, not gnu - this stupid irc client is autocorrecting |
23:50 | Thijs_ | @hste, the script works great |
23:50 | Thijs_ | I now run Debian with the eth |