00:13 <naobsd> jcarlos: file says "data", nothing is wrong

00:14 <naobsd> (of course files says "data" for other files)

00:16 <naobsd> my ramdisk is just an example, and I'll modify it (hopefully)soon

00:18 <naobsd> I'm thinking to use multiboot.txt on SD(or somewhere) as a config which describe device/path to use as rootfs

00:18 <naobsd> and probably I'll change some other things

16:36 <ssvb> ncrmnt: hi

16:36 <ncrmnt> hello

16:38 <ssvb> <ncrmnt> For now all I get with xf86-video-mali is a blinky square where the window should be and the xorg segfaults. And both fbdev and fbturbo are giving me HUGE artifacts while rendering.

16:38 <ssvb> is it still a problem?

16:42 <ncrmnt> For now - yes, I haven't done any more experimenting since last time.

16:43 <ssvb> what kind of fbdev driver is that?

16:44 <ncrmnt> fbdev the simplest available video driver in xorg that works on top of /dev/fb

16:44 <ncrmnt> with no accel whatsoever

16:45 <ncrmnt> fbturbo has some neon optimisations for that.

16:45 <ssvb> ok, for a moment I had doubts that it might be olegk0's fbdev with mali patches

16:45 <ssvb> but having artifacts with the basic fbdev driver is definitely not normal

16:47 <ssvb> this needs to be resolved even before starting to experiment with mali

16:50 <ncrmnt> Well, mali could well solve this. Something tells me it is something with copyarea.

16:50 <ncrmnt> Basically, when I start dragging a window its edges disappear.

16:51 <ncrmnt> Since xf86-video-mali has EXA that accelerates copying this might do the trick. But I'm not sure.

16:52 <ncrmnt> Some olegk0's hacks are a mystery to me... I spent a while to figure out why do all apps segfault when trying to open /dev/fb0 with mali enabled in kernel.

16:53 <ncrmnt> And it turned out that with mali enabled rk_fb uses 'ipp buf' for /dev/fb0 that has memory reservation stuff commented out.

16:55 <ssvb> well, first try to make the most basic driver work properly

16:56 <ssvb> the EXA part just adds more complexity

16:56 <ncrmnt> Btw, does the basic fbdev driver work fine on those droid tv sticks with RK3188?

21:22 <jcarlos> naobsd: I don't understand then (I'm talking about "data" output when executing "file kernel"). If my extracted kernel is not signed and it is not a "Linux kernel ARM boot executable zImage", what the hell is then?

22:18 <karlp> hi, I've got one a "new" ug802 (getting called a ug809) fresh out of the box, but I'm on linux, not windows, and I don't seem to be able to find any way of getting virtualbox and the flash tools to detect the board,

22:18 <karlp> I don't really understand the steps I need to get to http://www.freaktab.com/showthread.php?4126-ANOTHER-CLONE!-UG802_9-or-UG80x-Stock-ROM-now-available&p=56906&viewfull=1#post56906 from a fresh out of the box device

22:19 <karlp> I _believe_ I need to root it first, as guides like the picbuntu install all start from there

22:19 <karlp> but is it really required?

22:21 <karlp> any other tips for getting started?

22:22 <karlp> all the guides I've got largely get me as far as running rk flash tools and then flashing, but only once the device is detected, but it's never detected for me

22:22 <karlp> I suspect the linux host os is snatching the device briefly when it changes modes from mtp to mass storage and back before virtualbox gets it again, and that's why the rk flash tools don't detect it, but is there any other way?

22:32 <karlp> ok, I seem to have gotten a cwm revoery thing installed on it via update.zip,

22:32 <karlp> I guess that's progress

23:27 <ikarus> silly Q, but before I can get started on properly working on this silly HDMI stick, I need to identify what HW design it is based on, any general recommendations on how to tell (it came pre-rooted, so I can get at a lot of info if I want to)

23:31 <karlp> ikarus/flukso?

23:37 <ikarus> flukso ?

23:39 <karlp> never mind, same nick as another dutch guy

23:39 <karlp> was just fun seeing you in yet another place if it had been that person :)

23:39 <ikarus> ah

23:39 <karlp> only advice I could say is open it up and have a look

23:39 <karlp> but I'm pretty new here

23:40 <ikarus> karlp: I pretty much know the chipset, etc

23:40 <ikarus> just not which "named" design it matches

23:40 <karlp> well, I had to open up mine to find that out

23:40 <ikarus> I mean this is probably a rebranded one, branded as Gembird, HDMI Smart TV Dongle

23:40 <karlp> though the versions and dates of the stock android matched some other posts

23:41 <ikarus> But I can just find a few random polish forums mentioning that one :)

23:46 <ikarus> just to watch them squirm

23:46 <karlp> they'll just refer you to the upstream vendor

23:47 <karlp> hrm, picuntu 4.5 doesn't seem to have a recovery.img file?

23:47 <karlp> or am I meant to boot kernel.img there instead?

23:47 <karlp> trying to do a dual boot

23:48 <karlp> I've managed to install cwm into the recovery section, verified it works, replaced it with what i thought was the recovery from finless 1.7 for u80x_9 beta3, which wouldn't boot, but successfully reflashed the cwm image to recovery, and that works

23:48 <karlp> just not sure how to move forward from here to get a regular desktop linux booting while leaving the android in place

23:49 <ikarus> karlp: actually they've rebranded and got their own CE licensing for it

23:49 <ikarus> for all intents and purposes they are the manufacturer

23:52 <ikarus> so either they had to pass on the written offer, or created their own if the chinese company built this on their order