Wikiwide has joined #maemo-leste
Pali has quit [Ping timeout: 268 seconds]
Blikje has quit [Ping timeout: 268 seconds]
Blikje has joined #maemo-leste
pere has quit [Ping timeout: 260 seconds]
Blikje has quit [Ping timeout: 268 seconds]
RedW has quit [Ping timeout: 260 seconds]
RedW has joined #maemo-leste
Blikje has joined #maemo-leste
<tmlind> yeah great :) nice that terminal supports the vol keys now for font size, i did not know that
joerg has quit [Ping timeout: 260 seconds]
joerg has joined #maemo-leste
pere has joined #maemo-leste
<mighty17[m]> hey, is there anything special needed to make usb-otg work on omap4? also usb only works when connected before booting the device, ie if once device booted and then i connect it to my pc, pc doesnt detect it :( here's my dts https://paste.debian.net/1218005/
<freemangordon> oh, VRFB was never ported to omapdrm :(
<freemangordon> luckily the code is still there for omapfb
<tmlind> mighty17[m]: you need to configure the usb phy driver for it, probably the legacy drivers/usb/phy driver still for that pmic
<tmlind> mighty17[m]: compare to the pandaboard dts files assuming you have the same twl pmic and usb phy, i guess it's possible you have some separate usb phy for the otg interface
Pali has joined #maemo-leste
_inky has quit [Ping timeout: 268 seconds]
<Wizzup> freemangordon: what is VRFB ?
zhxt has quit [Ping timeout: 260 seconds]
_inky has joined #maemo-leste
zhxt has joined #maemo-leste
<freemangordon> virtual rotated frame-buffer
<freemangordon> this is what is used to rotate display on omap3
<freemangordon> and maybe omap4, I am not sure it has dmm
<freemangordon> tmlind may know
uvos has joined #maemo-leste
<tmlind> omap4 has dmm with tiler for sure
<tmlind> omap3 has vrfb instead afaik
<tmlind> i think both provide separate addresses for various rotations, looks like vrfb configuration is missing from drivers/gpu/drm/omapdrm?
<tmlind> less than 400loc for drivers/video/fbdev/omap2/omapfb/vrfb.c it seems
<freemangordon> yeah
<tmlind> ok
<freemangordon> not really 'ok', but yeah. I would port that, but I'll need some hints where to start
<tmlind> no idea on that one, seems like it just needs to be configured, then saved and restored for idle states
<uvos> so if tiler rotation is supported by omapdss in practice atm
<uvos> what prevents it from working in modesetting
<uvos> do we know?
<freemangordon> no
<freemangordon> uvos: also, we need vrfb rotation form omap3 (n900, n9/50)
<tmlind> maybe nothing reconfigures the changed tiler/vrfb addresses right now on rotation change?
<tmlind> maybe there was some ioctl in the old ddk-1.9 setup doing that
<freemangordon> yes, there is
<uvos> freemangordon: sure but knowing why tiler is not working helps in understanding how to implement vrfb
<tmlind> although it sounds like the rotation change should be a standard ioctl..
<uvos> freemangordon: since in theroy ms should use it
<freemangordon> not really
<freemangordon> at least IIUC
<tmlind> my guess is it all should be simpler than earlier anyways
<freemangordon> when you create BO you need to omap_bo_new_tiled()
<freemangordon> but, in GBM case I don;t see how this can be done
<uvos> no
<freemangordon> uvos: yes, in order to use TILER roatation, a special BO is needed
<uvos> sure but really the kernel should do this more or less transperantly if you setup kms/drm correctly
<freemangordon> yes, I agree
<uvos> at least thats how the interfaces are supposed to work
<freemangordon> but maybe this is not implemented
* tmlind bbl
<uvos> sure
<freemangordon> lemme check if omapdrm dma_buf implementation supports that, somehow
_inky has quit [Ping timeout: 260 seconds]
<freemangordon> uvos: I don;t see a way of requesting dma_buf with TILER flags
<freemangordon> amd because modesetting uses gbm (dma_buf that is), bo's never have OMAP_BO_TILED_XXX set on them
<freemangordon> so, rotation does not work
Pali has quit [Ping timeout: 268 seconds]
_inky has joined #maemo-leste
<uvos> freemangordon: right but really omapdrm should allow the primary display plane to be rotatied
<uvos> by just calling the rotation transform on it in the kms interface
<uvos> and then the kernel should just do whatever to rotate the plane, ie move it to tiler space and configure it
<uvos> this appears not implemented atm
<uvos> but this is the right/generic way of doing it.
<Wizzup> MartijnBraam[m]: btw I answered the tweakers guy late last night, thanks for the refer, hope I was able to help
<Wizzup> uvos: freemangordon: seems like it would be quite helpful to have the omapdrm folks here
<Wizzup> or for us to move some discussion to a medium where they read along
<parazyd> uvos: This is what's left in -devel, http://sprunge.us/urFWSH
<parazyd> uvos: Anything from here I should promote?
<Wizzup> what about ke-recv ?
<parazyd> It's in the list. I dunno, so that's why I'm asking.
<uvos> you promoted leste-config you have to promote hildon-desktop or rotation breaks
<Wizzup> I think I just changed some logging in ke-recv
<uvos> also please make sure that hildon meta in stable no longer wants hildon-rotation-support
<uvos> as this also needs to go
<uvos> simple-brightness-applet is fine for promotion
<uvos> so is hildon-home
<uvos> hildon-theme-alpha
<uvos> hildon-theme-beta
<uvos> hildon-theme-devel
<uvos> these being in devel at all seams wierd
<uvos> ofono can be promoted
<uvos> thats just the motmdm bugfix
<uvos> that looks like its it
<parazyd> Thanks
<uvos> add profilesx to hildon-meta while at it
<uvos> if Wizzup dident allready
<Wizzup> that wasn't done yet
<Wizzup> but I agree it should be
<parazyd> uvos: We have a Conflicts and Provides for hildon-desktop-rotation-support
<parazyd> uvos: That should be fine
<uvos> ok
<uvos> anny one have had any trouble with new osso-applet-display?
<uvos> if no thats fine to i gues
<uvos> to promote
<Wizzup> it works for me
xmn has quit [Ping timeout: 260 seconds]
<freemangordon> Wizzup: right, but I doubt tomi will join here :)
<freemangordon> back then there was linux-omap, but I doubt it is anymore
<freemangordon> uvos: agree
<parazyd> uvos: What about droid4-battery-calibration?
<uvos> parazyd: what about it
<parazyd> Should I also move it to stable?
<uvos> i dont recall any changes
<parazyd> ah nvm, it's my changes to install it in sysinit runlevel instead of default
<uvos> and you renamed it from maserati to droid4
<uvos> not that i mind
<uvos> but mapphone would have been more correct
<uvos> but no big deal
<parazyd> Wizzup: What about qt5 stuff? Leave that alone or move?
<uvos> this is me removing the color workaround
<uvos> its broken either way
<uvos> if you keep it osso_caluclator is broken, if you move it qcalendar is broken
<uvos> (amoung other things)
<Wizzup> freemangordon: maybe he would?
<Wizzup> parazyd: not sure @ qt
Wikiwide has quit [Ping timeout: 260 seconds]
<parazyd> ok, then all is done now
<parazyd> Let's see if next week's images are ok
<parazyd> About hildon-theme-*, I didn't promote them yet, as I think there's some packaging bug, but I haven't confirmed it.
<parazyd> So that's gonna wait a bit
_inky has quit [Ping timeout: 268 seconds]
_inky has joined #maemo-leste
dsc_ has joined #maemo-leste
<Wizzup> dsc_: \o
<mighty17[m]> but what about usb only working when connected before boot?
zhxt has quit [Ping timeout: 260 seconds]
<dsc_> hi
<dsc_> does maemo-leste run on my iphone 13 pro max?
System_Error has joined #maemo-leste
<Wizzup> dsc_: ;-)
<Wizzup> It runs on a few devices, but not iphones
<dreamer> maybe you can ask steve jobs' ghost
<dsc_> :P
zhxt has joined #maemo-leste
<uvos> mighty17[m]: well you dident explain what "usb working" or "usb not working" means and its very ambigous
<uvos> mighty17[m]: but if it "works" when coccentcted before boot its because your bootloader is initalizing usb for itself and the hw state carrys through
<mighty17[m]> uvos: yeah thats a possible reason
<uvos> the bootloader dose so to allow android fastboot or rather whatever the proprietary samsung equivalent is to work
<mighty17[m]> the thing is my pc doesnt show anything in dmesg, but on device i get `twl6030_irq: Unmapped PIH ISR 20 detected` when i do not let bootloader initialize it
<uvos> so some plug/usb interrupt fires and your not handling it
<mighty17[m]> any example of it?
<uvos> as tmlind said look at how it works on some other device with twl6030 pmic
<uvos> (what you have to do is device dependant)
<mighty17[m]> mine is twl6032, they're different
<mighty17[m]> afaik my device has some usb_sel1 thingy
<uvos> well your going to have to figure out what the differences are and ammend the usb phy driver
<mighty17[m]> oh, now thats weird, it worked now
<mighty17[m]> ie without bootloader initialisation
Pali has joined #maemo-leste
_inky has quit [Ping timeout: 260 seconds]
_inky has joined #maemo-leste
joerg has quit [Read error: Connection reset by peer]
joerg has joined #maemo-leste
_inky has quit [Ping timeout: 268 seconds]
R0b0t1`` has quit [Ping timeout: 260 seconds]
_inky has joined #maemo-leste
R0b0t1`` has joined #maemo-leste
mardy has quit [Quit: WeeChat 2.8]
xmn has joined #maemo-leste
akossh has quit [Quit: Leaving.]
elastic_dog has quit [Ping timeout: 268 seconds]
elastic_dog has joined #maemo-leste