<focus_it>
doesn't mention emac in sun7i_defconfig
Guest32283 has quit [Quit: Leaving]
<focus_it>
Turl: thanks - I will put CONFIG_SUNXI_EMAC=y in sun7i_defconfig and recompile tomorrow - bye for now
focus_it has quit [Quit: Leaving]
popolon has quit [Quit: Quitte]
deasy has quit [Quit: Nom d'un quark, c'est Edmonton !]
steev has quit [Excess Flood]
steev has joined #linux-sunxi
kaspter has joined #linux-sunxi
kaspter has quit [Remote host closed the connection]
egbert has quit [Disconnected by services]
egbert has joined #linux-sunxi
vinifr has quit [Quit: Saindo]
akaizen has quit [Remote host closed the connection]
naobsd has quit [Quit: Page closed]
naobsd has joined #linux-sunxi
[7] has quit [Disconnected by services]
TheSeven has joined #linux-sunxi
book` has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
HeHoPMaJIeH has quit [Read error: Operation timed out]
HeHoPMaJIeH has joined #linux-sunxi
vaxholm has joined #linux-sunxi
atiti has quit [Ping timeout: 264 seconds]
drachenphone has joined #linux-sunxi
drachenphone2 has quit [Read error: Connection reset by peer]
drachenphone2 has joined #linux-sunxi
drachenphone has quit [Ping timeout: 260 seconds]
vaxholm has quit [Ping timeout: 245 seconds]
iamfrankenstein has joined #linux-sunxi
Quarx has joined #linux-sunxi
ZetaNeta has joined #linux-sunxi
HeHoPMaJIeH has quit [Changing host]
HeHoPMaJIeH has joined #linux-sunxi
<rm>
drivers/misc/pwm-sunxi.c:51:24: fatal error: pwm-sunxi.h: No such file or directory
<rm>
this mess
<rm>
barely even compiles
atiti has joined #linux-sunxi
hipboi has joined #linux-sunxi
kaspter has joined #linux-sunxi
iamfrankenstein has quit [Quit: Nettalk6 - www.ntalk.de]
<hno>
rm, odd, that file is there..
iamfrankenstein has joined #linux-sunxi
n01 has joined #linux-sunxi
<hno>
rm, builds for me.
<rm>
yeah strange
<rm>
I checked, it's there on my copy too
<HeHoPMaJIeH>
i have the same issue
<rm>
but the build failed with that message, so I just disabled the PWM driver now
<hno>
are you building in-tree or with a separate object directory?
* hno
does the latter
<rm>
in-tree
<HeHoPMaJIeH>
if file is included with system file include #include <sunxi-pwm.h> build fails :)
<hno>
which branch are you building?
<rm>
sunxi-v3.4.43-r2 tag
<hno>
HeHoPMaJIeH, indeed. And I guess that bits in-tree builds but not when using a separate object directory.
<hno>
gah.. this driver is messing with PIO directly, not using pinmux registration. This will fail.
<hno>
rm & HeHoPMaJIeH should be fixed now.
vaxholm has joined #linux-sunxi
<HeHoPMaJIeH>
hno, 10x
rellla has joined #linux-sunxi
gnufan has joined #linux-sunxi
massi_ has joined #linux-sunxi
Clement_ has joined #linux-sunxi
TheViking has joined #linux-sunxi
akaizen has joined #linux-sunxi
FR^2 has joined #linux-sunxi
<oliv3r>
backreading! and the scrollbackbuffer ate some of my buffer
FDCX_ has joined #linux-sunxi
<TheViking>
oliv3r: Just a followup, thank you for the recommendation on a serial cable.
kaspter has quit [Ping timeout: 264 seconds]
fredy has quit [Excess Flood]
fredy has joined #linux-sunxi
<TheViking>
f2fs backports seem to work ok on the current linux-sunxi 3.4 kernel.
panda84kde has joined #linux-sunxi
<oliv3r>
wingrime: the lcd_bak, isn't that the backlight? Why would they bitbang stuff ... there's plenty of SPI and i2c pins available ... maybe to directly hack in touchscreen? backlight drivers? PWM takes care of backlight normally. did you find naymore smore specifics?
atiti has quit [Ping timeout: 245 seconds]
ZetaNeta has quit [Ping timeout: 245 seconds]
notmart has joined #linux-sunxi
notmart has joined #linux-sunxi
<oliv3r>
ssvb: while backreading, can A10 run at 600 MHz mbus too? does that improve 1080p playback? (higher refresh rate?)
<TheViking>
oliv3r: You want to run the memory at 600MHz?
wingrime has joined #linux-sunxi
popolon has joined #linux-sunxi
<TheViking>
oliv3r: Also, you asked wingrime a question when he wasn't online earlier. You might want to ask again :-)
Black_Horseman has quit [Remote host closed the connection]
<arokux>
what is the best allwinner tablet right now?
<oliv3r>
TheViking: mbus :)
<oliv3r>
wingrime: i commented on your comment, the 'from' thing he should figure out himself :p
<oliv3r>
TheViking: serial cable? refresh my memory?
<oliv3r>
wingrime: the lcd_bak, isn't that the backlight? Why would they bitbang stuff ... there's plenty of SPI and i2c pins available ... maybe to directly hack in touchscreen? backlight drivers? PWM takes care of backlight normally. did you find naymore smore specifics?
<oliv3r>
arokux: 'best' is hard to describe, a nice screen, a20 or a10, 1gb + memory should work decent
<oliv3r>
512mb works; but is a little tight imo
<arokux>
oliv3r, best is 1gb, dual core (possibly quad core, but here the battery life comes into play), but the most important is the manufacturing quality
mcbrick has quit [Quit: Leaving]
Tsvetan has joined #linux-sunxi
<oliv3r>
arokux: quad core? that'll be A31, not sure if you want that :)
<arokux>
oliv3r, that be for elderly ppl, they will happily use android while I will hack on Mele and Cubietruck :)
<oliv3r>
yeah, but A31 is powerVR :)
gnufan has quit [Ping timeout: 245 seconds]
<arokux>
oliv3r, well, world isn't perfect. trade-offs need to be made you know..
<arokux>
oliv3r, so do you know a few decent manufacturers? :)
<TheViking>
oliv3r: I asked around for a serial-to-usb cable a few days ago. You linked me to one on DX.
<ssvb>
and I don't quite understand the FIXME part of the comment
<oliv3r>
hno: well for sun4i it looks like mbus is hardcoded and writing anything to those registers goes up in the void!
<hno>
Manual says MBUS_clock = PLLx / 2^N / (M+1)
<oliv3r>
Turl: are you sure you tested it right? I'm thinking a little bit about it, and you are basically reconfiguring pll5, right? and none of those changes influence the mbus?
<hno>
Right.. It's PLL6*2 if PLL6 is used.
<hno>
annoyingly the MBUS clocking is not part of the clock tree diagram.
<oliv3r>
hno: for sun4i or sun7i?
<hno>
sun7i. There is no mention of MBUS in any sun4i resources (manual or sources)
<oliv3r>
hno: yeah turl suggested that it might be hardcoded
<oliv3r>
while I don't understand hardware that much, i find it hard to imagine that sun4i doesn't have an mbus
<oliv3r>
actually I did find 1 reference to the mbus in the a10 user manual
<oliv3r>
it's in the display diagram
<hno>
where?
<oliv3r>
it shows how the display unit is connected to the mbus
<oliv3r>
but nothing really other then that
jemk has joined #linux-sunxi
<oliv3r>
don't know if i can easily link that section of the document :)
<hno>
in which chapter?
<oliv3r>
ok let me find it
gnufan has joined #linux-sunxi
<hno>
I have only seen that diagram in A20 manual.
<oliv3r>
hmm, now i'm in doubt
<vaxholm>
speaking of manual... how come the a20 user manual lacks info on nfc and usb otg registers? deliberate or wip?
<oliv3r>
maybe i saw in in A13 manual
<oliv3r>
vaxholm: deliberate
<vaxholm>
k
<oliv3r>
chapter 27 of a13 (page 286)
<oliv3r>
so it may have been wrong on my end :(
gzamboni has quit [Remote host closed the connection]
gzamboni has joined #linux-sunxi
eebrah has joined #linux-sunxi
eebrah is now known as Guest18545
<hno>
oliv3r, but A10 manual is quite confising and incoimplete in this area so...
<hno>
oddly a13 manual have better clock tree than a20.
JohnDoe_71Rus has quit [Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org]
<oliv3r>
hipboi: might know :) does a10 have an mbus like a13 and a20 (very very likly it does) and it it hardcoded on a10? (registers don't do anything)
<hipboi>
oh, mbus
<hipboi>
it sounds familiar...
<oliv3r>
Memory bus I think :)
TheViking has quit [Ping timeout: 250 seconds]
<ssvb>
hno, oliv3r, Turl, hipboi: should we ask allwinner people whether it is safe to increase mbus clock speed to 400mhz for a20?
<ssvb>
just like 240mhz -> 300mhz increase, it improves memcpy/memset performance and also some memory performance limited mali benchmarks
<hipboi>
i think we had better test it
vaxholm has quit [Ping timeout: 240 seconds]
<hipboi>
i just did a grep in boot0 and no mbus found
<hipboi>
sunxi.org:/tmp
<hipboi>
sunxi.org:/tmp/boot_23.tar.gz
<ssvb>
hipboi: with 600mhz mbus the systems boots, but deadlocks later on heavy memory usage
<ssvb>
hipboi: 400mhz and 480mhz mbus seems to work without visible problems (but I have a lucky a20 chip, which works fine with 480mhz memory clock)
<hipboi>
what's the relationship with mbus clock and ddr clock
<hipboi>
the one we set in script.fex
<oliv3r>
HTTP request sent, awaiting response... 404 Not Found
<oliv3r>
:(
<oliv3r>
oh let me ssh in
<ssvb>
my guess is that MBUS is something like FSB from desktop PCs, if you have it clocked too low, then it becomes a bottleneck and the memory bandwidth is wasted
vaxholm has joined #linux-sunxi
<oliv3r>
hipboi: so mbus should be in sync with ddr freq?
auxym has quit [Ping timeout: 264 seconds]
<oliv3r>
hipboi: or should never be higher then ddr freq*
<oliv3r>
kinda sounds sensible :p
<oliv3r>
but ssvb knows more about this memory timing stuff then me
auxym has joined #linux-sunxi
<ssvb>
oliv3r: they don't necessarily have to be in sync, and also I think that mbus is probably wider (maybe 64-bit)
<oliv3r>
i think that's the function that setups pll5 for mbus
<oliv3r>
ssvb: ok so is it a bad thing to run the mbus HIGHER then the ddr freq?
<oliv3r>
ssvb: from my simple mind, I would think, if you write something to the ram, at a higher freq then what it's running at, havoc ensures :p
<ssvb>
oliv3r: well, we have ddr memory, so it does 2 transfers per cycle
<ssvb>
oliv3r: as for the mbus speed, with 240mhz we had ~1.6GB/s memset, with 300mhz mbus we got ~2GB/s memset, with 480mhz or 600mhz mbus Turl got ~3GB/s memset
<oliv3r>
but you've reported instability with 600 MHz?
<oliv3r>
i probably should try to understand how a 600 MHz mbus correlates to a 480 MHz DDR bus
<ssvb>
oliv3r: yes, but there is little difference between 480mhz and 600mhz
<oliv3r>
should not*
<ssvb>
oliv3r: based on the memset performance numbers, the speed is 6.5 bytes per mbus cycle
<ssvb>
oliv3r: which looks like 64-bit mbus width
<oliv3r>
sounds probable
<ssvb>
oliv3r: and ddr is "double data rate", so it's twice 32-bit per dramc cycle
<ssvb>
oliv3r: the optimal configuration seems to be mbus clock matching the dramc clock
<ssvb>
oliv3r: however we don't know if mbus is really stable at 480mhz
<oliv3r>
would the mbus be unstable, or the ddr itself?
<ssvb>
we need to test it :)
<oliv3r>
i don't understand how a 600 MHz mbus, can write data on a 480 MHz running ddr bus
<oliv3r>
i would expect not everything would make it in :)
<oliv3r>
ssvb: now if the mbus would be 32 bit, i can see how you could run it x2 DDR
auxym has quit [Ping timeout: 248 seconds]
auxym has joined #linux-sunxi
<ssvb>
oliv3r: because we don't know any fine details about the mbus from allwinner, I think treating it kind of like http://en.wikipedia.org/wiki/Front-side_bus might be not too wrong
<hno>
hipboi, not sure if there is a direct relation between MBUS and DDR clocks.
<oliv3r>
ssvb: so while i still have to backread; does this improvement make 1080p @ 50Hz with 24/32 bpp possible?
<ssvb>
oliv3r: screen shaking with 1080p is a major problem for a10, but it does not look like we can fix it with mbus there
<oliv3r>
well Turl said you found that the mbus register is ignored on a10
<ssvb>
yep
<oliv3r>
so for a20, will it help ther?
Clement_ has quit [Ping timeout: 250 seconds]
<ssvb>
you can write any garbage to the mbus register from u-boot, and a10 boots fine and shows exactly the same memory performance
<ssvb>
I can run some tests with a20, trying different mbus and dram clock to see whether we get the same "screen shaking" effect at low mbus/dram clock
<oliv3r>
ssvb: that would be interesting indeed
<oliv3r>
(i can't atm, no hardware, and @ work)
n01 has quit [Quit: Lost terminal]
n01 has joined #linux-sunxi
shineworld has joined #linux-sunxi
<vaxholm>
ssvb, this screen shaking, is that believed to be related to mismatching clock speeds?
<vaxholm>
(sorry for asking a lot of nosy questions, but i'm curious.)
<ssvb>
vaxholm: more like framebuffer scanout gets starved and does not have enough memory bandwidth left to send pixels to hdmi
<vaxholm>
ssvb: that's using external dram for framebuffer?
<ssvb>
there is no dedicated video memory in allwinner devices, system memory is also used for the framebuffer and everything else
<hno>
The MBUS looks like a data bus between DDR controller and a number of DMA controllers. The MBUS likely manages both internal and external transactions.
<vaxholm>
ssvb: ... which poses a problem if the bus speed is too low and screen resolution is too high. i see, thanks.
<hno>
vaxholm, yes that's always a problem at higher resolutions.
<hno>
display, gpu, vpu, video mixer etc all start to compete about the bus bandwidth.
<vaxholm>
nod. is there any better block diagram than the powerpointy think in the a20 user manual?
<vaxholm>
s/think/thing/
<oliv3r>
vaxholm: not really; well there's always 'the code'
<vaxholm>
i think that could be useful for "point-n-tell" about different buses.
<vaxholm>
i got a kernel booting yesterday. i'll add a tutorial to the wiki on how to get the two LEDs on the CB to blink in five different ways... from plain u-boot up to /sys/class/leds/
<vaxholm>
then we'll see where i go. this seems like a fun channel. :)
<hno>
vaxholm, there is some quite nice things that can be done with led triggers in Linux.
<vaxholm>
yepp. maybe the last tutorial step is adding ledtrig support
<hno>
only problem is that you soon run out of the two leds...
<vaxholm>
of course. it's just a CBL on getting started. like FirstSteps with a goal.
<ssvb>
oliv3r, Turl: and for the CPU, there is also AXI on the way to memory, its clock might be relevant (if MBUS stops being the bottleneck)
<vaxholm>
err.. PBL
<oliv3r>
ssvb: so lots of stuff to play with
auxym has quit [Ping timeout: 245 seconds]
auxym has joined #linux-sunxi
hipboi has quit [Quit: Leaving]
auxym has quit [Ping timeout: 264 seconds]
auxym has joined #linux-sunxi
Guest18545 has quit [Ping timeout: 260 seconds]
auxym has quit [Ping timeout: 248 seconds]
auxym has joined #linux-sunxi
<hno>
AXI is relevant for CPU accesses to mostly anything. But is not involved graphics.
auxym has quit [Ping timeout: 245 seconds]
<hno>
oliv3r, yes, DRAM clock setup configures PLL5.
deasy has joined #linux-sunxi
auxym has joined #linux-sunxi
<oliv3r>
wingrime: whilst still backreading, the i2c and spi bitbang stuff you found in the lcd_bak; maybe it's related to TV-Out?
<oliv3r>
hno: so it configues pll5; but the mbus bits are hardcoded?
<oliv3r>
ok i just stumbled upon the FIrefox OS on a31 thing. Idiots. They will have to do a shitload of work, or use vendor kernel and don't do any work at all
<oliv3r>
i guess it's good for a31 if they'd actually put in the work
shineworld has quit [Quit: Sto andando via]
<deasy>
"FPU: Vector Floating Point Unit (standard ARM VFPv3 FPU Floating Point Unit)"
<deasy>
can i think this information is false are the a10 have a vfplite?
<deasy>
s/are/like/
<deasy>
the information is also really redundant
<deasy>
vfp+fpu+floating point unit in the same sentence
auxym has quit [Ping timeout: 245 seconds]
<hno>
oliv3r, seems that Firefox OS is using Andoid kernel & libc, so they happily just swallow whatever Android blobs vendors throw at them.
<arokux>
wigyori, ping
<Tsvetan>
hno does this make them GPL violators ;)
<hno>
Tsvetan, if they use Allwinner SDK yes..
<deasy>
what?
<deasy>
firefox os is ported on allwinner?
<hno>
Tsvetan, but it's not too hard to fix those GPL violations today.
<hno>
as you already know.
auxym has joined #linux-sunxi
<hno>
Comment was more that Firefox OS on this class of devices uses whatever hardware support Android 4 is providing, but running Firefox OS application instead of the Android launcher.
<wingrime>
hark: please read part with vdpau problem
<wingrime>
err
<wingrime>
jemk: please read part with vdpau problem
boycottg00gle has quit [Remote host closed the connection]
panda84kde has quit [Read error: Connection reset by peer]
tgaz has joined #linux-sunxi
<deasy>
buZz, yes
<buZz>
yes
<buZz>
what?
<buZz>
ah
<buZz>
yes
<buZz>
:P
wingrime has quit [Read error: Operation timed out]
Quarx has quit []
vaxholm has quit [Ping timeout: 245 seconds]
binaryferret has quit [Ping timeout: 256 seconds]
binaryferret has joined #linux-sunxi
FR^2 has joined #linux-sunxi
<deasy>
buZz, him answer to questions on the site
_enrico_ has quit [Quit: Bye]
<libv>
base mali clock is 600MHz, which is nice
massi_ has quit [Quit: Sto andando via]
<deasy>
he*
ykchavan has joined #linux-sunxi
iamfrankenstein has quit [Quit: Nettalk6 - www.ntalk.de]
n01 has joined #linux-sunxi
<Turl>
ohai n01
pirea has joined #linux-sunxi
<pirea>
xbmc + libvdpau-sunxi is working?
gnufan has quit [Ping timeout: 260 seconds]
ykchavan has quit [Ping timeout: 240 seconds]
<oliv3r>
pirea: where did you hear that?
<pirea>
oliv3r nowhere
<oliv3r>
so what makes you think that that's possible allready?
_BJFreeman has joined #linux-sunxi
iamfrankenstein has joined #linux-sunxi
_BJFreeman is now known as BJfreeman
<n01>
Turl: hi
Galland has joined #linux-sunxi
brain_ has joined #linux-sunxi
<Galland>
hi
<brain_>
Hello everyone
<brain_>
I am not sure if this is the place to ask this but here goes, I am working on porting CM10 to my allwinner A10 Tablet, i have to use the stock prebuilt kernel 3.0.8 due to a custom factory touchscreen driver which I cannot rebuild... So far Touch, Wifi, interface, storage all working. I am battling audio output issues and have no idea were to look or if this is simply impossible.
jemk has quit [Ping timeout: 264 seconds]
<brain_>
I have heard that i can only get CM9 with this kernel but am unable to find a full source tree to base off of, currently using Christiontroys tree tweaked a bit to work.
arokux2 has joined #linux-sunxi
<brain_>
the stock kernel was from a 4.0.4 ROM so i'm starting to suspect this is not gonna work or might POSSIBLY work on CM9 if only I could find a full allwinner a10 tree to base off of.
<techn__>
brain_: I think no one here uses 3.0.8 kernel
<techn__>
everyone is currently focused on 3.4.x kernel
<techn__>
and mainline
<brain_>
I kinda figured that, I have no other options due to the touchscreen being custom from the factory. if I could get the FT5x_TS working i could move on but I ran out of idea down that path as well.
<techn__>
ft5x should work with 3.4 kernel too
<deasy>
stable 3.11.1 is realeased ;)
<deasy>
-a
<deasy>
what is the difference with mainline? mainline is the outdated now no?
<brain_>
I am only able to load the OEM touchscreen into various 3.0 kernels. if their was a way to make the prebuilt OEM module load into a newer kernel i'm all ears lol.
<techn__>
deasy: mainline .. not yet released latest kernel SCM head
<brain_>
If I built my own ft5x module from source it does not respond at all. the output from the oem module seems to have been heavily tweaked compared to the mainline ft5x module.
<deasy>
techn__, can you use complete words instead of short, as i'm not familiarised with it? thank you
<brain_>
that is my modules output, i have no tried the kernel you linked. tried many 3.0 kernels up to 76
<techn__>
brain_: how cat /dev/input0 responds?
<techn__>
oh.. it's input2
<brain_>
I can only get output from cat /dev/input when using OEM module, that "szg" stuff in the oem module confuses me, i cannot find any code that will reproduce the init section.
pirea has quit [Quit: Leaving]
<brain_>
I would rather fix the module so I could get my ubuntu touch working as well and ditch android but again, dead end it seems.
<atsampson>
brain_: I've recently got CM9 and CM10 going on an A10 tablet (with ft5x but the stock driver works for me)
<atsampson>
CM10 was fairly straightforward; CM9 has bitrotted quite a bit and needed some hand-hacking
notmart has quit [Quit: notmart terminated!]
<brain_>
atsampson, did you oem module have any custom init lines like my pastebin or was it a standard module from any tree?
<atsampson>
in yours, "twi_addr=70" suggests it's on a different I2C address from mine...
Galland has left #linux-sunxi ["Saliendo"]
<brain_>
odd, my built modules looked very similar but i got no output from cat /dev/input*
<atsampson>
that might be what you'd expect if it's on a different address (or a different interrupt, or something); maybe your custom module has something different hardcoded in it...
<atsampson>
anyway, if it's of any use to you, I've put my manifests and some notes on what I had to hand-hack here: http://offog.org/stuff/cm/
<brain_>
thank you atsampson, i'll give that a shot next, thanks for the help and I will see how this works out.
auxym has quit [Quit: Lost terminal]
<brain_>
the stock firmware is just horrid, CM10 really moves on my tab compared to stock. even if I can get CM9 i'll be happy...lets see.
pacopad has joined #linux-sunxi
vaxholm has joined #linux-sunxi
tgaz has quit [Quit: Over and out]
tgaz has joined #linux-sunxi
tgaz has quit [Client Quit]
tgaz has joined #linux-sunxi
tgaz has quit [Client Quit]
pacopad has quit [Read error: Connection reset by peer]
<ZetaNeta>
what is the proccess of porting Linux onto new A13 board
<oliv3r>
ZetaNeta: A23?
tgaz has joined #linux-sunxi
<oliv3r>
ZetaNeta: nobdoy has an a23 yet, but we expect it to be sun7i with less options
<ZetaNeta>
13
<ZetaNeta>
oliv3r, 13!
vaxholm has quit [Quit: Leaving]
<oliv3r>
A13 is sun5i which is old and well supported
<tgaz>
new here, but thinking of revamping the wiki. hard to find the important stuff (boot sequence, what the different tools do, which branch to use)
mturquette has quit [Changing host]
mturquette has joined #linux-sunxi
<hno>
oliv3r, yes, it's been rock solid forever, but now it's very unstable, most times failing SDRAM initialization even on the stock factory test image.
<hno>
and easily hangs later if it gets past SDRAM setup.
<hno>
sad time.
<oliv3r>
:(
<oliv3r>
ironically i pronounced the A10 dead today!
<hno>
you did?
<oliv3r>
yeah, since i do most work now on a20, and CB1's phy is broken again/still
<oliv3r>
so i shun it!
<oliv3r>
yet my tablet is a10 and i use it daily ;)
<ZetaNeta>
one of my tablets is on a10.
<ZetaNeta>
Anyone know a replacement..... touchscreen.... and the board...... for it?
<ZetaNeta>
Becouse top part of the screen is dead
<ZetaNeta>
And the power switch too
<ZetaNeta>
through, powerswitch isnt much trouble
nove has quit [Quit: nove]
<hno>
ZetaNeta, there several thousand different A10 tablet models by too many manufacturers... but sounds like it would be cheaper to get a new tablet than trying to repair.
<ZetaNeta>
hno, Had same idea
eebrah is now known as O_o
<steev>
><
<steev>
post office didn't redeliver my package
O_o is now known as O_o|eebrah
<ZetaNeta>
oliv3r, Should it be ok to use android script.bin with linux
<ZetaNeta>
(Or android being retarded again?)
O_o|eebrah is now known as x_x|eebrah
<oliv3r>
yeah
<oliv3r>
its identical
<ZetaNeta>
^^
<ZetaNeta>
can i somehow gather u-boot from my device?
<ZetaNeta>
or somehow add my device
<ZetaNeta>
Olaff,
<ZetaNeta>
oliv3r,
<ZetaNeta>
You should change you nickname. Or kick the Olaff somehow
<oliv3r>
haha, oliver is taken
<ZetaNeta>
ofcourze, thats freenode. Its not all that free
<ZetaNeta>
Try 111. you will most probably be the first one in everyones tabs
<hno>
stock u-boot do nothing... only loads Android kernel image and boots it. relies on Allwinner bootloader running before it.
Black_Horseman has joined #linux-sunxi
Black_Horseman has joined #linux-sunxi
Black_Horseman has quit [Changing host]
<hno>
not quite sure why they added the u-boot step after their bootloader.
<ZetaNeta>
hno, Tons of reasons to use u-boot
<ZetaNeta>
hno, I already submitted it
<ZetaNeta>
But, i like need linux on it tomorow :P
<ZetaNeta>
With nmap, msf, xchat and terminator
<hno>
ZetaNeta, adding your board to u-boot is easy. sunxi-tools/bootinfo your_dumped_boot1_header
<ZetaNeta>
:D
<ZetaNeta>
And where do i get the header?
<hno>
gives you the data you need.
<hno>
by the instructions in the link above.
<hno>
you then need to add your board to boards.cfg boards/sunxi/dram_... and boards/sunxi/Makefile
focus_it has joined #linux-sunxi
fredy has quit [Excess Flood]
<brain_>
I had no problem building u-boot for my tablet..the problem came up when i powered it up holding 1 in serial console and replacing the bin...after that the new uboot would load instantly with no countdown to stop autoboot so I was kinda stuck.
<ZetaNeta>
A10 USB FEL device not found!
<ZetaNeta>
brain_, The problem is that my device is new
<ZetaNeta>
hno, USE MAGIC TO FIX MY PROBLEM!
<brain_>
ahh gotcha.
fredy has joined #linux-sunxi
<ZetaNeta>
And change my CPU to A10 :D
<ZetaNeta>
jk
<ZetaNeta>
i like a13
<brain_>
I dont like odd numbers.. :) A10 for me
<ZetaNeta>
it doesnt seem to boot into fel
<ZetaNeta>
and doesnt seem to be A10
<ZetaNeta>
how should this mode look like?
<ZetaNeta>
hno, Do you mean i need to get script.fex?
<brain_>
felboot on mine is volume-up > insert USB cable > power X5
<brain_>
or their is a button to make it simple :) but i rarely use it, too small
n01 has quit [Read error: Connection reset by peer]
<brain_>
or blank the whole Nand lol
n01 has joined #linux-sunxi
<ZetaNeta>
YAY
<ZetaNeta>
booted it!
drachenphone2 has quit [Ping timeout: 245 seconds]
<brain_>
different from A10?
<ZetaNeta>
?
<ZetaNeta>
This tablet is A13
<brain_>
you booted into fel?
<ZetaNeta>
hno,
<ZetaNeta>
yup
* ZetaNeta
feels like having linux soon!
<ZetaNeta>
*le crazy me dance*
<buZz>
\o/
<buZz>
congratz :)
<ZetaNeta>
o.o libusb usb_bulk_send error -7 o.o
<ZetaNeta>
*omg, omg, what to do?*
<ZetaNeta>
oliv3r, hno!
<ZetaNeta>
Come the here and the help the me the put the linux on the A13 the tablet
wingrime has joined #linux-sunxi
wingrime has quit [Client Quit]
<oliv3r>
ZetaNeta: no clue :p
<brain_>
I was able to boot CM9 completely into android UI with most hardware working using A13 build so there can't be many differences to make linux work. only had some screen flicker.
<ZetaNeta>
brain_, The thing is.... There is no android build for it either
<oliv3r>
ZetaNeta: what is on your tablet right now?
<oliv3r>
just prepare an SD card as explained on the wiki for starters :)
<ZetaNeta>
android, but i mean there is no android build for it exept stock
<ZetaNeta>
ls
<ZetaNeta>
sry
<ZetaNeta>
wrong place XD
<brain_>
hmm, then i wonder what the heck I installed lol.
<ZetaNeta>
brain_, Can you understand that all A13 are different. Its not like only thing that matters is cpu
<ZetaNeta>
The thing is the board
<ZetaNeta>
They work different
<brain_>
i usually just swapped script.bin...i dunno its been a while before I gave up on pre built stuff.
<ZetaNeta>
Well, i tried that
<ZetaNeta>
With olinuxino board configs
<ZetaNeta>
Didnt work
<ZetaNeta>
also i tried even the MID one. Yet, nothing
<focus_it>
not sure what needs doing to get hdmi going - any clue helpful
<Turl>
focus_it: have you tried disabling the lcd stuff and using just hdmi?
<Turl>
(on fex)
Nikolas has quit [Ping timeout: 248 seconds]
<focus_it>
i can try that - the lcd i do need it - eventually
Nikolas has joined #linux-sunxi
ZetaNeta has joined #linux-sunxi
ZetaNeta has quit [Changing host]
ZetaNeta has joined #linux-sunxi
Nikolas has quit [Ping timeout: 264 seconds]
Nikolas has joined #linux-sunxi
ZetaNeta has quit [Quit: ZetaNeta]
deasy has quit [Ping timeout: 245 seconds]
<focus_it>
Yeeeeehaaa!! Turl!! Well done 100%!!
<focus_it>
Got linaro working on EOMA with ethernet, sata and hdmi!!!!!!!!!!!!! Love it!
<focus_it>
uSD card images to be uploaded later this evening
<focus_it>
thanks guys
arokux2 has quit [Remote host closed the connection]
arete74_ has quit [Ping timeout: 260 seconds]
arete74 has joined #linux-sunxi
tinti has quit [Read error: Connection reset by peer]
naobsd has quit [Quit: Page closed]
brain_ has quit [Quit: Leaving]
brain_ has joined #linux-sunxi
<hno>
oliv3r, I think ZetaNeta did not follow instructions. fel dump of boot0/ script.bin only works in SOFT FEL mode triggered by keys, not if using the hard FEL button.
<hno>
using hard FEL button gives that USB error as it hangs the CPU when trying to access non-existing DRAM.
<Turl>
focus_it: :)
<specing>
may I warn you that zetaneta is a 10 year old indian boy that has been "trolling" #gentoo* channels for some time now
BJfreeman has quit [Ping timeout: 240 seconds]
iamfrankenstein has quit [Read error: Connection reset by peer]