<sjoerd>
luc4: It's very likely they have patched the rk kerenl
<luc4>
sjoerd: ok, so no luck. Thanks anyway for your help!
<lautriv_>
luc4, that's not what he said
<sjoerd>
luc4: You should ask them for their kernel sources really
<luc4>
sjoerd: in years they never provided anything, not even a printf.
<sjoerd>
pff
<lautriv_>
luc4, what is the plan ?
<luc4>
lautriv_: what do you mean by "plan"?
<lautriv_>
luc4, want to upgrade androshit or put a real OS on ?
<luc4>
I need to do a couple of fixes. But I know there is no way if they do not provide the proper sources.
<lautriv_>
luc4, thingie rooted ?
<luc4>
Just noticed there was a rk kernel and I had this bad idea of giving a try.
<luc4>
lautriv_: there are rooted images.
<lautriv_>
so get root, chroot linux, toy with values.
<luc4>
lautriv_: or I can probably root it by unpacking it.
<luc4>
without the sourceS?
<sjoerd>
luc4: Typically board vendors don't change a whole lot, but it really depends on how similar their board design/component selection is to one of the reference boards
<sjoerd>
It's not impossible, but without the sources to check or the schematics you have at least one hand tied against your back :)
<luc4>
sjoerd: probably economically conveniente to switch to something better.
gb_master has joined #linux-rockchip
<sjoerd>
Nod
<luc4>
sjoerd: what about just building specific modules for it instead? Probably it is possible to build from the original rk kernel right?
<lautriv_>
what will E:Invaid tag(0x4D524150)! tell me ?
premoboss has joined #linux-rockchip
<lautriv_>
nvm, meant what i assumed.
<lautriv_>
luc4, what modules ?
<luc4>
lautriv_: at the moment I need the hid-multitouch driver.
<lautriv_>
luc4, _should_ work if you use the same version and toolchain.
<luc4>
lautriv_: yes, I've done it in the past with x7 mini and x8. Only problem here is version on device is 3.0.36+, kernel sources are 3.0.36. Are these compatible?
<luc4>
naobsd: what is this?
<naobsd>
I guess it supports mini too...
<naobsd>
luc4: android SDK (includes kernel) for Minix X5
<luc4>
naobsd: oh thanks... I didn't find it...
<naobsd>
which Android ver. are you using on X5 mini? I think this SDK is 4.2.2
<lautriv_>
bah why does all this crap assume to be cross-compiled o.O
<luc4>
naobsd: I'm using 4.4
<luc4>
lautriv_: cause it is build on a different arch?
<lautriv_>
luc4, said who ?
<naobsd>
luc4: that's 4.2 SDK. you can extract diffs from Rockchip original 4.2, then you can apply it to 4.4 SDK
<luc4>
naobsd: but 4.2 may even be ok
<luc4>
naobsd: thanks
<luc4>
lautriv_: do you build on arm?
<lautriv_>
luc4, yes.
<luc4>
lautriv_: what kind of arm is it? How does it compare to i7?
<lautriv_>
luc4, why must it compare to i7?
<naobsd>
luc4: hm, it seems that supports X5 (!mini). I'm not sure how they are compatible, sorry
<luc4>
lautriv_: cause typically people don't want to spend their life building? Building android requires hours and tens of GB on i7.
<naobsd>
I guess it may be shorter than "hour" on i7 ;)
<naobsd>
I want such a fast build machine!
<luc4>
naobsd: you sure? I remember at least a couple of hours on mine.
<luc4>
naobsd: maybe also depends on whether you have a ssd.
<naobsd>
4core 8thread with 16GB RAM if possible
<lautriv_>
luc4, if i want to build fast, i throw it on my cluster. but i need only a kernel and want that built native.
<lautriv_>
naobsd, appears the major difference is 16G vs 8G flash.
apritzel has joined #linux-rockchip
<lautriv_>
what header is this the RC4 section is talking about ?
<luc4>
Anyone who knows what this from insmod means? insmod: init_module 'hid-multitouch.ko' failed (Device or resource busy)
<lautriv_>
luc4, you want to access it while in use this is one of a.) already loaded b.) fail to claim node c.) another module in use
<lautriv_>
luc4, maybe evdev grabbed it already ?
<luc4>
lautriv_: no idea...
<lautriv_>
lsmod ?
<luc4>
lautriv_: it is not loaded
<lautriv_>
but something else ?
<luc4>
lautriv_: tried to reboot without the device plugged in but the same happens.
<luc4>
lautriv_: none of the /dev/input/event* write anything
<lautriv_>
luc4, that's odd. since andro doesn't use udev, you may have something in initramfs if it was supposed to be used.
<naobsd>
generally RK stock kernel has several hid drivers
<naobsd>
and RK 3.0 kernel is not new, if it's recent win7/8 multitouch protocol, it shouldn't be supported
<lautriv_>
they have probably a module to make your box hover around but no proper documentation.
<luc4>
naobsd: I was able to make it work on minix x8
<luc4>
naobsd: simply insmod hid-multitouch, setting idc and good to go
<luc4>
naobsd: here it is not working
<luc4>
naobsd: even if the module seems to be there
hipboi has quit []
<lautriv_>
(me hands luc4 a solder-iron.
<lautriv_>
anyone interrested in a 3188 tv-box populating 8G flash,2G RAM, rk1000, spdif,hdmi, 2x usb host, 1x usb OTG, Analog A/V, rtl 8123 WiFi, rtl8201 ethernet ? Condition : brand new with UART attached.
<lautriv_>
and µSD slot.
<karlp>
luc4: I've got an x5 mini, haven't got very far with it yet, I never managed to get minix to give out a kernel for it.
<karlp>
and no, the x5 sources are _not_ suitable.
<luc4>
karlp: I probably don't need it, it already has the driver, although it does not work it seems
<karlp>
what are you working on? getting mainline up or just tyring to get a 3.0.+ android kernel up?
<luc4>
for the moment I'd just need to connect a touch monitor
<luc4>
on x8 it works properly, not sure why it does not here
<karlp>
right, but are you trying this on the stock 3.0.36+ kernel, or are you working on linux mainline or what?
<luc4>
karlp: stock 3.0.36+ kernel
<karlp>
yar, whatever then, uninteresting :)
<karlp>
if you figure out the usb power supply gpio for me that would be great though :)
<karlp>
i think that's where I was stuck last time, but I think it was 3.16/3.17 last time I was trying this.
<karlp>
need to finish some other projects first.
<lautriv_>
karlp, are you booting from SD ?
<luc4>
lautriv_: is it possible that the raw device is not in /dev/input?
<lautriv_>
luc4, yep
<lautriv_>
that would be rather some hidrawX
<naobsd>
luc4: X8 shouldn't be RK, right?
<luc4>
naobsd: amlogic
<naobsd>
then "it works with X8" is not so helpful
<lautriv_>
there you go.
<luc4>
lautriv_: no hidraw at all
<lautriv_>
luc4, andro does only make nodes in scripts, i assumed the lack of it.
<luc4>
lautriv_: may I create that manually?
<karlp>
lautriv_: no, RFS on sd, kernel flashed with rktools
<lautriv_>
luc4, you have no root and it will vanish on each boot.
<luc4>
lautriv_: yes, I do have root
<luc4>
lautriv_: I may unpack the image, modify init.rc and repack
<lautriv_>
luc4, if you unpack, you may search for the init to touchpanels.
<luc4>
lautriv_: what is it?
<lautriv_>
luc4, the whole upcoming is trial and error, if you see some lines mentioning any touchpanel you should see where it fails.
<lautriv_>
karlp, so you never came across that strange RC4 part ?
<luc4>
lautriv_: but can't I create the nodes from the shell?
<lautriv_>
luc4, the point is, if there is no plan to support from startup, existing nodes doesn't matter.
<lautriv_>
luc4, regular /dev/hidraw0 starts with c 250 0
<karlp>
that came after I was doing this, and I never found the time to figure out if it worked on rk3066 anyway,
<karlp>
and while booting from sd is nice, it wass't what was stopping me.
<karlp>
I was fine with flashing the kernel and RFS on sd, I just want more of it to work.
<karlp>
boot from sd is a nicety for later
<lautriv_>
appears there is no other solution for 3188 but that part grabs values out of thin air.
<karlp>
magic values are magic, that's why they have that name...
<karlp>
also, like I said, I was working on rk3066.
<lautriv_>
all the same BS, close to trash it and use another arm.
<karlp>
pretty sure you know where the door is.
<karlp>
why so grumpy about magic values, they exist on every platform I've ever looked at.
<lautriv_>
even a wondermedia which is entirely under NDA is able to boot a kernel without truncating the whole media using special tools.
<karlp>
lautriv_: so, the only reason you were asking me about booting from sd is so you could complain?
<lautriv_>
no, i ask because incomplete explanation, that <header> is taken from nowhere.
premoboss has quit [Remote host closed the connection]
gb_master has quit [Remote host closed the connection]
<naobsd>
luc4: there is no script on android to populate nodes under /dev
<naobsd>
luc4: ueventd does it
<naobsd>
magic values _were_ magic til RK u-boot source was published
<lautriv_>
hey they improved. you talk about that uboot where the link points to androtab which mentions something similar at position 6, which in turn leads to a site within "content not created yet" ?
<naobsd>
what's "content not created yet"?
<luc4>
naobsd: not sure I understand anyway. If I have the driver in the kernel, dmesg seems to report that the kernel sensed the device and is using hid-multitouch for it... what else is needed to have a working dev and bring events to Android UI?
<lautriv_>
works at least better than unreliable docu on getting SD-Boot and a proper kernel.
<karlp>
lautriv_: any idea on the kernel source in that rom?
<lautriv_>
karlp, the modded one ?
<karlp>
yeah, looks like it's just unpacked and repacked with a new RFS.
<lautriv_>
no idea.
* lautriv_
went to the door with the conclusion anything containing a rockchip is not worth the efford.
lautriv_ has left #linux-rockchip ["Leaving"]
luc4 has quit [Ping timeout: 255 seconds]
cosm has joined #linux-rockchip
gb_master has quit [Remote host closed the connection]
GriefNorth has quit [Ping timeout: 260 seconds]
maz has joined #linux-rockchip
maz has quit [Ping timeout: 272 seconds]
luc4 has joined #linux-rockchip
xcasex has quit [Ping timeout: 240 seconds]
cnxsoft has quit [Quit: cnxsoft]
rory096 has joined #linux-rockchip
xcasex has joined #linux-rockchip
gb_master has joined #linux-rockchip
maz has joined #linux-rockchip
sanjay85 has joined #linux-rockchip
<sanjay85>
hello
<sanjay85>
naobsd ? i have some news for you
<sanjay85>
me102a is booting !!
<sanjay85>
i have boot me102a with sdcard (modify boot.img)
<sanjay85>
but now there is no sound, and no touch ? i'm on the first screen of asus, i must select langage, but no digitalizer ? wtf ? maybe a other file to edit ?
<sanjay85>
an idea ?
sanjay85 has quit [Quit: Page closed]
gb_master has quit [Remote host closed the connection]
luc4 has quit [Quit: Konversation terminated!]
<rperier>
hi all
ssvb has quit [Ping timeout: 240 seconds]
overcr has joined #linux-rockchip
<overcr>
hi
JohnDoe_71Rus has joined #linux-rockchip
maz has quit [Ping timeout: 240 seconds]
maz has joined #linux-rockchip
<overcr>
so
<overcr>
i realize this is not a helpdesk
<overcr>
but google failed me for the first time
<overcr>
i have a rk3066 tablet which i deliberately bricked with "eraseflash" in RKandroid tool for windows, now nothing wants to load a bootloader for me
<overcr>
anything i try results in a message saying "boot download failed"
<overcr>
and linux tools seem to do nothing either
<overcr>
i have parm file and stuff, but i'm retarded enough to have forgotten to backup the original bootloader, too
<overcr>
so i kindly ask, do you have any idea how to make that tablet operational again? from what i already researched on that topic, there's that MROM thing that kicks in when there's no bootloader or NAND's corrupted
maz has quit [Ping timeout: 246 seconds]
jas-hacks has joined #linux-rockchip
<overcr>
but because that maskrom isn't much verbose i have no idea what's going on with the bootloader update process
ssvb has joined #linux-rockchip
McBitter has joined #linux-rockchip
maz has joined #linux-rockchip
McBitter has left #linux-rockchip [#linux-rockchip]
<overcr>
all right, i fixed it, thanks guys :3
overcr has quit [Quit: Page closed]
<karlp>
what did you do in the end?
akaizen has joined #linux-rockchip
maz has quit [Ping timeout: 250 seconds]
maz has joined #linux-rockchip
apritzel has quit [Ping timeout: 264 seconds]
maz has quit [Ping timeout: 260 seconds]
cosm has quit [Ping timeout: 240 seconds]
maz has joined #linux-rockchip
maz has quit [Quit: Leaving]
maz has joined #linux-rockchip
jas-hacks has left #linux-rockchip [#linux-rockchip]