wickwire has quit [Remote host closed the connection]
field^Mop has joined #radxa
naobsd has quit [Remote host closed the connection]
naobsd has joined #radxa
field^Mop has quit [Ping timeout: 244 seconds]
AstralixNB has joined #radxa
Astralix has joined #radxa
Astralix1 has quit [Ping timeout: 264 seconds]
AstralixNB1 has quit [Ping timeout: 264 seconds]
irsol has quit [Ping timeout: 264 seconds]
irsol has joined #radxa
<Shdwdrgn>
I was wrong, it still didn't finish the build. Had to figure out how to install the actual Sun JDK6 on my machine. Been compiling the kernel for 5 hours now, guess I'll have to wait overnight for it to finish.
<naobsd>
Shdwdrgn: what are you compiling? full Android? kernel?
<Shdwdrgn>
full android
<Shdwdrgn>
I'm doing the "make -j8" step right now
<naobsd>
Shdwdrgn: do you have 8GB ram or so?
<Shdwdrgn>
of course this begs the question... did I only need to do "make kernel.img" to get the additional drivers for my touchscreen, or is the full android build actually needed?
<Shdwdrgn>
haha no I only have 4GB of ram
<naobsd>
how man cores?
<Shdwdrgn>
2 very old cores... its an Athlon X2-6400
<naobsd>
then between -j2 and -j4 will be better...
<naobsd>
and if you need only kernel,
<naobsd>
make kernel.img is enough
<Shdwdrgn>
hmm figures... OK I'll make a note to change the -j8 for the next time I do this
<Shdwdrgn>
I'm heading to bed shortly anyway, so no time to flash the kernel over and test the touchscreen tonight. I'll get it installed tomorrow after work.
<naobsd>
I don't know only make kernel.img is enough for you. what I know is make kernel.img is enough for building kernel
<naobsd>
what you need is another story
<naobsd>
good night!
<Shdwdrgn>
well I selected to include the drivers in the kernel rather than making modules, so it makes sense that the kernel image alone would be enough
<naobsd>
what I talked is not "only kernel or with modules"
<Shdwdrgn>
eventually I'll want to customize the android setup anyway, so it doesn't hurt to get the experience of compiling the whole thing.
<naobsd>
then trying to build full android will be good for you
<Shdwdrgn>
I'm trying to put together a carPC. I have all the hardware now except for the harness to replace my existing stereo, so now I just need to learn enough about android to build the display the way I want it
<Shdwdrgn>
I think the hard part is going to be finding an app that gives a nice display like a car stereo, but works with an rtl-sdr
Astralix has quit [Ping timeout: 264 seconds]
AstralixNB has quit [Ping timeout: 264 seconds]
paowz has quit [Ping timeout: 264 seconds]
paowz has joined #radxa
AstralixNB has joined #radxa
Astralix has joined #radxa
paowz has quit [Ping timeout: 244 seconds]
paowz has joined #radxa
hipboi has joined #radxa
wickwire has joined #radxa
hipboi has quit [Remote host closed the connection]
<Vutral>
hm ^^
paowz is now known as PaowZ_laptop
PaowZ_ has quit [Remote host closed the connection]
<PaowZ_laptop>
hi there !! Concerning the radxa-lite, what sdcard address is being read by the board upon startup, in order to read parameter file ? (I assume the board is reading parameter file before anything, is that right ??)
PaowZ_laptop has quit [Quit: Leaving]
PaowZ_ has joined #radxa
<naobsd>
PaowZ_: CPU load bootloader, bootloader load parameter etc
<PaowZ_>
hi naobsd, thanks for the reply.. ok, bootloader expects to see parameter file at what address on sdcard? 0x0 ?
<paowz>
I built a kernel and a rootfs.. I guess I have to merge a parameter file + boot.img + rootfs into one .img before flashing on sdcard.. am I right ?
wickwire has quit [Read error: Connection reset by peer]
shdw_work has joined #radxa
<shdw_work>
So is the talk page completely borked right now?
<shdw_work>
I'm getting wierd messages during login, cannot go to the next page under any group, and cannot post a new topic
<shdw_work>
tried closing out and clearing cookies, logged back in with the same results
<shdw_work>
went to that page, scrolled to the bottom, clicked the button for next page, and it takes me to http://talk.radxa.com/category/16/linux# which still displays the same set of messages.
<shdw_work>
same results for both chrom and firefox
<shdw_work>
*chrome*
<shdw_work>
and nothing at all happens when I click the new topic button
<shdw_work>
well lets try restarting FF... although that doesn't explain why the same thing happens in chrome?
Vutral has quit [Ping timeout: 264 seconds]
sybshfjkl has joined #radxa
field^Mop has joined #radxa
steev has quit [Ping timeout: 265 seconds]
steev has joined #radxa
Vutral has joined #radxa
<shdw_work>
nope, even after fully restarting firefox I still can't go to the next page
<shdw_work>
wait a minute... is this website written in *flash*???
qloogkm has quit [Read error: Connection reset by peer]
qloogkm has joined #radxa
hramrach has quit [Remote host closed the connection]
hramrach has joined #radxa
paowz has quit [Ping timeout: 264 seconds]
sybshfjkl has quit [Quit: Page closed]
paowz has joined #radxa
field^Mop has quit [Ping timeout: 244 seconds]
Vutral has quit [Ping timeout: 244 seconds]
field^Mop has joined #radxa
Turl_ has joined #radxa
Turl has quit [*.net *.split]
Vutral has joined #radxa
Vutral has quit [Excess Flood]
Vutral has joined #radxa
<shdw_work>
still not having any luck here... upgraded to the latest firefox and the latest flash, getting the same results on the forum
field^Mop has quit [Ping timeout: 245 seconds]
naobsd has quit [Quit: naobsd]
field^Mop has joined #radxa
field^Mop has quit [Ping timeout: 265 seconds]
shdw_work has quit [Quit: They're coming to take me away, ha ha]