ganbold_ has quit [Remote host closed the connection]
ganbold_ has joined #linux-rockchip
Tony_ has joined #linux-rockchip
<prop81>
grrrr....I can't get past the Firefly splash when I built system.img
<prop81>
anyone else run into this issue?
<Tony_>
I'm here now.
<Tony_>
Firefly splash is mean that there are many error ?
<prop81>
After download system.img, it reboots and hangs at the Firefly splash screen
<naobsd>
"I can't get past the Firefly splash when I built system.img" is too less information
<naobsd>
you should explain more e.g. how did you built system.img, what you changed, serial console output, etc
<naobsd>
Tony_: generally splash == logo on boot
<Tony_>
naobsd, okay.
<prop81>
I did not change any of the source, just followed the instructions right off the firefly website
<naobsd>
btw there are some "splash"es, logo on u-boot, logo on kernel, logo on boot.img, Android boot animation...
<Tony_>
I have this experience before, my question is wrong parameter.
<prop81>
the splash screen I see is the light bulb and the word "Firefly" underneath it
<prop81>
sorry, I'm pretty new to all of this
<naobsd>
you should explain about "the instructions right off the firefly website" more, at least you can put uri. please keep in mind that here is not firefly support forum
<prop81>
I understand, is there any other rk3288 device with source available?
<naobsd>
prop81: then, any output from serial console?
<prop81>
I tried only updating system.img first, then I tried uboot,resource,kernel, boot and recovery with the same results
<Tony_>
There are some tech brief report from RK.
<naobsd>
Tony_: thanks... oh, too many docs....
<prop81>
I do not have those pins connected to anything right now
<naobsd>
prop81: did you check addresses in AndroidTool screen and addresses in parameter on your device are surely matched, in other word, what happen if you flash parameter first and all remaining images next?
<naobsd>
prop81: as far as I know, firefly is dev board. you should use serial console for development work
<naobsd>
well
<naobsd>
prop81: minor correction, confirm addresses in AndroidTool screen and addresses in parameter file are matched first, then flash parameter and all images
<naobsd>
Tony_: it looks like release notes or changelog or errata
<prop81>
naobsd: I did not flash parameter, but I confirmed address are correct
<naobsd>
prop81: if you didn't flash parameter, then you need to check parameter flashed on your firefly. parameter _file_ and parameter on your board may be different
<prop81>
naobsd: I will give that a try. Thanks for being patient with a newbie!
<naobsd>
prop81: btw, you have engineering prototype, right?
<prop81>
I just got it today
<naobsd>
I heard mass production ver. will be available at end of Oct
<naobsd>
there are some difference between prototype and production
<naobsd>
you need to built correct one
<naobsd>
build
<Tony_>
naobsd, I try to translate one. this :https://drive.google.com/open?id=0B6NGoH-iSqrKdFplWlI1R1JydVE&authuser=0
<prop81>
naobsd: happen to know what the differences are?
<naobsd>
prop81: probably it will be available when MP ver. is released
<Tony_>
naobsd, yeah, many changelog or errata, but there are many WANING about hardware. such as PMU etc.
<naobsd>
prop81: if you have prototype, you need to use config files named beta
<naobsd>
Tony_: I don't design hardware, no way to do something related to hardware :)
<naobsd>
Tony_: anyway, thank you for your information
<Tony_>
okay.
<naobsd>
prop81: I think system.img should be flashed to 0x00092000
<naobsd>
prop81: anyway, I recommend to use serial console
<prop81>
naobsd: yes, system.img is at 0x00092000. I will have to hook up the serial, so I will do some soldering tomorrow
<naobsd>
prop81: soldering? no pins on your firefly>
<naobsd>
?
naobsd has quit [Quit: Page closed]
nighty^ has quit [Quit: Disappears in a puff of smoke]
c0d3z3r0 has quit [Ping timeout: 244 seconds]
c0d3z3r0 has joined #linux-rockchip
c0d3z3r0 has quit [Ping timeout: 256 seconds]
c0d3z3r0 has joined #linux-rockchip
Astralix has joined #linux-rockchip
AstralixNB has joined #linux-rockchip
Astralix1 has quit [Ping timeout: 250 seconds]
AstralixNB1 has quit [Ping timeout: 250 seconds]
GriefNorth has joined #linux-rockchip
Tony_ has quit [Quit: Page closed]
ganbold_ has quit [Ping timeout: 255 seconds]
eebrah has quit [Remote host closed the connection]
eebrah has joined #linux-rockchip
Tony_ has joined #linux-rockchip
<Tony_>
Who can tell me that how to create boot.img alone ?
<Tony_>
I used ./mkimage shell from RK.
<Tony_>
naobsd, are you here ?
Tony_ has quit [Ping timeout: 246 seconds]
Tony_ has joined #linux-rockchip
Tony__ has joined #linux-rockchip
Tony_ has quit [Ping timeout: 246 seconds]
hipboi has quit [Ping timeout: 255 seconds]
hipboi has joined #linux-rockchip
<rperier>
mmind00: unfortunately "poweroff-source" is used by act8865 AND tps65910 now (on linux-next)
<rperier>
however the property is not used yet by dts
dlezcano has joined #linux-rockchip
selfbg has joined #linux-rockchip
hipboi has quit [Ping timeout: 258 seconds]
dlezcano has quit [Ping timeout: 272 seconds]
naobsd has joined #linux-rockchip
<Tony__>
naobsd,
<Tony__>
can you tell me that how to create boot.img only.
<Tony__>
naobsd, can you ...?
<naobsd>
Tony__: mkbootimg or mkkrnlimg or rkcrc. please tell me what you really want to do
<Tony__>
naobsd, I used ./mkimage before.
<Tony__>
It will create boot.img system.img etc.
<Tony__>
every time.
hipboi has joined #linux-rockchip
<naobsd>
mkimage.sh is shell script, you can see & understand what is done
<Tony__>
Yeah, It is.
<Tony__>
And do you know about 4.4 ?
<Tony__>
4.4 has no rknand.ko.
<Tony__>
Actually, I still think about the problem which is talk about yesterday.
<cristian_c>
but I can't identify exactly the firmaware (brand)
<cristian_c>
*firmware
<cristian_c>
I've extracted qc802_publice_ap6210_20130805.img and if I unpack it, I find a different loader: RK3188Loader(L)_V1.20.bin
naobsd has quit [Quit: Page closed]
dlezcano has quit [Ping timeout: 264 seconds]
hipboi has quit [Ping timeout: 265 seconds]
bengal has joined #linux-rockchip
hipboi has joined #linux-rockchip
<rperier>
in order to write an changelog via git send-email usually you need to write your comments after the marker line "---". Some developers seems to create a dedicated commit containing all changes since previous version (usually [PATCH v2 0/xxx ] for example). How do they do ?
<rperier>
a good example is "[PATCH v15 0/5] Rockchip soc thermal driver"
bengal has quit [Ping timeout: 250 seconds]
<rperier>
any ideas ?
<rperier>
I mean, do they create an empty commit via git commit just for that or this is an option with send-email ? I don't find on the web
<karlp>
I was just coming to ask you about that myself, your series looks cool, with v2 for 1 and 2, and v1 for 3 and 4
<karlp>
I was going to ask how you did it :)
<karlp>
I get the empty mail by using the --annotate or something, that makes a separate email at the beginning
<karlp>
and I haven't worked out how to add the comments after the marker per commit in the series.
<rperier>
in my case I type: git send-email --to <address1> <put cc here if your need> --annotate HEAD~4
<rperier>
(the 4 last commits)
<rperier>
then it open your default editor (using the variable $EDITOR) and you can edit the subject
<rperier>
I just add v1 or v2 myself
<karlp>
oh well, next time.
<rperier>
and you can edit the whole mail/patch, so you can write a comment after "---"
<rperier>
;)
<rperier>
--annotate makes a separate email at the beginning you said? strange, not here...
<rperier>
I just found
<rperier>
--compose
<karlp>
I've only used it with a patch file, not specifying HEAD~x though
<karlp>
that's it then sorry, compose
<karlp>
I wsa probably looking for annotate to let me edit the individual patches :)
<rperier>
ah yeah it's the right option
<rperier>
:)
<rperier>
I tested it locally it works just fine :)
ganbold_ has quit [Remote host closed the connection]
<rperier>
oh with format-patch too ? interesting, I tried --compose with git send-email the result is the same. it looks good
<rperier>
good to know
cristian_c has quit [Quit: Sto andando via]
mrcan_ is now known as mrcan
Celia_ has joined #linux-rockchip
Celia_ has quit [Remote host closed the connection]
FergusL has quit [Read error: Connection reset by peer]
FergusL has joined #linux-rockchip
dlezcano has quit [Ping timeout: 255 seconds]
dlezcano has joined #linux-rockchip
GriefNorth has quit [Ping timeout: 240 seconds]
ganbold_ has joined #linux-rockchip
<karlp>
format-patch --cover-letter, then just mail the file it generates?
<mmind00>
karlp: I always use "git format-patch --cover-letter -$NUMPATCHES"; edit any patches necessary including the cover letter; and send it via "git send-email *"
<rperier>
mmind00: I proposed to Mark to drop the whole serie completly from "next" (poweroff-source). Keep things simple. That's better to re-do things from scratch instead of maintaining 3 properties from "of_has_system_poweroff_source" or introduce a bisection which might break things. I don't want to send unclean commits to fix things which should not have happened.
<rperier>
(if this is possible of course)
<rperier>
now wait and see
<mmind00>
rperier: yes I read that ... if Mark is willing to drop the patches I would agree that this is the best solution
<rperier>
yes I agree
selfbg has quit [Quit: Leaving]
* mrcan
is away: afk
Bludot has joined #linux-rockchip
nighty^ has joined #linux-rockchip
dlezcano has quit [Ping timeout: 255 seconds]
dlezcano has joined #linux-rockchip
eebrah has quit [Remote host closed the connection]
eebrah has joined #linux-rockchip
FreezingCold has joined #linux-rockchip
dlezcano has quit [Ping timeout: 264 seconds]
dlezcano has joined #linux-rockchip
bengal has joined #linux-rockchip
dlezcano has quit [Ping timeout: 244 seconds]
dlezcano has joined #linux-rockchip
dlezcano has quit [Ping timeout: 258 seconds]
dlezcano has joined #linux-rockchip
dlan has quit [Ping timeout: 255 seconds]
Bludot has quit [Quit: Connection closed for inactivity]