<libv>
(said the author of that very page, and most of the devices linked from it)
<arokux>
libv: do you know what is needed to have (sorry for noob terms) text output when connecting though, say, VGA (i suppose it is the simplest video output) in mainline?
Black_Horseman has joined #linux-sunxi
Black_Horseman has joined #linux-sunxi
<libv>
arokux: yup, as i only really have lcds to do on my 3.4 kms driver
<Black_Horseman>
back
<arokux>
libv: how is lcds has something to do with VGA?
<arokux>
(without is*)
kivutar has quit [Quit: Ex-Chat]
<arokux>
libv: and I was asking about mainline
afaerber has quit [Quit: Verlassend]
<arokux>
libv: how is this thing called at all that is needed to be done? framebuffer?
<libv>
arokux: yes, framebuffer would get a console
<arokux>
libv: I see, what dependencies does it have?
<libv>
an fbdev driver is pretty trivial and doesn't depend on much in the rest of the kernel
<arokux>
libv: "on much..." :)
<Turl>
hey wens :)
shineworld has left #linux-sunxi ["Leaving"]
<Turl>
libv: you could add display support for uboot :P
<Turl>
and I think we can get fancy menues then
<arokux>
wingrime tried to do it, but failed
<Turl>
and w/ simplefb we should be able to use it as well from linux
<arokux>
DISP Driver Support(sunxi) -- is the thing that needs to be mainlined?
<Turl>
arokux: it needs to be rewritten
<arokux>
well, mainlining assumes lots of things... long debugging nights, rewriting, testing.... :D
<Turl>
arokux: I'm pretty sure it'd need to be rewritten from scratch pretty much
<Turl>
but don't take my word for it
<arokux>
Turl: ok, i'm not disputing anything. my question is what are the dependencies of it?
<libv>
but there's tons of stuff in there that is not in the user guides or datasheets
<libv>
so it is a very solid piece of documentation
<Turl>
a bunch of clocks I suppose, the rest should be there
<Turl>
libv: it doesn't require DMA, does it?
<arokux>
Mali and framebuffer, are those connected?
<Turl>
arokux: not really
<libv>
arokux: yes and no
<arokux>
because I see something like DISP Driver Support(sunxi)
<arokux>
oh
<libv>
Turl: that isn't entirely clear yet
<arokux>
select FB_SUNXI_RESERVED_MEM if MALI
<arokux>
so MALI can be still OFF
<libv>
Turl: there might be an even bigger shortcut by using dma, but we have very little sample code
<Turl>
arokux: that's just for the allocation stuff
<Turl>
libv: I don't recall seeing any disp stuff on the dma channels when working on that
<libv>
Turl: but it is mentioned in some datasheets
<arokux>
but then except of FB, the driver for VGA is also needed, right?
<libv>
and there is even a tiny bit of code hinting at how it could work
<libv>
arokux: ...
<Turl>
libv: HDMI DDC is the closest I've seen
<arokux>
libv: ?
<Turl>
libv: that's "disp"
<Turl>
err arokux ^
<Turl>
libv: and HDMI audio
Black_Horseman has quit [Ping timeout: 244 seconds]
afaerber has joined #linux-sunxi
<Turl>
libv: hmm on a second look I see TCON0/1, does that ring a bell?
<arokux>
so basically this directory should be rewritten / mainlined? drivers/video/sunxi/disp/
Black_Horseman has joined #linux-sunxi
Black_Horseman has quit [Changing host]
Black_Horseman has joined #linux-sunxi
<ssvb>
Turl: adding a simple display driver to u-boot would be indeed very cool
<ssvb>
Turl: but it also would need USB support for the keyboard, right?
<Turl>
ssvb: we already have USB support, don't we?
<Turl>
I think we can already boot from usb storage
<ssvb>
Turl: how can I find it in the u-boot sources?
tomboy64 has quit [Remote host closed the connection]
<wens>
Turl: sorry, didn't get around to review the rest of your patches
tomboy64 has joined #linux-sunxi
<ssvb>
Turl: I mean, a lot of other board have defines for USB/OHCI/EHCI config options in u-boot 'include/configs' directory, but I don't see anything like this for sunxi
<Turl>
ssvb: maybe they didn't get merged yet?
<Turl>
arokux: ^
<Turl>
wens: np :)
<Turl>
wens: btw, is that an ack on the uart patch?
<wens>
Turl: it is, but I'm not sure my ack is worth anything :p
<Turl>
:p
jebba has quit [Quit: Leaving.]
issueat has quit [Remote host closed the connection]
issueat has joined #linux-sunxi
issueat has quit [Remote host closed the connection]
<ssvb>
arokux: and if we don't have usb for the keyboard, then we have little use for the display driver there :)
<ssvb>
arokux: you seem to be interested in the display driver, right?
<ssvb>
arokux: in any case, forget about the u-boot-sunxi repository, it only exists to support the current users until the mainline u-boot is fully ready to replace it
<arokux>
ssvb: ah! you are using my patches! that is cool. I thought I'm the only user.
<arokux>
ssvb: was u-boot-sunxi upstreamed?
libcg has quit [Remote host closed the connection]
<ssvb>
arokux: I'm not using your patches yet, but thanks to Turl I have just found them
<arokux>
ssvb: I think I'm missing something there... is everything in u-boot-sunxi upstreamed?
<arokux>
ssvb: just ask if you have some problems with these patches.
smotocel69 has quit [Read error: Connection reset by peer]
<arokux>
Turl: "Reboot failed -- System halted": not anymore with the patch mripard has given me
<ssvb>
arokux: the initial sun7i support with the cubietruck config has been mainlined (v2014.07), and a lot more will be mainlined in the next u-boot release (v2014.10)
<arokux>
hm.. so in theory I won't be able to connect a CRT display to the cubieboard...?
<Rose28357>
arkolux: why not ? CRT is using VGA which is supported by Cubietruck. But you can not use CRT and LVDS-connected LCD at the same time.
<afaerber>
arokux, dunno about sunxi, but many embedded boards allow to connect LCD panels directly via LVDS or similar connections rather than via VGA/HDMI/DisplayPort
<arokux>
afaerber: same for sunxi.
HeHoPMaJIeH has joined #linux-sunxi
HeHoPMaJIeH has quit [Changing host]
HeHoPMaJIeH has joined #linux-sunxi
<afaerber>
formerly they then had some external I2C controller logic, these days that's moved into the SoCs
<arokux>
afaerber: as I understand it there is LCD controller it then outputs VGA/HDMI/... I just find it strange there is LCD in the controller name. it is kind of assuming all the displays are LCD?
<libv>
wens: now one of those two guys joined broadcom to do their open gpu driver
<Rose28357>
arokux : thats right. i made the assumption that vga and LCD shared pins. i was wrong.
<arokux>
libv: display engine is hairy!
<libv>
arokux: yes.
<libv>
arokux: i have it mostly figured out, just need to deal with lcd power on/off, pwm and irqs
<afaerber>
libv, broadcom open gpu driver> did that go anywhere beyond that "spectacular" code drop at the rpi anniversary?
<libv>
afaerber: broadcom hired eric anholt last week
<libv>
don't know why they chose him, as there are tons of people who have equal or better experience with mesa
<libv>
but eric and keithp fucked up modesetting (badly based on my insights upon it) for all of us for years
<libv>
let's hope that he doesn't fuck up the broadcom gpu either
<libv>
i complained my head off in december when i was implementing gem
<afaerber>
libv, don't know him. I rather meant, are they actively contributing to any upstream graphics project? or just continuing their own code drop?
<libv>
and then erics idea of turning mesa into one huge blob with every driver linked in at build time... that's just stupid, and it has the toolchain guys here wondering what things the graphics guys smoke
<arokux>
libv: I was thinking such engine should be actually in the GPU...
<libv>
which reminds me, i am supposed to go meet those and others in artefakt right now
<libv>
arokux: no.
<libv>
afaerber: check phoronix.com, it's all on there
<arokux>
libv: but do the desktop architectures also have something like display engine?
<libv>
arokux: yes, very much so.
<afaerber>
libv, is there some conference or are they all in the NUE area anyway?
<arokux>
libv: and where is the memory for such engine?
<libv>
but the stupid idiots have managed to toss the whole lot in the same pot
<libv>
afaerber: no, just normal tuesday beers, but this time in a football free zone
<libv>
arokux: depends
<afaerber>
libv, enjoy :)
<libv>
arokux: google for IGP
HeHoPMaJIeH has quit [Ping timeout: 240 seconds]
<arokux>
libv: well, ok, but this is rather recent that GP is integrated. so basically at desktops such display engines are parts of the graphic cards
<libv>
afaerber: well, if you're bored, head on over
<libv>
arokux: part of the same chip, yes
<libv>
arokux: but that doesn't mean that it isn't a mostly separate block
Andy-D has quit [Ping timeout: 255 seconds]
<libv>
arokux: see, i went through this sort of discussion more than a decade ago
<arokux>
ok :p
<libv>
when the word modesetting hadn't been invented yet
<libv>
and when people believed that this sort of black magic belonged in the bios
<libv>
the hardware is modularly designed and logical
<libv>
so the software should at least mimic that
<libv>
but that was not accepted
Netlynx has joined #linux-sunxi
Netlynx has quit [Changing host]
Netlynx has joined #linux-sunxi
<libv>
until keithp got tasked with fixing up the intel graphics driver
<oliv3r>
i've noticed that a10 devices nearly always boot when power is applied
<oliv3r>
do we know more specific rules?
<oliv3r>
our device won't have buttons exposed
<mnemoc>
if it was properly shutdown before removing power it won't come back automatically when it's powered. only with a button
<mnemoc>
but i doubt the AXP can remember the previous state for long
issueat has quit [Remote host closed the connection]
<mnemoc>
good night
<froese>
there's the power_start flag in the fex.
<froese>
is the nand-driver from sunxi-3.4 supposed to work on the cubietruck?
<arokux2>
oliv3r: our device? :P
<oliv3r>
well lime + our stuff
<froese>
there are a couple of options in the axp209 for that - i've not completely understood all the magic but it seems, u-boot plays a role, too. (shutdown in the kernel stores some magic values in the "cmos-regs" of the axp)
akaizen has quit [Remote host closed the connection]
<arokux2>
what driver(?) is responsible for proper treating of the power btn?
<froese>
i don't want to make partitions - they should be there already (last time i checked, it booted android just fine). but under linux is see nothing of that.
<froese>
arokux2: look under drivers/power/axp_power
<Turl>
froese: don't you see /dev/nand[abcde...] ?
<froese>
Turl: right. gives some warnings on boot the it can't find the partitions...
<arokux2>
froese: so the power button is always the same at different boards?
<Turl>
froese: paste dmesg
<froese>
arokux2: the power button is handled by the power management controller (axp209/axp202)