/srv/irclogs.ubuntu.com/2012/07/27/#ubuntu-arm.txt

BV1ALI connected USB HUB to the OTG and it work for my keyb/mouse when I boot TI Blaze with Android ICS.06:36
BV1ALBut if I boot ubuntu-12.04-preinstalled-desktop-armhf-omap4 on TI Blaze, and with the same connection(USB HUB keyb/mouse)06:36
BV1ALthe keyb/mouse has no any response even though I can see the Ubuntu desktop on HDMI monitor06:37
BV1ALwhat can I do to solve this problem ? so I can start to configure Ubuntu.06:37
scientesBV1AL, AFAIK OTG ports are reverse ports06:39
scientesso they don't work for what you want06:39
BV1ALso this means I cannot run Ubuntu ? but only ICS ?06:42
scientesnono06:42
BV1ALbecause the keyboard on Blaze has no any response when I boot to Ubuntu06:42
scientesBV1AL, can you login via ssh?06:43
BV1ALso I need a external keyb06:43
BV1ALit has no network connection even I plug the ethernet to Blaze06:43
scientesthen you need to log in via the serial console06:43
BV1ALserial port has no any response either06:44
BV1ALthe monitor waiting me to select language for the system, but I can do nothing06:45
scientesdid you unplug and replug in the keyboard?06:46
BV1ALyes I did06:47
scientesdid you try with no hub?06:47
scientesanyways serial port is your best bet06:48
BV1ALin the beginning, the serial has messages06:49
BV1ALbut right after "Uncompressing linux... done, booting the kernel" it has no any response06:49
scientesahh then its a bug in ubuntu06:49
scientesor in the parameters you are passing to the kernel06:50
scientesshoudl pass something like console=ttyS0,1152006:50
BV1ALwhen I type printenv, it has this console=xxxx06:50
scientesthats wrong06:50
scientesneeds to be the above06:51
scientesbut its "bootargs" that is the important variable06:51
BV1ALno, I mean it has the console=tty(something,speed06:51
scientesyou have to study how it is booting before messing around06:51
scientesoh06:51
scienteswell it might be good, and it might not06:51
scientescause it has to pass it to the kernel too06:51
scientesvia the bootargs variable in uboot06:52
BV1ALok I'll try later06:52
BV1ALdoes this mean even I can login through serial port and configure, I still cannot use external keyb/mouse ?06:53
scientesserial port is with an external input06:54
scientesthat is why serial is the universal debug port, its the simplest06:54
BV1ALbut if everything need to send through serial port, this mean I have to depend on another PC06:56
BV1ALI wish to run Ubuntu on Blaze not debug06:57
scientesof course06:57
scientesbut you need to run evtest to figure out what is going on with the keyboard/mouse06:57
scientesand dmesg06:57
BV1ALI see, thanks06:58
BV1ALthe OTG port under ICS can act either master/slave mode depend on the microUSB I plugin07:06
BV1ALI wonder how to configure Ubuntu to let OTG port do exactly the same as ICS did ?07:08
BV1ALthere are some demo on Youtube that they running Ubuntu on TI Blaze, how did they setup the external keyb/mouse ?07:09
BV1ALor the Ubuntu they do demo on Youtube different with the image they release for people to download ?07:11
scientesyou need the usb port to be in host mode07:13
BV1ALI knew, so I plug in a microUSB with pin4-pin5 connected, this make it act as host07:14
BV1ALand this work as expected under ICS07:14
scienteswell you need that serial port so you can read the kernel log07:15
scientesand then start sending in patches07:15
scienteswhen you fix it07:16
BV1ALis it possible to get the Ubuntu image some people demo successfully on TI Blaze ?07:18
BV1ALI think they did fixed it, otherwise hwo do they demo ?07:18
scientesi know nothing about that hardware07:19
scientesyou have a page on the stats?07:19
BV1ALhttp://www.omappedia.org/wiki/OMAP4_Blaze07:20
scientesooo thats pretty07:21
LetoThe2ndscientes: its TI's super-expensive omap4 dev platform07:23
suihkulokkifsov "super-expensive"07:24
LetoThe2nd?07:24
suihkulokkiif you actually are going to make an omap4 product, a blaze will be rounding error in the whole budget...07:26
LetoThe2ndsure, if you are into the omap4 production market thats totally irrelevant07:26
LetoThe2ndbut there are those folks who want to just tinker around a bit on the omap, and compared to the panda its justified to call it expensive.07:28
suihkulokkiwell blaze isn't targeted for tinkerers07:30
LetoThe2ndi never said it was. i just called it expensive. :)07:31
ogra_blaze is a dual screen elephant cellphone ... only buy it if you also have the elephant to use it :P08:09
phh:)08:10
phhi didn't remember it could phone08:10
ogra_it has a SIM slot08:10
LetoThe2ndogra_: not a SOM slit?08:11
ogra_not sure we ever had a driver ...08:11
phhbut yeah, the blaze is here only for people who uses omap4 to complain to TI "see, it doesn't work for you either !"08:12
ogra_heh08:13
phh(yup that's from experience.)08:13
ogra_well, it was available before the panda at least  ... without blazes the ubuntu port would have been a release later08:14
ogra_infinity, any opinion ? http://paste.ubuntu.com/1113920/14:50
infinityogra_: .d is a misleading name for that directory.14:57
ogra_just /etc/flash-kernel/bootscript/ then ?14:57
infinityogra_: One expects .d directories to be full of snippets that get reconstructed.14:57
ogra_k14:57
infinityogra_: Yeah, just mirroring the layout in /usr/share with bootscript/ seems sane.14:58
infinity(Though, I wouldn't be against designing a .d system where one could drop in bits, it's probably overkill)14:58
ogra_my next step would be to make f-k-i cp the input file from /usr/share/flash-kernel/bootscript/ and make f-k check for its existence14:59
infinityWell, you just made f-k look for it.14:59
ogra_and after that we should look into setting root= from f-k-i so we arent depending on initrd's14:59
infinityAlso, this doesn't necessarily need to be a directory in /etc at all.15:00
infinityWhy break past assumptions?15:00
infinityCan't we just use /boot/$usname ?15:00
ogra_you mean reading /boot/boot.script ?15:00
ogra_no15:00
ogra_$usname differs from boot.script15:00
ogra_it carries the subarch name15:01
infinityAhh, so it does.  But that's fine.15:01
infinityIt's still where people expected it to live.15:01
infinityAnd it's not a conffile.15:01
ogra_sure, but if we abuse /boot for configs again i would like to have backwards compatibility15:01
infinity*shrug*15:01
ogra_f-k-i should copy it from /usr/share/flash-kernel/bootscript/ to /boot/boot.script then15:02
infinityIt's probably more correct to have it in /etc anyway.15:02
ogra_adn f-k should respect that15:02
ogra_why ? /etc is for configs or did that change15:02
infinityI was just thinking about people's assumptions, not about backward compat, per se.15:02
ogra_i was always shouted at for putting it into /boot15:02
infinity09:02 < infinity> It's probably more correct to have it in /etc anyway.15:02
infinity^-- I just said that. :P15:02
ogra_(though i still think its the most logical place)15:03
infinityAnyhow, drop the .d from that patch, and it seems sane enough to me.15:03
ogra_oh. sorry, misread more as not ...15:04
* ogra_ is melting, germany has a heatwave15:04
ogra_ok15:04
infinityOr maybe even just /etc/flash-kernel/$whatever15:04
infinityThere's nothing else being shipped in that directory, seems weird to have an empty directory just to contain another one.15:04
ogra_yea, less typing ... i wasnt sure we wouldnt have other stuff in there in the future15:05
infinityEven if we do, the bootscr.platform stuff is well-named.15:05
infinityAnd it's not like you'll have 30 of them.15:05
infinityNot in /etc anyway.15:05
ogra_and i would like to prevent having to migrate configs around more than i have to for release upgrades15:05
infinitySince you should really only have the one for the platform you're running.15:05
ogra_ok, i'll cut it15:06
=== TRON is now known as TypoNAM
ogra_infinity, so steve just convinced me to use /etc/default/flash-kernel and there only stote the additional cmdline options ... and them make f-k append these on boot.scr generation15:35
infinityThat works too.15:36
infinityI'm not picky.15:36
ogra_sure. just a bit more work15:36
infinityThough, I thought there was a drive in Debian to deprecate /etc/default in general for wheezy+115:36
ogra_that way we have an easy place to set root= too15:37
ogra_in favour of ?15:37
infinityJust making it go away.  Not necessarily replacing it with anything. :P15:37
ogra_heh15:38
ogra_that doesnt sound well thought through15:38
ogra_rsalveti, any PVR news ?15:44
rsalvetiogra_: I just tested with latest compiz + precise unity and things seems to be working nicely15:45
ogra_YAY, one positive thing at least15:45
rsalvetithere's still an annoying bug but at least it's not dumping anything at the sgx side15:46
ogra_(seems compiz is still not ready)15:46
rsalvetinot yet, I'm using the branch people are still working on15:46
rsalvetibut I must say I'm quite happy with the results15:46
rsalvetipeople are finally merging the stuff back15:46
rsalvetiand fixing a few other issues as well15:46
rsalvetiso I'll be working at getting the driver at ubuntu in a few, now that the linaro release is done15:46
ogra_well, as long asd it lands in the ubuntu packages i will be happy too :)15:46
rsalvetiyeah, probably before feature freeze I'd say15:47
ogra_but compiz is pretty closely bound to feature freeze15:47
ogra_yeah15:47
rsalvetiyup15:47
infinityIs this all still build-time selection, or have we moved on to runtime yet?15:48
ogra_compiz you mean ?15:48
ogra_that should be runtime since GLES is also available on some intel chips nowadays15:48
infinityThe GL/EGL stuff in compiz, nux, and unity.15:48
infinityYes, it *should* be runtime selected, but it wasn't in precise. :P15:48
infinityHence the question.15:48
ogra_but i dont know how much the reality matches "should"  :P15:49
ogra_i know it was disxcussed that way at UDS15:49
rsalvetihm, not that sure if this will land (runtime selection) at quantal15:49
rsalvetifirst thing I want to see is the code merged15:50
ogra_++15:50
rsalvetiand not maintaining that huge patch set anymore15:50
rsalvetiafter that we can discuss new features ;-)15:50
ogra_++++++++ !15:50
infinityFair enough.  Just as long as runtime selection is on someone's radar.15:51
infinityRight now, it matters for x86.  In the future, I bet it'll matter for some ARM platforms that decide to flip-flop back to pure GL.15:52
ogra_yup15:52
infinity(And we really need to sort out the QT GL/EGL thing sometime too, for similar reasons)15:52
rsalvetiyup15:52
infinityHaving that all build-time selected, and having to patch everything that links to QT is such a joke.15:52
rsalvetiwell, someone at Qt decided it was a good idea to let applications to render GL directly15:53
rsalvetiwhile also using a GL-enabled Qt :-)15:53
infinityWell, you can't really stop people from using libGL directly.15:53
rsalvetiwhich let people to do whatever they wanted15:54
infinityIt's a shame that QT doesn't appear to provide a rich enough API that people feel they need to do so, though.15:54
ogra_sure you can.  make it a symlink tolibGLES15:54
rsalvetidon't know how it's not working with qt5, but I'd expect to be similar in some way15:54
=== zyga is now known as zyga-afk
=== TRON is now known as TypoNAM

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!