<JohnDoe_71Rus>
and may be with other releases after Android 4.2_v1.06
<shineworld>
Actually I'm using dualboot without issues:
<shineworld>
- NAND run Cubian
<shineworld>
- SD run 4.2.2
<shineworld>
I've removed insmod nank.ko from init.rc (so android don't fuck and view nand device)
<JohnDoe_71Rus>
but this nand android - SD linux
<shineworld>
I've modified etc/vold.fstab so don't map in nand devices
<JohnDoe_71Rus>
sometimes useful to have access to the nand memory
<shineworld>
I flashed Cubian (or any other linux image) in NAND and I wrote my script to get Android working on SD :)
<shineworld>
ok can be done ... just you have to:
<shineworld>
modify monkey.cpp so don't manage uventd for /dev/block/nandk (previous mapped UDISK)
<shineworld>
change vold.fstab configuration so don't try to mount any nand device
<shineworld>
leave nand.ko in init.rc so you can mount the nand without problems (manually from adb shell)
<shineworld>
or you can always load nand.ko con insmod in anymoment
<shineworld>
JohnDoe_71Rus, the bad thing with cubieboard is ALMOST inexisten support and chaos in their sources....
<shineworld>
they make image 1.07 but don't relate what sources made it
<shineworld>
sometime they put/change new zip in dl.cubieboard..... and you have to hope that is latest version
<shineworld>
without any reference on what SDK version is
<shineworld>
just a name which every time is different
<JohnDoe_71Rus>
shineworld: yep
<shineworld>
This is not a the right way to work
<shineworld>
so I spent my time to diff AOSP with their sources to understand what's happen
<shineworld>
ah forgot that there is also a nand enabling in script.bin
<shineworld>
however to modify nand device from android isn't so usefull
<shineworld>
so I've removed any access in my SD's
<shineworld>
and reduced the boot-time....
<shineworld>
my best boot was in 14s with some tips
<shineworld>
I hope to reduce it yet
<shineworld>
Actually in my test SD is more fast than NAND BUT if I boot from NAND is more fast than SD ... sigh
<shineworld>
This is over my knowledges
tat has quit [Remote host closed the connection]
kieppie has quit [Ping timeout: 265 seconds]
rz2k has quit []
tomcheng76 has quit [Quit: leaving]
Midnightmyth has quit [Ping timeout: 252 seconds]
tomcheng76 has joined #cubieboard
tat has joined #cubieboard
hramrach has joined #cubieboard
suhanc has joined #cubieboard
NamanG has joined #cubieboard
FR^2 has joined #cubieboard
popolon has joined #cubieboard
enrico_ has joined #cubieboard
tat has quit [Remote host closed the connection]
nighty^ has joined #cubieboard
<Bushmills>
data transfer rate is only one metric, another is number of i/o per interval. sd cards are notoriously bad with that, given that they were targetted occasionally writing single bigger files, like pictures in a camera.
<Bushmills>
can't say how NAND performs with this, but that's something worth to measure when comparing the two
D0pamine has joined #cubieboard
<Bushmills>
running a random read test with small block sizes may show.
<Bushmills>
or it may not. filling both NAND and SD card with small files, maybe hashed into directories, and read the same (pseudo random) sequence of files on both should.
<shineworld>
it is a system to create an SD with Android 4.2.2 (prebuild binaries) for a friend which uses a 1024x600 LVDS display
<JohnDoe_71Rus>
shineworld: from home. now i am at work
<shineworld>
you will have only to get your script.bin and recover your SystemServer.jar from /system/framework
<shineworld>
ah ok
<JohnDoe_71Rus>
thanks
<shineworld>
pratically instead to start from sources there is inner the /system /root /recovery /uboot /kernel path with binaries
<shineworld>
so cubietool create your sd using these directories
<shineworld>
the only fix you have to do is recover standard script.bin (which is made for HDMI) and restore standard SystemServer.jar (because I've modified to avoid display re-initialization done by SurfaceFlinger.cpp just after boot)
<shineworld>
*and of android boot
<JohnDoe_71Rus>
think you patch SystemServer.jar will work with hdmi-dvi converters
<shineworld>
Uhm... I will update a version "PURE" so anyone can mote it to SD without patch nothing
<shineworld>
nah... SystemServer just check for HDMI mode, etc. and write a file in /data/xxxxx (I don't remember name). SurfaceFlinger read this file (if exist) and then restore display settings
<shineworld>
is a chain... I've just commented the SystemServer.java which create the file so SurfaceFlinger does nothing
<JohnDoe_71Rus>
at all android i get good splash with monkey but then android boot, get pink screen with wrong resolution
<shineworld>
however if you be patient I can publish a full working tool to get SD with 1.05 without personal changes
<shineworld>
this is because:
<shineworld>
the cubieboard.org android img uses a special u-boot in which (in spl) initialize the display driver and load the "monkey" image
<shineworld>
then when kernel start it read your HDMI info from monitor (if available) or in your command line and try to configure your actual display
<JohnDoe_71Rus>
this only with hdmi-dvi converters. test 2 converters, 3 hdmi cables and 3 monitors
<shineworld>
could be there is some bugs...
<shineworld>
the pink'ish is during ANDROID boot animation or after ?
<shineworld>
PS: in your system there is three points in which display is initialized:
<shineworld>
1 - in uboot (spl module) for first boot logo
<shineworld>
2 - in kernel boot
<shineworld>
3 - ant end of android boot phase (in SurfaceFlinger.cpp module)
<shineworld>
JohnDoe_71Rus, I guess just joking with systemserver you can fix your issue (or with my SD you can modify settings in uEnv.txt)
tat has quit [Remote host closed the connection]
<shineworld>
I've got same problem with my office monitor
<JohnDoe_71Rus>
shineworld: but, if i connect only hdmi it fine
<shineworld>
with my home monitor (DVI) and my TV (sony bravia 42W652) all works fine
<shineworld>
My monitors are all DVI
<shineworld>
so I'm using a DVI -> HDMI cable converter
<JohnDoe_71Rus>
i test 2 converters
<shineworld>
I don't think is a problem of converter
<shineworld>
if it work at first time it works also after
<shineworld>
Could be a problem of kernel when try to detect HDMI vs CBS vs other settings
<JohnDoe_71Rus>
I also do not think so. Linux works correctly.
<shineworld>
in SystemServer.java there is a moment in which try to get display settings
<shineworld>
All happen in SystemServer.java
<shineworld>
In a very little piece of code full of oddities (by my view point)
<shineworld>
a sec for more info
<shineworld>
During boot with logcat you can get a lot of useful messages "adb logcat | grep SystemServer"
<shineworld>
like what display type and mode the system recognized
<shineworld>
could be the kernel don't recognize corret settings from your monitor
<shineworld>
there is a way also to get all running display settings using sysfs
<shineworld>
directly in TTL console (or in adb shell dmesg if you are using adb)
<shineworld>
I don't remeber full path .... I've wrote it in a paper at home
<shineworld>
howver the latest display configuration is wrote by SystemServer.java in /data/displaysetmode file how output type (LDVS,VGA, etc) and mode (resolution model)
<shineworld>
for HDMI should have 4 and 2
<shineworld>
by default
<shineworld>
.... I need to retry in office with bad monitor but unfortunately 4.2.2 require a 64 bit system to be build (here only very old 32 bit machine)
_massi_ has joined #cubieboard
payne_ has joined #cubieboard
payne has quit [Ping timeout: 264 seconds]
kivutar has joined #cubieboard
JohnDoe_71Rus has quit [Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org]
bizarro_1 has joined #cubieboard
makka has joined #cubieboard
jluisn has joined #cubieboard
kivutar has quit [Quit: Ex-Chat]
vali has quit [Ping timeout: 240 seconds]
joph has quit [Ping timeout: 240 seconds]
makka has quit [Ping timeout: 252 seconds]
impure_hate is now known as macicka
rooted-arm has quit [Ping timeout: 240 seconds]
kivutar has joined #cubieboard
tomcheng76 has quit [Quit: leaving]
tomcheng76 has joined #cubieboard
ganbold_ has joined #cubieboard
<buZz>
11:57:59 < rooted-arm> does cubieboard support java sdk ?
<buZz>
11:58:54 < rooted-arm> java development in general
<buZz>
yes, sure
llaine has joined #cubieboard
<llaine>
does anybody ever try to install arch on a cubieboard2 ?
<n3glv_McWifi>
or can someone comment on use as xbmc device??
weltall has quit [Ping timeout: 240 seconds]
OutOfLine has quit [Ping timeout: 252 seconds]
weltall has joined #cubieboard
n3glv_McWifi is now known as n3glv
tat has joined #cubieboard
popolon has joined #cubieboard
popolon has joined #cubieboard
kivutar has joined #cubieboard
tat has quit [Remote host closed the connection]
paulo_ has joined #cubieboard
<paulo_>
sorry if dummy question, but I would like to know if I can connect directly my Cubieboard2 to PC using LAN cable without to connect them to the router (is far now)... So CUBIE -> LAN CABLE -> PC LAN Port
FR^2 has joined #cubieboard
<rm>
paulo_, should be able to
<rm>
not sure if the CB NIC is Auto-MDIX capable (90% likely it is), but your PC should be (99%)
<rm>
and that's required only on one end
<Kamilion>
all gigabit NICs should be Auto-MDIX
<Kamilion>
I'm pretty sure it's required in the specification at this point.
<rm>
CB2 is not gigabit though?
<paulo_>
this shound good... I need to use a reversing cable ?
<Kamilion>
PC-side
<paulo_>
CB2 isn't gibabyte
<rm>
not all PCs are gigabit :)
<Kamilion>
Any PC with a gigabit port will do auto crossover.
<Kamilion>
"Subsequently, Dove promoted auto MDI-X within the 1000BASE-T standard[5] and also developed patented algorithms for "forced mode auto MDI-X" which allow a link to be automatically established even if the port does not auto-negotiate."
<paulo_>
Unfortunately I don't reach my routher with WIFI dongle so I'm trying to connect Cubieboard directly to PC Lan PORT
<Kamilion>
if PC lan port is gigabit, it will work
<Kamilion>
if it's 100mbit, it will *probably* work.
<Kamilion>
It works for my cubieboard2
<Kamilion>
and the cubietruck is the same PHY connected to the A20, to my knowledge
<paulo_>
1 x RTL8111D chip (10/100/1000 Mbit)
<paulo_>
my board is a Gigabyte GA-P55A-UD3
<Kamilion>
mine is GA-890GPA-UD3H
<Kamilion>
1 x Realtek 8111D chip (10/100/1000 Mbit)