<wens>
so on sun4i, axi_dram is for bus masters, ahb_dram is for cpu access, pll5_sdram is for the phy
avsm has quit [Quit: Leaving.]
<wens>
Turl: on sun6i, it seems ahb1_sdram is only used for accessing the dram related registers
avsm has joined #linux-sunxi
pwhalen has quit [Ping timeout: 245 seconds]
zeRez has joined #linux-sunxi
deasy has joined #linux-sunxi
deasy has quit [Read error: Connection reset by peer]
leviathanch2 has quit [Ping timeout: 245 seconds]
pwhalen has joined #linux-sunxi
pietrushnic has quit [Ping timeout: 250 seconds]
zeRez_ has joined #linux-sunxi
zeRez has quit [Ping timeout: 246 seconds]
xavia has joined #linux-sunxi
leviathanch2 has joined #linux-sunxi
zeRez_ has quit []
<dack>
Is there a rationale behind sending patches for u-boot through the mailing list instead of a pull request to github? Or is either accepted?
buZz has quit [Read error: Connection reset by peer]
buZz has joined #linux-sunxi
cubear has joined #linux-sunxi
buZz is now known as Guest38114
Guest38114 is now known as buZz
<wens>
dack: sending patches to the mailing list allows others to review them
<wens>
github pull requests may be accepted if they are for u-boot-sunxi
<wens>
for upstream/mainline, the mailing list is what you should use (just like linux)
leviathanch2 has quit [Ping timeout: 260 seconds]
<dack>
wens: is a "pull request" primarily a github construction?
avsm has quit [Quit: Leaving.]
<wens>
dack: no, you can send pull requests using git, it's just an email
<dack>
ah.. okay. My introduction to git was via github.
<wens>
hehe
<wens>
have you read Linus' response to github pull requests? :p
<dack>
wens: ^_^ yes.. you'd think github would listen a little more to Linus' suggestions
<dack>
ssvb: what's the dram rank_num?
<wens>
github is a more "easy to use" GUI
<wens>
mripard_: i think i've hit the limit of number of patches i can mentally keep track of
<wens>
that or i need some sleep
<dack>
wens: it is pretty late in the ROC... ;)
<wens>
dack: just past midnight
<dack>
wens: well, that's pretty late for me... I have a 3yr old kid who wakes me up at 6am
<wens>
tis the mixed joys of raising a child
<wens>
off to bed, see y'all in 9 hours or so
leviathanch2 has joined #linux-sunxi
<ssvb>
dack: rank_num is the number of ranks, in practice it is always 1 for Allwinner devices
<ssvb>
dack: having two ranks instead of one allows to connect twice more ddr3 chips to the SoC
<dack>
wens: it just means you have someone that keeps you to a schedule.. ;)
<dack>
ssvb: ah.. okay.
Gerwin_J has quit [Quit: Gerwin_J]
<ssvb>
dack: for example, a20 dram controller has 32 data lines, and you can normally connect two x16 ddr3 chips to it
<ssvb>
dack: with two ranks, you can connect four x16 chips, and use chip select lines to select two of them, which are currently active
<dack>
ssvb: k. I just wanted to check that my value of '1' made sense. I just copied it from a similar device without understanding it.
pwhalen has quit [Ping timeout: 260 seconds]
<ssvb>
dack: I guess, dual rank configuration is a little bit more complicated to implement properly in both hardware and software, so nobody bothers :)
leviathanch2 has quit [Ping timeout: 272 seconds]
<ssvb>
dack: yes, everyone uses just only one rank, that's enough to populate 2GB of RAM (and 2GB is the limit anyway)
<dack>
ssvb: is that a limit due to the ARM architecture or something else?
<ssvb>
dack: that's a limitation of the SoC, you can check the physical address space map in the A20 user manual
<dack>
ssvb: k.. just curious. ;)
bonbons has joined #linux-sunxi
avsm has joined #linux-sunxi
TheSeven has quit [Ping timeout: 260 seconds]
pwhalen has joined #linux-sunxi
pwhalen has quit [Changing host]
pwhalen has joined #linux-sunxi
TheSeven has joined #linux-sunxi
bengal has joined #linux-sunxi
Zboonet has quit [Remote host closed the connection]
pietrushnic has joined #linux-sunxi
Zboonet has joined #linux-sunxi
Zboonet has quit [Remote host closed the connection]
Zboonet has joined #linux-sunxi
Tenebrous has left #linux-sunxi [#linux-sunxi]
konradoo77 has joined #linux-sunxi
BorgCuba has joined #linux-sunxi
cubear has quit [Ping timeout: 258 seconds]
avsm has quit [Quit: Leaving.]
<BorgCuba>
libv, who is working on vivante?
<BorgCuba>
I just found some interesting code for GC350 and XAQ2(?)
avsm has joined #linux-sunxi
earny has quit [Ping timeout: 250 seconds]
FreezingCold has quit [Ping timeout: 245 seconds]
cubear has joined #linux-sunxi
FunkyPenguin has quit [Quit: No Ping reply in 180 seconds.]
<BorgCuba>
mnemoc, the a80 uses this hantro/on2 decoder?
avsm has quit [Quit: Leaving.]
BorgCuba has quit [Quit: leaving]
pwhalen has joined #linux-sunxi
bertrik has joined #linux-sunxi
FR^2 has quit [Quit: Connection reset by peer]
pwhalen has quit [Ping timeout: 245 seconds]
konradoo87 has quit [Ping timeout: 260 seconds]
pwhalen has joined #linux-sunxi
<oliv3r_>
lo
oliv3r_ is now known as oliv3r
konradoo77 has joined #linux-sunxi
akaizen has quit [Remote host closed the connection]
rafaelMOD has joined #linux-sunxi
<libv>
dack: cool, some meminfo patches for your device\
<libv>
dack: since you probably get no way to rescue things :(
<dack>
libv: I just wanted to get this device working as a linux server... it's actually quite a pile of steaming crap when it comes to playing anything on it in Android
<libv>
yeah, it definitely is better off running linux :)
<libv>
good, i'll commit in a bit
akaizen has joined #linux-sunxi
<Wes->
Does anybody have a line on inexpensive tablets with Allwinner SoCs that can run linux-sunxi out of the box? i.e. just stick in an appropriate microSD card and boot, no shenanigans?
akaizen has quit [Remote host closed the connection]
<libv>
Wes-: did you try looking at our wiki?
akaizen has joined #linux-sunxi
<libv>
if you want cheap: A13 based Q8
<libv>
whether it will just work, probably not.
<libv>
so if you really do not want any hassle at all, and refuse to put in any effort yourself then you are in the wrong place.
konradoo87 has joined #linux-sunxi
akaizen has quit [Ping timeout: 272 seconds]
konradoo77 has quit [Ping timeout: 258 seconds]
Skaag has quit [Quit: Leaving.]
<Wes->
libv: Yeah - I started going through the wiki, but it's not clear to me which of those choices "just work" and which are likely to ship with locked bootloaders requiring more than a small amount of effort to use. (I'm trying to find something I can mail my boss and actually have him boot. It needs to be very simple. :) )
<libv>
Wes-: you will have to put in some effort for yourself
<libv>
it's not much, and definitely not hard, let alone impossible, but bringing up a new device is still several h of work
<libv>
just buy an A20 device from somewhere
<Wes->
libv: I can, for example, build a kernel and tweak a distro and mail the guy an SD card. What I *can't* do is walk somebody through opening a tablet to solder on a serial port so that he type new kernel boot parameters.
<libv>
you'll probably have to spend most of your time getting touch to work
<libv>
then buy two devices, one for you, one for your boss
<libv>
identical
<Wes->
libv: Yeah. I expect that to be a pain. Hopefully the lion's share of that is already done and I just need to integrate.
<libv>
one where you have a uart to help fix some issues
<libv>
Wes-: there is no-one as advanced as us
<libv>
far from it.
<oliv3r>
Wes-: trivially put, get 2 tablets, one for you, one for your boss, fix the SD card for yoruself, clone it, send it to your boss; done :)
<oliv3r>
JINX
<Wes->
libv: Yeah. (except the boss will eventually need about 100...but that's another story). Will he need UART just for troubleshooting, or initial boot? It's actually the initial boot that I'm most confused about. Documentation is very sparse.
<oliv3r>
i'm not as fast as libv :(
<libv>
Wes-: but you do not get that "it just works solution"
<libv>
you do not even get that on x86
<libv>
you get a lot closer with x86
<libv>
but you still do not get that
<libv>
windows gets that as the pc/laptop you buy was specifically designed with and for windows, and you get a disk of drivers specifically for that device for windows.
<Wes->
libv: Actually, what you've described is close enough to "it just works". My concern is that once I ship the boss some tablets and some SD cards that there is still another step he has to jump through to get them to boot the first time.
<libv>
Wes-: correctly insert it?
<libv>
if the devices are identical, there should be no further issues that you shouldn't have already solved
<Wes->
libv: If that's it, then I'm in good shape. I was worried about vendor-locked tablets that won't boot from the SD port until you break into them.
<Wes->
libv: Ah. I was wondering about that. So I can look at A13, A20 tablets fairly safely then. That would be good. I'm hoping to stick with an Allwinner platform since we are already rolling out parts of the same application A10 computers.
<libv>
you can always insert an SD card, and if that is wired up correctly, it should work
<Wes->
libv: that is the best news I have heard all day! :)
<oliv3r>
aren't all OEM allwinner devices properly wired for SD boot?
<libv>
oliv3r: was there so far any device which doesn't boot from sdcard?
<libv>
even the chinese have not messed that up afaik
<dack>
What's the "SUNXI_EMAC" do in the boards.cfg of u-boot-sunxi? I notice some boards have it as an option and others don't.
<libv>
10/100Mbps ethernet mac
<oliv3r>
libv: i only know of some custom device where some guy left it off as he didn't think it was important
<dack>
libv: I've seen one A20 device with no SD card... so it shouldn't be able to boot from sd card.. ;)
<libv>
oliv3r: ok... did he curse a lot?
<oliv3r>
i think most OEM's do the first flash via sd card?
<oliv3r>
libv: he did :)
<libv>
oliv3r: serves him right :p
<dack>
libv: okay, so if I have a physical ethernet port I should include that?
FR^2 has joined #linux-sunxi
<libv>
dack: in uboot, only when you want it to boot over ethernet
<libv>
perhaps it is not a bad thing to do that by default
<libv>
Alt is documenting those uboot options now btw
Zboonet has quit [Remote host closed the connection]
<libv>
ok, seems i need to commit some patches, so two more boards make it all the way
<dack>
libv: yeah, I thought I'd stick that in just in case..
<dack>
libv: Should I generate a new patch including this change I'm doing right now or can you chain the patches... (I'm not familiar with using patches from emails)
<libv>
dack: isn't that a 10/100 phy that is on your device?
<libv>
also, emac is 10/100, gmac is Gbps
<dack>
libv: I'm not sure, but I think it is
<libv>
ok
<dack>
my change is "sun7i:TXCZ_A20_V1,SPL" => "sun7i:TXCZ_A20_V1,SPL,SUNXI_EMAC,STATUSLED=244"
akaizen has joined #linux-sunxi
<libv>
ok
<libv>
will do that for you
<libv>
as it is barely 2s more work for me
<dack>
libv: k.. thanks..
<libv>
also, i do not get pull requests for sunxi-boards
<libv>
so if you want things for old style board support, you will have to use email
<dack>
libv: is that for future reference or do you need an email patch for that TXCZ_A20 fex?
<libv>
i'll grab it myself, i just only noticed it from your uboot commit message
petr_ has quit [Ping timeout: 272 seconds]
egbert has quit [Ping timeout: 245 seconds]
jmcneill has joined #linux-sunxi
egbert has joined #linux-sunxi
<jmcneill>
Hi! I wasn't able to find on the wiki -- has anyone managed to get to a U-Boot prompt on a Hummingbird A31?
<libv>
jmcneill: 2 answers.
<libv>
first, allwinner has not provided us with reasonable dram information for us to add full uboot support
petr has joined #linux-sunxi
bonbons has quit [Quit: Leaving]
cubear has quit [Quit: Leaving]
<libv>
secondly, we still have no A31_Manual_Build_howto, where the allwinner binary boot0, an sdk uboot, and an sdk kernel are combined to form a workable sd card image
<libv>
i would be thrilled if anyone would start working the latter though
<jmcneill>
That's exactly what I was looking for. I have the AllWinner SDK but no idea how to make the image. Clearly different from A20.
<jmcneill>
I see some mentions of a boot1 for A31, do you know where that fits in?
<libv>
i do not own any a31 hw
<libv>
so i have no idea
<libv>
check the wiki to see if it has anything on that
<jmcneill>
It says: Linux-sunxi's U-Boot currently lacks SPL support. This means that you have to chain load it from Allwinner's bootloader How?.
<libv>
jmcneill: these are things you have to solve still.
<jmcneill>
I was afraid you'd say that :)
<libv>
i have been saying that for the last 14 minutes
balog has quit [Read error: Connection timed out]
<jmcneill>
Alright, well thanks for your help. Much appreciated.
jmcneill has quit [Quit: Leaving]
<libv>
...
balog has joined #linux-sunxi
petr has quit [Ping timeout: 246 seconds]
<libv>
typical.
<libv>
note how the very first line typed was clearly pointing at this.
paulk-collins_ has quit [Remote host closed the connection]
petr has joined #linux-sunxi
konradoo77 has joined #linux-sunxi
konradoo87 has quit [Ping timeout: 260 seconds]
bart2014 has joined #linux-sunxi
<bart2014>
Hi everyobdy
<bart2014>
Can i ask a question ? Im using cubietruck with ubuntu 13.10 sunxi mod installed, lxde, i would like boot in ocnsole mode but i cannot find grub (is not present)... any hint?
<libv>
bart2014: read up on uboot in our wiki
<libv>
also, i guess you are barking up the wrong tree. you need to find a way to stop the display manager from loading, and to get gettys up on the VTs
<libv>
this is very distribution specific
<libv>
and has nothing to do with sunxi
<bart2014>
sorry then....
<libv>
no need for an apology, google for ubuntu 13.10 stop lightdm
Black_Horseman has joined #linux-sunxi
akaizen has quit [Remote host closed the connection]
dack has quit [Remote host closed the connection]
Wes- has quit [Remote host closed the connection]
Skaag has joined #linux-sunxi
TheSeven has quit [Ping timeout: 272 seconds]
akaizen has joined #linux-sunxi
TheSeven has joined #linux-sunxi
bart2014 has quit [Quit: —I-n-v-i-s-i-o-n— 3.2 (July '10)]