<akaizen_>
naobsd: yes - i think right between the microSD and switch - labed G T R
akaizen_ is now known as akaizen
<akaizen>
There have been updated SDKs tho
<naobsd>
akaizen: oh, where?
<akaizen>
naobsd: I have not found them - currently using firefly
<naobsd>
I want to correct SDK and share on my git server
<naobsd>
ah, I see.
<akaizen>
so are the wiki and google group what is being updated now?
<akaizen>
i'll add the dts and info on this board
<naobsd>
I already become owner of linux-rockchip things
<naobsd>
but for wiki
<naobsd>
wiki admin account is not so powerful
<naobsd>
so I'm preparing my own server
<naobsd>
probably, what we need for new device is
<naobsd>
dmesg and dtb from latest stock firmware, dmesg from plain SDK kernel (if it works)
<akaizen>
what does dmesg provide? partitions and boot parameters?
<naobsd>
I could get extra/require info from dmesg, it was not in dts
<naobsd>
better than nothing
<akaizen>
True. My first step when getting a new board is parititons dump. dmesg, ls -lR /, mount,
<akaizen>
only thing missing is bootloader
<akaizen>
oh and /proc/kmsg
<naobsd>
it uses eMMC? NAND?
<naobsd>
if it's eMMC, "dd if=/dev/mmcblk0 of=/somewhere/to/dump bs=4M count=1" will do the job for bootloader
<akaizen>
yes all partitions are one mmcblk0
<akaizen>
on*
<naobsd>
probably it's prebuilt u-boot, which is included in Firefly SDK
<naobsd>
you can confirm it with u-boot build date & commit id from serial console
<akaizen>
hmm /dev/block/mmcblk0 only dumps 4 bytes
<naobsd>
ah, 4M may not work
<naobsd>
well
<naobsd>
dd if=xxx of=xxx count=8192
<naobsd>
8192 sectors = 4MiB
<naobsd>
but
<naobsd>
for me/my RK3288 box, only parameter/kernel/boot/recovery/resource/system are unique
<naobsd>
(parameter was not so unique)
<naobsd>
I can use loader.bin in SDK
<akaizen>
Really want GPU + VPU in linux & bsd...
<akaizen>
H265 in Android would be nice for now tho
<naobsd>
I have a lot of android device with cheap chinese socs,
<naobsd>
but I didn't use with android so much...
<naobsd>
I've made cm/cwm for (some of) them, but I didn't use my cm/cwm so much too... only for basic test ;)
<naobsd>
oh geekbuying post new firm for my device
hipboi has quit [Ping timeout: 272 seconds]
AstralixNB has joined #linux-rockchip
hipboi has joined #linux-rockchip
hipboi has quit [Quit: Leaving]
hipboi has joined #linux-rockchip
hipboi has quit [Remote host closed the connection]
RayFlower has joined #linux-rockchip
hipboi has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
hipboi has quit [Ping timeout: 260 seconds]
hipboi has joined #linux-rockchip
FightingCat has joined #linux-rockchip
<karlp>
dianders: I didn't knwo about pwclient, nor what patchwork it ends up in, so thanks for that.
<karlp>
dianders: I did however think that if it had gotten into mailing lists, that it must be in _someone_'s tree alread :)
hipboi has quit [Ping timeout: 245 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 245 seconds]
hipboi has joined #linux-rockchip
<mmind00>
karlp: my devel/workbench tree does have working cpufreq, concerning mailinglists it's the other way around: mailingling -> someone's tree :-)
<karlp>
well, presumably, somoene had it in their tree to generate the patches for the mailing list is what I meant,
<karlp>
but ok, if your devel/workbench has it, I was probably missing some config settings, as I didn't have that directory to modify anything
<karlp>
I'm at the dayjob right now though anyway, so won't be playing anymore til later this evening
bengal has joined #linux-rockchip
FreezingCold has quit [Ping timeout: 260 seconds]
FightingCat has quit [Ping timeout: 260 seconds]
FreezingCold has joined #linux-rockchip
tomeu has quit [Quit: Coyote finally caught me]
tomeu has joined #linux-rockchip
hipboi has quit [Ping timeout: 255 seconds]
nighty^ has joined #linux-rockchip
hipboi has joined #linux-rockchip
GriefNorth has quit [Quit: WeeChat 1.0]
naobsd has quit [Quit: Page closed]
FightingCat has joined #linux-rockchip
GriefNorth has joined #linux-rockchip
cyrozap has quit [Ping timeout: 258 seconds]
ganbold__ has joined #linux-rockchip
naobsd has joined #linux-rockchip
cyrozap has joined #linux-rockchip
Bludot has joined #linux-rockchip
hipboi has quit [*.net *.split]
ganbold_ has quit [*.net *.split]
FightingCat has quit [Remote host closed the connection]
hipboi has joined #linux-rockchip
cyrozap has quit [Ping timeout: 272 seconds]
<naobsd>
I wish DNS thing will be finished in this weekend...
cyrozap has joined #linux-rockchip
naobsd has quit [Quit: Page closed]
FreezingCold has quit [Quit: Out]
FreezingCold has joined #linux-rockchip
AstralixNB has quit [Ping timeout: 250 seconds]
karlp_ has joined #linux-rockchip
Astralix1 has quit [Ping timeout: 250 seconds]
honx has quit [Ping timeout: 252 seconds]
libv has joined #linux-rockchip
libv has quit [Ping timeout: 250 seconds]
ssvb has quit [Ping timeout: 250 seconds]
Astralix has joined #linux-rockchip
karlp has quit [Ping timeout: 250 seconds]
ssvb has joined #linux-rockchip
honx has joined #linux-rockchip
Astralix has quit [Ping timeout: 250 seconds]
libv has quit [Ping timeout: 250 seconds]
libv has joined #linux-rockchip
naobsd has joined #linux-rockchip
<naobsd>
hmm
Astralix has joined #linux-rockchip
<naobsd>
it seems
<naobsd>
there is bootloader version vs hardware compatibility issue
rz2k has joined #linux-rockchip
BorgCuba has joined #linux-rockchip
<BorgCuba>
naobsd, I read your message for the 16k max length
<BorgCuba>
naobsd, I also tried to execute some code but this doesnt work so far
<naobsd>
BorgCuba: hm... I see
<BorgCuba>
I am looking at the loader right now
<BorgCuba>
If nothing helps it would still be possible to patch the loader itself using sdram upload, but this would only work for one loader version
RayFlower has joined #linux-rockchip
<BorgCuba>
or one could inject code in the vector table (which is always located at 0x0)
<naobsd>
live binary patching ;)
<BorgCuba>
yes ;-)
<BorgCuba>
I have to leave again, see you
BorgCuba has quit [Quit: leaving]
FreezingCold has quit [Ping timeout: 246 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
FreezingCold has joined #linux-rockchip
bengal has quit [Quit: Leaving]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
<mmind00>
and the dt-translation table of the iio-thermal driver I picked from a mailinglist uses tupels of <millivolt millikelvin> (millikelvin - 273150 = millicelsius)
<karlp>
hrm,, right, I have that in my dts as well,
<karlp>
voltage0 and voltage1 are almost identical on the 20060000 blob,
<karlp>
should that show up somewhere in /sys/devices/iio-thermal as well?
<mmind00>
/sys/class/thermal/thermal0/temp or something like this
<karlp>
seems like a units file wouldn't have gone astray, but no matter :)
<mmind00>
yep thermal_zone is handling in celsius ... only the iio-thermal driver uses milli-kelvin internally for whatever reason
<karlp>
so, you might be sick of me hearing it, but I don't remember seeing any tips from you (if you don't have any, that's cool to) got any tips on working out gpios for things like interrupts?
<karlp>
I kinda figure I can eventually poke the gpios for power regulators by toggling gpio pins where possible and using a multimeter,
<karlp>
and some of them from reading alleged compatible kernel code, but the gpio interrupt lines seems trickier
<karlp>
I've got some wild ideas, but they mostly seem like a lot of work and involve probing the board, which I'd like to do as little as possible, my serial console is a rather weak connection.
c0d3z3r0 has quit [Remote host closed the connection]
<karlp>
reword: you might be sick of me asking it...
<mmind00>
haha ... not sick, but I also can't offer anything ... after having done this one time on my s3c2416 (samsung) ereader, I don't want to do this again ... so I'm simply concentrating on stuff I have schematics for (the R89 is an exception here)
<karlp>
yeah, that's fine,
<karlp>
I got an email from a minix dude asking me to send a gpl request to a specific email, so I'm still hopign that will help out.
<mmind00>
but in general, Rockchip boards always use similar layouts, so a lot of gpios are always connected to the same thing
<karlp>
yeah, I was goign to look at a bunch of the common stuff, try those all out first,
c0d3z3r0 has joined #linux-rockchip
<karlp>
and if I hadn't found it, it can't be _too_ difficult to poke gpios one by one and crash it a lot until it turns up,
<karlp>
for the ones that are gpio controlled regulators at least.
<karlp>
pwm regs and interrupts are the silly stuff.
<karlp>
and of course, workign out which source is relevant
<karlp>
but hey, usb works as long as I provide vbus externally :)
<mmind00>
:-D
<karlp>
hrm, I should probably try and pull that clockfreq thing and test i2c for max...
<karlp>
oh, you actualyl _work_ for bq!
<karlp>
or did, at least
<karlp>
I was kinda curious how the _only_ rk3066 dts file was for a table I'd never heard of :)
<mmind00>
I do
<mmind00>
and continue to do so :-)
<karlp>
groovy
<karlp>
so, why only the one .dts? ;)
<karlp>
if I may ask, andyou're free to not answer, how much of your mainline work is you personally and how much is tacitly approved/helped/sponsored by work? I notice you use a personal email for kernel stuff, so I guess it's personaly time, but still related....
<mmind00>
main reason for the one dts: no need to flood the tree with similar dts-files while we don't have components that differ
<karlp>
fair enough. that's somethign I'v ebeen curious about, as mainline linux gets more and more capable for these devices, how many damn dts files will there be!
<mmind00>
as for involvement: the whole Rockchip part is mainly my hobby [but I have of course stuff like schematics for "my" devices]
<mmind00>
which then uses a different mail address :-)
<karlp>
it's mostly buttons and then the ehternet/usb that's still WIP
<karlp>
heh, my work uses linux, but mostly just userspace apps, I've got one tiny kernel patch in our tree, and it's disgustingly gross and I'd love to find the time it deserves to make a proper patch
<karlp>
but it seems if I wait long enough it will happen without me anyway :)
<mmind00>
your vcc_phy fixed-regulator is strange ... on the marsboard, this pin leads to a reset-pin of the phy
* karlp
shrugs, I'm still not 100% sure on that,
<karlp>
ethernet doesn't work,
<karlp>
but that's the pin used on sources that the ninterwebz claims "works on my device"
<mmind00>
in any case ... I'm going to bed now ;-)
<mmind00>
1am is late enough
<karlp>
yeah, I'm meant to be ina bar, but the internet and some port and cheese has been more interesting
<karlp>
but tomorrow! joyride to visit the volcano!
<naobsd>
mmind00: I got a report that u-boot on R28(R89) need to be Apr212014_134842 version.
<naobsd>
mmind00: there are ver. 2.15, 2.15.01, and 2.15.02 are also available (prebuilt binaries in Android SDK), but at least 2.15.02 doesn't boot
<naobsd>
mmind00: I couldn't get detail (he doesn't have serial console), something may be incorrect
<naobsd>
mmind00: if you have any info (in future), please share info
RayFlower has joined #linux-rockchip
<naobsd>
I guess you don't change bootloader ;)
<karlp>
hrmm, trying pwclient, it's just hanging.
<karlp>
ah, pwclient list is waiting for somethign to search on.
<karlp>
ok, interesting tool.
RayFlower has quit [Read error: Connection reset by peer]